AP-205 Exam Dumps : Consumer Goods Cloud: Trade Promotion Management Accredited Professional

In the Salesforce Consumer Goods Cloud (CGC) architecture, data is split between the core Salesforce platform (where standard objects like Assortments and Products reside) and the Cloud Processing Service (the high-performance calculation engine usually hosted on Hyperforce/Heroku).

When a Key Account Manager (KAM) updates aProduct Assortmentin the core platform—for example, adding a new SKU to the "Summer 2025" list—this change is committed to the Salesforce database immediately. However, the TPM Planning Grid (the P&L view) and the Promotion Product Selector rely on the Processing Service to render data quickly. The Processing Service uses a cached or synchronized version of the master data to perform its complex calculations.

If the KAM immediately tries to create a promotion for the new product, it might not appear in the selector because the Processing Service is unaware of the update. Merely refreshing the screen (Option C) only reloads the UI, not the underlying data cache. Therefore, to bridge the gap between Core Salesforce and the Calculation Engine, the KAM or an automated process mustSync the changes(specifically the Assortment-Product links) to the processing service. This action pushes the new relationship into the engine's memory, making the product available for immediate promotion planning and calculation.

The Ad-Hoc Sync feature in Consumer Goods Cloud is a critical administrative tool used to push metadata and configuration changes to the Processing Service immediately, bypassing the standard nightly batch windows. This is essential during setup or debugging (like scenario planning configuration) to verify results instantly.

To determinewhichobjects need syncing, analyze what was changed:

New Fields & Linking:The admin created fields and updated theKPI Map. The KPI Map tells the engine how to read/write data from Salesforce fields into the calculation grid. If this isn't synced, the engine won't know the new fields exist.

Configuration:ThePromotion Templatewas modified to include the new KPI Set. The template is the blueprint; the engine needs this new blueprint to know which KPIs to display and calculate.

Transactional Data:Promotionswere created using this template. For the scenario planning to work on these specific records, the promotion instances themselves must be recognized by the processing layer.

While "Customer Extension" (Option B/C) is important for account-level attributes, the scenario specifically highlights changes to theKPI definition,Template structure, and thePromotionsthemselves. Therefore, the set {KPI Map, Promotion Template, Promotion} represents the specific metadata chain that must be refreshed for the calculation engine to correctly process the new scenario planning logic.

Onboarding a "new group" of users implies a bulk operation. In the Salesforce ecosystem, the standard best practice for bulk data creation is using Data Loader or the Import Wizard via File Upload (Option C).

For TPM specifically, setting up a user is not just about creating the User record. It requires:

User Record:Name, Email, Username.

Profile & Permission Sets:Assigning the "TPM User" license and specific permissions.

User Settings:(Critical for TPM) Assigning the user to aSales Organd defining theirManaged Accounts/Products.

Option C correctly identifies that all these steps can be handled by preparing a data file (CSV) and uploading it to mass-create and mass-assign these records. "Quick Start" (Option A) is typically for initial org setup, not ongoing user management. Custom scripts (Option B) are unnecessary technical debt when standard tools exist.