Important Salesforce AP-205 Exam Questions

Answer: B

Explanation:

This scenario addresses a common data granularity mismatch: the Planning is done at the Parent (Anchor) level, but the Data (Base Volumes) resides at the Child (Sub Account) level.

To bridge this gap, thePromotion TemplateandAccount P&Lmust be configured forAggregation.

Select Sub Accounts on Account P&L:The Key Account Manager must essentially 'opt-in' the relevant sub-accounts into the view. This tells the systemwhichchildren contribute to this plan.

Calculation Mode: Sub Account Aggregation:This is the specific setting in the Promotion Template that dictates the engine's behavior. Instead of looking for a baseline volume record attached directly to the Parent Account (which doesn't exist in this scenario), the engine is instructed to look at the selected Sub Accounts, retrieve their individual baselines, andsum them up(Aggregate) to display the total at the Planning Account level.

Without this 'Sub Account Aggregation' mode, the baseline at the planning level would likely show as zero because the system would default to looking for a direct match at the parent level. Option B correctly identifies the combination of UI selection (P&L) and calculation logic (Aggregation Mode) required to surface this data.

Answer: C

Explanation:

Customer Business Plans (CBPs) in Consumer Goods Cloud are records that establish the targets and planning data for a specific customer and year. If the granularity of the planning needs tochange (e.g., from 'Planning Customer + Category' to just 'Planning Customer'), the existing CBP records can be deleted provided they are not locked by active workflows or other restrictive dependencies that strictly prevent deletion. Deleting the incorrect CBPs allows the administrator to re-upload or re-create the plans at the correct level of granularity (Planning Customer level) for both the Current Year and Next Year to meet the new business requirement.

=============

Answer: B

Explanation:

To execute a specific promotional mechanic like 'Buy One Get One' (BOGO), the system needs to know how to calculate the cost. In Consumer Goods Cloud TPM, this financial logic is determined by the Compensation Method configured on the Tactic.

Tactic Template:The consultant has already created the container (the 'BOGO' Tactic Template).

Compensation Method:This is the engine under the hood.

Per Case:Calculates cost as $X per unit sold. (Incorrect for BOGO).

Fixed:Calculates cost as a flat lump sum. (Incorrect for BOGO).

BOGO (or Free Goods):This specific compensation method contains the logic to understand that for every X units bought, Y units are given free. It calculates the 'Cost' of the promotion based on theCost of Goods Sold (COGS)of the free items, rather than a discount off the invoice.

Therefore, selecting theCompensation Method BOGO(Option B) is the critical configuration step. It instructs the calculation engine to apply the correct 'Free Goods' formula to the tactic, ensuring that the Spend and ROI metrics reflect the cost of the given-away inventory.

Answer: C

Explanation:

The requirement is twofold: flexible planning (sometimes total customer, sometimes specific format) and graphical visibility (filtering the calendar).

Option C offers the most efficient design by leveraging Promotion Attributes and the native Trade Calendar filtering capabilities.

Instead of fracturing the account structure or forcing every promotion to be at the 'Sub Account' level (which adds significant maintenance overhead as seen in Option B), the consultant should recommend planning at the main Customer level. To handle the 'Format' distinction, a custom dropdown (Attribute) is added to the Promotion Template labeled 'Store Format' (e.g., Hypermarket, Minimarket, All).

The crucial feature here is theTrade Calendar'sability to filter based on these attributes. The KAM can open the calendar for the 'German Market' account and apply a quick filter: 'Show only Hypermarket promotions.' This instantly renders the requested 'graphical overview' of the timeframe overlap for that specific format. This approach avoids the need for external reporting (Option A) and keeps the user experience seamless within the TPM application, satisfying both the data capture and the visualization requirements with standard configuration.

Answer: A

Explanation:

In Salesforce Consumer Goods Cloud, the Customer Trade Org Hierarchy is the foundational structure used to model the commercial relationships between accounts. This hierarchy is designed to handle the standard parent-child relationships found in retail, such as a Headquarters (Parent) governing multiple regional divisions, which in turn govern individual Stores or Outlets (Children).

When NTO needs to run a promotion that targets a retailer and trickles down to its 20+ direct stores and outlets, theCustomer Hierarchyis the native mechanism to represent this. By setting up the Stores as child accounts of the Retailer Chain account in the hierarchy:

Data Aggregation:Sales volume and trade spend can automatically roll up from the stores to the chain level.

Promotion Push: A promotion planned at the Chain level can be automatically pushed or made applicable to the underlying stores.

'Customer Sets' (Option C) are typically used for grouping disparate, unrelated accounts for a specific promotion (e.g., 'All Gas Stations in Florida'), whereas the retailer-to-store relationship is a permanent structural relationship best modeled by the standard Hierarchy.