AP-208 Salesforce Accredited Agentforce Financial Services Professional Exam Topics and Questions

Discovery sets the tone for everything that follows. You're documenting what the client wants from Agentforce Financial Services, why they want it, and what success looks like. Get this wrong and the rest of the project builds on sand. The work here is translating business language into system requirements while mapping the current state accurately enough to design a credible path forward.

How Discovery is tested

At 12 percent, Discovery appears less frequently than design or delivery, but the items are dense. You'll face scenarios that describe a client situation in a few sentences and ask you to identify the correct next step, the right stakeholder question, or the documentation priority. The trap is choosing the answer that sounds consultative but skips a necessary step. For example, proposing a solution before you've mapped the current state, or documenting vision without tying it to measurable outcomes. Another common mistake is confusing business process mapping with technical architecture. The exam wants you to know when you're still gathering information and when you have enough to move forward. Marks are lost by candidates who jump to design too early or who document the wrong level of detail for the discovery phase.

Define/Design is the heaviest topic by far, carrying 42 percent of the exam. You're translating requirements into a working architecture, choosing the right objects and relationships, and making security decisions that will either enable the business or create support tickets for years. The breadth here is wide: data model, process design, sprint planning, and migration strategy all sit under one topic.

– Data model and object design

You need to know which objects, record types, and relationships the Agentforce Financial Services data model provides, and when to use them versus when to extend. The exam will describe a business requirement and ask you to identify the correct object structure. The mistake candidates make is choosing a custom object when a standard Financial Services Cloud object already handles the use case, or picking a lookup when a master-detail relationship is required for rollups. You also need to recognize when a requirement calls for a record type versus a separate object entirely. The data model is not optional knowledge here. If you can't map a business entity to the right object without hesitation, you'll burn time and lose marks.

– Security, territory, and global configuration

Security design starts with organization-wide defaults and role hierarchy, then extends into sharing rules, territory management, and field-level security. The exam tests whether you understand the sequence: get the foundation wrong and no amount of sharing rules will fix it. Territory hierarchies appear in scenarios with geographic or product-based segmentation. Multi-currency and multi-language configuration is tested in the context of a global rollout, and the question is usually about what needs to be enabled when, not whether to enable it at all. Candidates lose marks by choosing a sharing rule when the requirement calls for a role change, or by configuring territory assignment without understanding how it interacts with account ownership.

– Process design and sprint planning

Designing the future state process means taking a set of requirements and producing a flow that users can actually follow. The exam wants you to know when to simplify a process versus when to accommodate complexity, and how to identify which Agentforce modules support which outcomes. Sprint planning appears as user story prioritization: given dependencies and story size, which stories belong in which sprint. The trap is prioritizing by business value alone and ignoring technical dependency. A high-value story that depends on three others doesn't go in sprint one. You also need to recognize when a story is too large and needs to be split, and when a dependency is a blocker versus a nice-to-have.

– Data migration strategy

Data migration strategy is about sequencing, referential integrity, and knowing what to migrate when. The exam will describe a legacy system landscape and ask you to identify the correct load order or the right approach to preserve relationships. The common mistake is loading child records before parents, or failing to account for lookup fields that reference records not yet in the system. You also need to know when to migrate data in phases versus all at once, and how to validate data quality before andAfterTrigger the load. This is tested with scenarios that describe data volumes, system constraints, and business timelines, then ask you to choose the strategy that balances all three.

How Define/Design is tested

With 42 percent of the exam, Define/Design appears in roughly four out of every ten questions. The items are scenario-heavy: you'll read a paragraph describing a business requirement, then choose the design decision that best meets it. The exam punishes over-engineering and under-engineering equally. Choosing a complex solution when a standard feature would work costs you the mark, as does choosing a simple solution that ignores a stated requirement. Security questions often layer multiple constraints: role hierarchy, sharing rules, and field-level security all in one scenario. The correct answer is the one that satisfies every constraint, not just the most obvious one. Data model questions require you to know the Financial Services Cloud object model well enough to recognize when a requirement maps to an existing object. Migration questions test sequencing and referential integrity under time pressure. Candidates lose marks by skipping a step in the design process or by choosing an answer that sounds right but doesn't scale.

