AP-205 Consumer Goods Cloud: Trade Promotion Management Accredited Professional Exam Topics and Questions

Discovery carries the heaviest weighting on this exam and tests whether you can translate business need into documented requirements across functional, technical and volumetric dimensions. The domain spans use-case validation, interview technique, system boundaries, process mapping and the discipline of balancing what users want against what the platform can deliver at scale.

– Use case validation and interview structure

You need to know when Consumer Goods Cloud and TPM fit a customer's environment and when they do not. That means recognising the signals in a use case that point to trade promotion management rather than a different Salesforce product or a bolt-on. The TPM lifecycle provides the frame for discovery interviews, so you are expected to structure conversations around planning, execution, settlement and analysis rather than letting requirements gather in an unordered list. The exam tests whether you can move from high-level business requirements to a coherent interview agenda that covers each lifecycle stage without skipping the steps that expose risk early.

– System boundaries and process documentation

Enterprise landscapes are messy. TPM sits alongside ERP, supply chain platforms, retail execution tools and analytics layers, and you need to map capabilities to the right system. The exam presents scenarios where a function could live in TPM or be handled by a third party, and you are expected to choose based on fit and integration cost. Process mapping follows: given specific customer requirements, you document the customer journey in enough detail that design can begin. That means identifying handoffs, decision points and data flows, not drawing swimlanes for the sake of it. The skill being tested is knowing what level of detail matters and what can wait.

– Requirements capture across three dimensions

Functional requirements describe what each step in the business process needs in terms of data and functionality. You gather these by asking what changes hands, what gets approved, what triggers the next action. Volumetric information underpins non-functional requirements: user counts, transaction volumes, data retention periods, peak load windows. These determine whether the design will perform and scale, and the exam expects you to know which numbers to ask for and why they matter. Technical requirements come last, shaped by the customer's technology landscape and environment. You apply product and platform best practices to ensure the solution can be built, deployed and supported without running into governor limits or architectural dead ends.

How Discovery is tested

At thirty-two percent, Discovery questions appear more often than any other topic and they test your ability to ask the right question at the right moment in a customer engagement. Items present a scenario with partial information and ask what you need to clarify next, or they describe a customer environment and ask whether TPM is the correct fit. You lose marks by choosing answers that jump to design before requirements are clear, or by gathering detail that does not change the architecture. The exam also tests whether you can distinguish functional requirements from volumetric ones, and whether you know which system should own a given capability when the enterprise landscape includes multiple platforms. Watch for distractors that sound thorough but collect information no one will use, and for answers that confuse interview structure with project governance. The weight means you cannot afford to guess your way through this section.

Design is the heaviest topic and the one that decides whether your solution will survive contact with real users. You are working from the requirements gathered in Discovery and turning them into a configured system: master data structures, KPI hierarchies, funds management logic, account planning setups, promotion templates, execution workflows and reporting. Every design choice has to be validated against stakeholder priorities before implementation begins, and the exam tests whether you know which standard capability to apply to each part of the customer's process.

– Master data and architecture foundations

Master data design starts with business requirements and integration information, and you apply best practices to plan how accounts, products, hierarchies and organizational structures will be modeled and maintained. The exam expects you to know when to extend standard objects, when to use custom metadata, and when to push complexity into an external master data management system. Architecture decisions made here ripple through every other module, so the questions focus on trade-offs: flexibility against complexity, ease of reporting against ease of maintenance. You need to recognize when a customer's data model will break promotion planning or make account hierarchies unmanageable, and propose a structure that works within platform limits.

– KPIs, funds and account planning

KPI design follows the customer's strategic planning process and areas of focus. You use standard KPI capabilities to build the structure that tracks performance without creating so many metrics that no one can interpret them. Funds management design depends on how the customer allocates trade spend: top-down budgets, bottom-up accruals, or a hybrid. You apply standard capabilities to ensure funds can be committed, claimed and reconciled without manual spreadsheet work. Account planning ties planning metrics to the account and product hierarchy, and the exam tests whether your setup supports the customer's Go-To-Market approach. That means knowing which dimensions to expose, which to lock, and how to handle exceptions when a retailer does not fit the standard model.

– Promotion planning and execution

Promotion planning structures are defined using standard functionality: templates, tactics, and the building blocks that let users assemble a promotion without starting from scratch every time. The exam presents a customer's Go-To-Market approach and asks you to choose the right combination of promotion types, tactic libraries and approval workflows. Promotion execution design brings in KPIs, Claims, and Account P&L capabilities. You need to understand how execution data flows back into planning, how claims are matched to promotions, and how account-level profitability is calculated. The questions focus on whether your design closes the loop between what was planned and what actually happened, and whether it does so in a way that users will trust.

