Free Salesforce-Consumer-Goods-Cloud-Trade-Promotion-Management-Accredited-Professional Practice Test Questions (2026)

Explanation:
NTO needs to model a retailer’s structure of more than 20 direct stores plus outlet chains so promotions can be planned at headquarters and cascade to lower levels. In Consumer Goods Cloud TPM, the recommended way to represent multilevel buying groups or chains of retail outlets is a Customer Hierarchy (Trade Org Hierarchy). This parent-child structure lets Key Account Managers plan once at the top and push or aggregate results across all related stores and chains.

Correct Option:

A. Customer Hierarchy –
Salesforce documentation states that if a customer has multilevel buying groups or chains of retail outlets, you create hierarchies that reflect this structure. KAMs can then plan promotions for the top account and make them available to all accounts in the hierarchy, run promotions at individual account level, and view aggregated account-plan values at the parent. This exactly matches the retailer-store-to-outlet-chain relationship required by NTO.

Incorrect Option:

B. Customer subaccounts –
Subaccounts are used to split volume percentages (e.g., Minimarket 40 % / Hypermarket 60 %) under a single customer for granular KPI tracking in account plans. They do not model hierarchical parent-child relationships between stores and outlet chains, and promotions cannot be created directly on subaccounts.

C. Customer Sets –
Customer Sets are simple administrative groups used to assign the same promotion to many unrelated customers quickly. Salesforce explicitly notes limited TPM capabilities with sets and recommends Customer Hierarchy instead for structured retailer relationships. Sets lack parent-child inheritance and aggregation.

Reference:

Salesforce Help – Create and Organize Customers / Create a Customer Hierarchy (TPM): “If your customer has multilevel buying groups or chains of retail outlets, create hierarchies that reflect the structure of these groups.”

Salesforce Help – Main Objects in Customer Master: Trade Org Hierarchy stores parent-child relationships so child accounts inherit TPM activities from the parent.

Explanation:
In Consumer Goods Cloud TPM, the Latest Estimate KPI in an Account Plan P&L must dynamically show actual values for all past periods and planned values for the current period plus all future periods. KPI formulas are written in JavaScript and can reference a special collection of helper functions (calcHelper) even when they are not listed as input parameters. These helpers provide period-aware logic (such as comparing the period start date to today) so the formula can correctly switch between actual and planned values based on whether the week is past, current, or future.

Correct Option:

A. Use an available calcHelper function. –
Salesforce documentation confirms that formulas for calculated (and editable-calculated) KPIs can freely call calcHelper methods. Functions such as calcHelper.daysUntilStart(Period.datefrom) return the number of days between the calculated period and the current date, allowing the formula to decide: if the period is in the past → use actual values; if it is current or future → use planned values. This is the designed, supported way to implement time-dependent Latest Estimate logic inside the KPI formula.

Incorrect Option:

B. Use the standard Salesforce formula function PREVGROUPVAL. –
PREVGROUPVAL is a reporting function available only in Salesforce custom summary formulas on reports. It is not available inside TPM KPI calculation formulas, which run in the TPM calculation engine (JavaScript + calcHelper), not in standard Salesforce report formulas.

C. Use the existing planned values if actual values are 0. –
Simply falling back to planned values when actuals equal zero is unreliable. Actuals can legitimately be zero (or null) in past periods, and this approach cannot correctly identify the current week or distinguish past from future periods. It also ignores the proper time-based logic that calcHelper provides.

Reference:

Salesforce Help – Calculation Helper Functions In a Formula: “a formula can access a calculation helper without specifying the helper as an input parameter.” Includes helpers such as daysUntilStart(calculationPeriodDateFrom).

Salesforce Help – Understanding How KPI Values are Calculated When Other KPIs are Referenced: calcHelper is the explicit exception that can be used in KPI formulas.