Delivery is the heaviest topic at 46 percent, which means nearly half the exam tests whether you can turn a design into a working system. This is where you configure objects, provision users, set up security, build automation, and deploy the components that make Agentforce Financial Services functional. The coverage is broad: initial setup, user interfaces, sharing rules, integration prep, reporting, automation tooling, ARC, householding, rollups, and lead management all appear here.

– Setup, users, and permissions

Initial setup covers the steps you take after the org is provisioned: enabling Financial Services Cloud features, configuring company settings, and setting up the foundational data required before users log in. User provisioning means creating profiles, permission sets, and permission set groups, then assigning them correctly so users see what they need and nothing more. The exam tests whether you know the order: profiles set the floor, permission sets extend access, and permission set groups bundle them. You also need to know when to use a custom profile versus cloning a standard one, and when to use a permission set versus changing the profile. Candidates lose marks by granting too much access or by choosing a permission set when the requirement calls for a profile change.

– Security, sharing, and integration configuration

Sharing rules appear again in Delivery, but now the focus is on deployment: writing the rule, testing it, and confirming it behaves as expected in a live org. The exam will describe a security requirement and ask you to choose the correct sharing rule type and configuration. The trap is choosing criteria-based sharing when owner-based sharing is required, or vice versa. Integration configuration means setting up the fields that external systems will map to, creating integration users with the right permissions, and ensuring API access is enabled where needed. You need to know which fields are required for common integrations and how to configure an integration user so it has enough access to write data but not enough to become a security risk.

– Objects, fields, reporting, and automation

Configuring objects and fields means creating custom fields, setting field-level security, and ensuring picklist values align with business processes. The exam tests whether you know when a field should be required, when it should be read-only, and when it should be hidden from certain profiles. Reporting and dashboards are tested through scenarios that describe success criteria, then ask you to identify the correct report type, filters, and grouping. The mistake is choosing a report type that doesn't include the necessary objects or choosing a dashboard component that can't display the required metric. Automation questions ask when to use Flow versus OmniStudio, when to use a record-triggered flow versus a scheduled flow, and when automation is the wrong choice entirely.

– ARC, householding, rollups, and lead management

Actionable Relationship Center, householding, and rollups are core Financial Services Cloud features, and the exam assumes you've configured them in a live org. ARC questions test whether you know how to surface the right relationships and actions in the interface. Householding questions focus on account hierarchy and relationship groups: when to use a household account versus individual accounts, and how to configure rollups so financial data aggregates correctly. Rollups are tested in scenarios where a parent record needs to display summarized data from child records. Lead configuration covers assignment rules, queues, and lead conversion. The exam wants to know whether you can route a lead to the right user or queue based on criteria, and whether you understand what happens to the lead data when it converts.

How Delivery is tested

Delivery carries 46 percent of the exam, so expect nearly half of all items to test configuration and deployment skills. The questions are task-based: given a final design, what do you configure, in what order, and with what settings. The exam punishes configuration errors that would cause downstream problems. For example, setting up a sharing rule before the role hierarchy is correct, or creating a rollup field without ensuring the relationship supports it. Reporting questions require you to know which report types give access to which objects, and how filtering and grouping affect the result set. Automation questions test whether you can choose the right tool for the requirement: Flow, OmniStudio, Process Builder (legacy), or Apex. The trap is choosing the tool you know best rather than the tool the requirement calls for. ARC, householding, and rollup questions assume hands-on experience. If you haven't configured these features in an org, the scenarios will feel abstract and the answer options will all seem plausible. Candidates lose marks by choosing answers that would work in a generic Salesforce org but ignore Financial Services Cloud-specific behavior.