– Business plans, reporting and validation

Customer business plans are set up to reflect specific business planning processes, and the exam expects you to know how to structure them so they align with the customer's calendar, approval stages and review cycles. Reporting design follows monitoring and analysis requirements: you determine which standard report or dashboard meets the need, and when you need to build a custom solution. The final step in design is validation. Given a draft of the solution design, you confirm priorities with key stakeholders to ensure accuracy before anything is built. The exam tests whether you know what to validate, who needs to approve it, and how to handle conflicting feedback when two stakeholders want incompatible things.

How Design is tested

Design carries the highest weight at thirty-six percent, and the questions assume you have read the requirements and now have to choose between competing design options. Items describe a customer's process or constraint and ask which standard capability to apply, or they present a draft design and ask what is missing or wrong. You lose marks by over-engineering solutions that could use out-of-the-box features, or by choosing configurations that will not scale when volumes grow. The exam also tests whether you can sequence design decisions correctly: master data before KPIs, funds management before promotion templates, account planning before execution workflows. Watch for distractors that sound sophisticated but introduce unnecessary custom code, and for answers that skip stakeholder validation or assume requirements will not change. The weight means this topic decides your result more than any other.

Implement takes the validated design and turns it into a working system. You are configuring TPM settings, promotion and TPM templates, the data model, individual modules, KPIs, workflows and then populating both Salesforce and the Consumer Goods Cloud processing service with migrated data. The domain also covers licensing, package installation and deployment strategy, because getting the sequence wrong will cost you days of rework.

– Licensing, installation and deployment

Before anything else, you rationalize the licensing needs and install the Consumer Goods Cloud package following the pre- and post-installation steps that ensure dependencies are met and features unlock correctly. The exam expects you to know which licenses are required for which roles, and what happens if you try to configure TPM before the package is fully installed. Deployment strategy follows the project lifecycle requirements: you establish a plan that accounts for sequential migration steps across sandbox, UAT and production. The questions test whether you understand that some configuration must happen in a specific order, and that deploying everything at once will break integrations or leave users without the data they need to test.

– Foundational configuration and templates

Once the package is in, you configure the TPM settings that form the foundation of the Consumer Goods Cloud environment. This is where you set defaults, enable features and establish the guardrails that every other module will respect. Promotion templates and TPM templates come next. Given the approved solution design, you configure these so that users can create promotions and plans without having to rebuild structure each time. The exam tests whether your templates align with the customer's Go-To-Market approach and whether they enforce the business rules that were agreed during design. Template configuration is not cosmetic: a poorly designed template will let users create promotions that cannot be settled or plans that cannot be reported on.

– Data model, modules, KPIs and workflows

The data model is configured to prepare for master data setup, and the exam expects you to know which objects to extend, which fields to add, and which relationships to establish before any records are loaded. Module configuration follows: you set up the various TPM modules according to the approved solution design, ensuring that planning, execution, settlement and analysis all work as intended. KPI configuration is tested separately because it involves defining calculations, setting thresholds and mapping data sources, and a mistake here will cascade through reporting. Workflow configuration automates business processes: approvals, notifications, field updates and record ownership changes. You need to know when to use Process Builder, Flow or Apex, and when automation will create more problems than it solves.

– Data migration

Data migration happens in two parts. First, you populate Salesforce Consumer Goods Cloud data: accounts, products, hierarchies, users and historical promotions. Then you populate the Consumer Goods Cloud processing service data, which handles the calculations and aggregations that TPM relies on. The exam tests whether you know the sequence, the data quality checks to run before migration, and how to handle errors when records fail to load. Migration is not a one-time event: you will need to refresh data in lower environments, and the questions focus on whether your migration design accounts for that without breaking existing configuration or losing user work.

How Implement is tested

Implement is weighted at thirty-two percent and the questions assume design is locked and approved. Items describe a configuration task and ask which setting to change, which object to update, or which sequence to follow. You lose marks by configuring modules before the foundation is in place, or by skipping steps that seem optional but are actually required for downstream functionality. The exam also tests whether you know when to use declarative tools and when to write code, and whether you understand that data migration is not just an ETL job but a validation exercise that will surface design flaws you missed earlier. Watch for distractors that suggest configuring everything in production, or that assume data can be migrated in any order without consequence. The weight is the same as Discovery, so implementation mistakes are just as costly as requirements mistakes.