Explanation:
The client requires the discount KPI to be entered manually by the KAM and editable only at the total level of the tactic/product hierarchy, not at the weekly level. In Consumer Goods Cloud TPM, editable KPIs have an Edit Mode setting that controls exactly where values can be changed. Setting Edit Mode to Total restricts manual input to the Total column only; weekly (period) cells remain non-editable. This matches the requirement while still allowing the KAM to provide the discount value at the overall tactic/product level.

Correct Option:

B. Set the Edit mode of the discount KPI as Total. –
Salesforce documentation for creating editable KPI definitions states: “To enable editing only for totals, select Total. To edit only periods, select Week. To edit both totals and periods, select All.” Choosing Total ensures the discount can be entered only in the Total column and cannot be changed week by week, exactly as requested.

Incorrect Option:

A. Set the Edit mode of the discount KPI as All. –
Edit Mode = All allows the KAM to edit both the Total column and every weekly period. This violates the requirement that the discount must not be editable on a weekly level.

C. Set the Editable storage level of the discount KPI as Tactic. –
Editable Storage Level controls where the manually entered value is physically stored in the hierarchy (e.g., Product, Tactic, or input level). It does not control whether weekly cells are editable. Storage level alone cannot enforce “total-only” editing; that is controlled exclusively by Edit Mode.

Reference:

Salesforce Help – Create KPI Definitions: “To enable editing only for totals, select Total. To edit only periods, select Week. To edit both totals and periods, select All.”

Salesforce Help – Types of KPIs: “The Edit Mode defines whether the weekly, total or both values of the KPI are editable.”

Explanation:
During UAT, users found that products with a valid KAM status for at least one day inside the promotion period (Date From – Date Thru) could not always be added. In the promotion template, the setting that controls how product eligibility is evaluated against KAM status is “Consider Product KAM Status.” Its two options are Promotion Commit Date (stricter) and Promotion Timeframe (allows any product that overlaps the promotion period by at least one day). Checking and adjusting this setting resolves the observed restriction.

Correct Option:

A. Consider Product KAM Status –
Salesforce documentation for Create a Promotion Template states that this field “Specifies the promotion date or date range that you can use to determine the valid products for a promotion based on the KAM status time frame.” The option Promotion Timeframe explicitly “Ensure[s] that the product has at least one day of the promotion time frame (Date From – Date Thru) within the time frame of the KAM Status.” The default is the more restrictive Promotion Commit Date, which is why some eligible products were blocked.

Incorrect Option:

B. Timeframe Determination Policy –
This setting controls how the promotion’s own start and end dates are determined (Manual, Automatic Simple, etc.). It does not govern product eligibility based on KAM status.

C. Consider Product Definition Policy –
This setting (Dynamic / Static) controls whether products are added via filters that react to master-data changes or are fixed manual selections. It does not evaluate KAM status validity periods.

Reference:

Salesforce Help – Create a Promotion Template (Product Settings section):

“Consider Product KAM Status – … Promotion Timeframe: Ensure that the product has at least one day of the promotion time frame (Date From – Date Thru) within the time frame of the KAM Status. Note: The default value is Promotion Commit Date.”

Explanation:
To make the Volume Planning card (VPC) visible to the KAM on Volume Only promotions, the consultant must enable it on the promotion template. The promotion template contains a dedicated “Display VPC” checkbox that controls whether the Volume Planning card appears for every promotion created from that template. Once selected (and the correct KPI set containing the VPC subset is linked), the KAM can open and use the VPC. This is the primary configuration point for VPC visibility.

Correct Option:

C. In the promotion template –
Salesforce documentation (Create a Promotion Template and Volume Planning Card Configuration) explicitly lists the setting “Display VPC – Shows the Volume Planning card in the promotion.” The configuration workflow also states: “Enable the VPC for a promotion type by selecting the Display VPC check box” on the promotion template, then associate the KPI set that contains the VPC subset.

Incorrect Option:

A. In the tactic template –
Tactic templates control tactic-level settings such as Display KPI Subset for the Spend Planning card (SPC). They do not contain a Display VPC option; VPC is a promotion-level card.

B. In the KPI subset –
Assigning KPIs to the VPC subset makes those KPIs available inside the card, but it does not turn the card itself on or off. Visibility of the VPC is controlled only by the Display VPC checkbox on the promotion template.

Reference:

Salesforce Help – Create a Promotion Template: “Display VPC – Shows the Volume Planning card in the promotion.”

Salesforce Help – Volume Planning Card Configuration: “Enable the VPC for a promotion type by selecting the Display VPC check box” on the promotion template.

Explanation:
Cloud Kicks uses assortments to drive the customer (account) product list. When KAMs add or change products in an assortment multiple times a day, those changes must be reflected in the time-dependent Account Product List (APL) before the products can be selected in a new promotion. In Consumer Goods Cloud TPM the APL is maintained in the CG Cloud Processing Service. Therefore the assortment updates must be synchronized (via SF Data Sync or the Account Product List alignment process) so the newly added products become available for promotion planning on the same day.

Correct Option:

B. Sync the changes in the assortment with the processing service. –
Salesforce documentation states that for time-dependent APLs “If there are unsynced changes to an assortment, the assortments are synced with off core applications and the time-dependent APLs is updated.” SF Data Sync (or the TPM Calculation Chain’s Account Product List step) pushes assortment changes from Salesforce into the Processing Service, after which the products appear in the customer product list and can be promoted.

Incorrect Option:

A. Re-approve the changes in the assortment. –
Assortments do not require a separate re-approval step for product-list updates to become usable in promotions. Approval workflows are not the mechanism that refreshes the APL.

C. Refresh the assortment screen. –
Refreshing the UI only reloads the current Salesforce view; it does not push the changes to the Processing Service or update the Account Product List that promotions use.

Reference:

Salesforce Help – Configure TPM Calculation Chain: “timedependent: The time-dependent APL for an account is based on the assortments of an account. If there are unsynced changes to an assortment, the assortments are synced with off core applications and the time-dependent APLs is updated.”

Salesforce Help – Sync Data with CG Cloud Processing Services: SF Data Sync replicates changed product/assortment data to the Processing Service.

Explanation:
In Consumer Goods Cloud TPM, product-level access for a KAM is controlled through User Settings combined with the Product Manager (Managed Products) relation. By assigning the Beverages category to the KAM in User Settings (and leaving the Customer field blank), the KAM becomes the product manager for Beverages across all customers. This restricts the products the KAM can see and plan in promotions, account plans, and the Trade Calendar to only those in the Beverages category.

Correct Option:

C. Configure user settings by assigning the Beverages category to the KAM through the product manager… –
Salesforce documentation states that User Settings define the customer–category combinations a user can manage. Assigning the Beverages category (with no specific customer) makes the KAM the product manager for that category for every customer in the sales organization. The system stores this relation in the Product Category Share object and filters products accordingly.

Incorrect Option:

A. Implement a sharing rule on the Product object… –
Standard Salesforce sharing rules on Product do not drive the TPM-specific product-category filtering used in promotions, account plans, or the Trade Calendar. TPM relies on the Product Manager relation instead.

B. Utilize Role-Based Permissions… –
Salesforce roles and permission sets control feature access (e.g., CGCloud KAM permission set), not the specific product categories a user can manage. Category restrictions are handled exclusively via User Settings / Product Manager assignments.

Reference:

Salesforce Help – Create User Settings: “Select the product category that you want to give the user access to. … If you leave the Customer field blank, the user is the product manager of the product category for all customers in the sales organization.”

Salesforce Help – Assign a Product Manager to a Product / Add Managed Products: Product Manager relations restrict the products and customers a user can see and plan.

Explanation:
Northern Trail Outfitters needs a flexible KAM landing page that surfaces volume-vs-target graphs, deal status indicators (Y/G/R), brand and promo performance, and pending approvals. In Consumer Goods Cloud TPM (Lightning Experience), the recommended approach is to build a Lightning App Home or utility page that hosts standard and custom widgets, embedded dashboards, KPI reports, approval lists, and task components. Access to the underlying data is automatically governed by the user’s profiles, permission sets (for example CGCloud KAM / TPM Standard User), and sharing rules, so each KAM sees only the records they are entitled to.

Correct Option:

A. – Salesforce best practice for TPM KAM home pages is to assemble Lightning page components (charts, report charts, list views of pending approvals, KPI tiles, etc.). These components inherit the running user’s sharing rights, profiles, and permission sets, delivering exactly the personalized view required without custom code.

Incorrect Option:

B. – Uploading a JSON customization file as a static resource is the pattern used for certain offline/mobile landing-page configurations (Salesforce Mobile App Plus), not for the desktop TPM KAM experience. It is not the supported method for the widgets and approval lists described.

C. – Organization-wide defaults control baseline record visibility; they cannot create a multi-widget landing page or surface the required visualizations and approval queues.

Reference:
Salesforce Help – Permission Sets (CGCloud KAM / TPM Standard User) and Lightning App Builder documentation for embedding dashboards, reports, and approval components on home pages. Data visibility is governed by the user’s sharing model and assigned permission sets.

Explanation:
To load Sell-through volume (or any measure) into the CG Cloud Processing Services so it can be read as a KPI, the system administrator must be able to register and interact with the processing-services tenant. Salesforce provides a dedicated permission set license, CGC Processing Services Register, that grants the rights required to pair the org with the processing engine, manage the connection, and load interfaced data. Without this license the administrator cannot complete the data-load steps into the processing engine.

Correct Option:

C. CGC Processing Services Register –
Official documentation lists this permission set license as the one that “Provides access to register-processing services.” It is explicitly required for any user who sets up or loads data into CG Cloud Processing Services (the engine that stores and calculates TPM KPIs).

Incorrect Option:

A. Lightning Trade Promotion Management Psl –
This permission set license grants access to TPM objects and features inside Salesforce; it does not authorize registration or data loading into the external processing services.

B. CGC Retail and Trade Promotion Management Psl –
This license covers the shared objects used by both Retail Execution and TPM. It is required for general TPM functionality but is not the specific license needed to register or load data into the processing engine.

Reference:

Salesforce Help – Trade Promotion Management Permission Set Licenses:

“CGC Processing Services Register: Provides access to register-processing services.”

Salesforce Help – Set Up Consumer Goods Cloud Processing Services: Users who manage the processing-services connection require the CGC Processing Services Register permission set.

Explanation:
In Consumer Goods Cloud TPM, BOM component quantities are stored on the Product Part (BOM relation) records and are time-dependent via Valid From / Valid Thru dates. The quantity field itself cannot be changed after the association is created. When a component quantity changes, the correct approach is to close the existing relation one day before the change and create a new Product Part record that starts on the change date with the updated quantity. This preserves historical accuracy for past promotions while applying the new quantity going forward.

Correct Option:

B. – Salesforce documentation for creating a Bill of Material states that the quantity “can’t be changed after the association is created.” Validity periods are maintained with Valid From and Valid Thru. Therefore the supported pattern is to set Valid Thru on the old relation to the day before the change and insert a new relation record with the new quantity and Valid From equal to the change date.

Incorrect Option:

A. – Ending the entire BOM header product and creating a completely new BOM is unnecessary and would break existing promotions that reference the original header. Only the affected component relation needs to be versioned.

C. – Directly updating the quantity (and shifting Valid From) on an existing relation is not allowed; the quantity field is immutable after creation. Changing Valid From retrospectively would also corrupt historical data.

Reference:
Salesforce Help – Create a Bill of Material: “Enter the quantity of the child product that’s included in the parent product. You can’t change this field after the association is created. Select the validity dates.”