Salesforce Accredited Agentforce Financial Services Professional AP-208 Exam Questions

Answer : B

Salesforce applies platform limits to the number of sharing rules configured for an object. The standard allocation is 300 total sharing rules per object, including owner-based and criteria-based rules. This limitation matters when designing a franchise architecture because creating separate sharing rules for every franchise, region, or user population can result in an unnecessarily complex sharing model and eventually approach platform limits. Architects should prefer scalable mechanisms such as roles, public groups, role-and-subordinate relationships, sharing sets or appropriate Experience Cloud sharing constructs, and criteria-driven sharing where those mechanisms meet the security requirements. The default total sharing-rule limit can in some circumstances be increased through Salesforce Support, but the standard architectural limit tested here is 300 rules per object. A user occupies one role in Salesforce's role hierarchy, not multiple simultaneous roles. Browser selection is unrelated to the fundamental role-and-sharing architecture. Public groups are supported as reusable sharing targets, but the stated 1,024 limit is not the relevant restriction identified in this scenario. Therefore, the architect must account for the per-object sharing-rule allocation when designing a large franchise access model and should avoid a design that depends on a separate rule for every franchise unless absolutely necessary.

Answer : A, B

A system-to-system API integration should operate through a dedicated integration user whose access is limited to the permissions required by that integration. Salesforce recommends creating a distinct user for each integration because this improves traceability, isolates credentials, enforces least privilege, and limits the impact if an integration account is compromised. The integration identity should also be configured for API-only access. An API-only profile prevents interactive Salesforce UI access while allowing the external system to authenticate and perform permitted API operations. Current Salesforce architecture also provides the Minimum Access - API Only Integrations profile for the Salesforce Integration user license. The required object, field, and system permissions should then be granted through appropriately scoped permission sets or permission-set groups. This provides tighter control than assigning the System Administrator profile. Options C and D violate the principle of least privilege. A System Administrator profile provides substantially more capability than a risk-control integration should require, and changing that profile to API-only would also be inappropriate because it affects users assigned to that profile. The correct security pattern is therefore a dedicated Integration User with API-only profile access, plus narrowly tailored permission assignments for the objects and API operations required by the external risk-control system.

Answer : D

A formal field mapping should define how each source-system data element corresponds to its destination field in Salesforce. This is a fundamental integration-design control because it creates an explicit contract between the external data structure and the Salesforce object model. For each source attribute, the mapping identifies the appropriate destination object and field, transformation requirements, data type, lookup behavior, and any required validation. Salesforce uses this same principle throughout its data-import and integration tooling. Field mappings define which input columns or external-system fields correspond to Salesforce fields, and administrators should review mappings before records are loaded. Data Loader batch processing similarly uses a field mapping file to map input-file columns to corresponding Salesforce object fields. Using a CSV and Data Loader would describe one particular import mechanism rather than the integration design required by the scenario. A junction object is appropriate for modeling many-to-many relationships, not simply for ensuring incoming attributes reach the correct fields. Custom metadata can support configurable integration behavior, but it is not inherently required merely to define source-to-target field correspondence. A documented field mapping provides the precise source-to-target definition necessary for reliable external-system integration.

Answer : D

Interest Tags are specifically designed to capture customer interests, needs, preferences, and prospecting opportunities in Agentforce Financial Services. They are therefore the appropriate capability for storing information such as a client's hobbies. Salesforce gives hobbies such as golf and skiing as examples of information that can be represented using Interest Tags on person accounts. Interest Tags can also represent investment interests and other topics discovered during customer interactions. Interest Tags can be organized into hierarchical Tag Categories, enabling institutions to establish a controlled taxonomy. For example, an organization could create a Hobbies category and define tags such as Golf, Skiing, Sailing, or Travel. Because this vocabulary is structured, organizations can report across clients and identify common themes or potential engagement opportunities. Topics provide the underlying platform capability and are a prerequisite for Interest Tags, but Topics alone are not the Financial Services feature designed for this client-interest requirement. Alerts communicate conditions requiring attention rather than persistent customer interests. Interest Tags therefore provide the Financial Services-specific functionality required for tracking hobbies and supporting personalized client engagement.

Answer : C

The appropriate object is Identity Document. Drivers' licenses and passports are formal identity credentials and should be represented using a structured identity-document model rather than as generic checklist or received-document records. Salesforce uses Identity Document terminology throughout its identity-document processing capabilities. Intelligent Document Reader and related onboarding capabilities can extract structured information from uploaded passports and driver's licenses by treating them as identity documents. Modeling identity credentials explicitly allows an implementation to distinguish personally identifying documentation from ordinary supporting documents used in onboarding, underwriting, servicing, or compliance workflows. Identity-document information can then participate in identity verification, KYC, onboarding, and related Financial Services processes. A Document Checklist Item serves a different purpose: it tracks whether a required document has been requested, received, reviewed, or otherwise processed as part of a checklist. It does not itself represent the customer's identity credential as the principal identity-data entity. Similarly, generic received or resolved document structures address document workflow rather than the semantic representation of the identity credential. Therefore, when migrating customer information associated with passports and driver's licenses, Identity Document is the Financial Services object aligned to the identity-document use case.

Answer : C

The relationship structure in option C reflects the essential Agentforce Financial Services household-modeling rules. Rachel's own household is her Primary Group, and Rachel is its Primary Member. Her spouse, Nigel, is another household member related through the spouse relationship. The Addams Charitable Trust is represented as a related business account, while the attorney is represented as a related professional contact.

Salesforce household modeling uses this same conceptual structure. A customer such as Rachel is represented by a Person Account and can be marked as both the household's Primary Member and as having that household as the Primary Group. A spouse is added as another group member and is connected through an explicit spouse relationship. A trust is represented by a Business Account and related to the household through an account relationship.

A person can participate in multiple groups but can have only one Primary Group because that designation determines the household to which eligible financial information and activities roll up. Rachel can therefore belong to the Symonds household as a beneficiary while retaining the Addams household as her Primary Group.

This structure provides the advisor with a complete view of Rachel's immediate household, family affiliations, trust relationship, and professional connections.

Answer : C

Action Plans and Action Plan Templates are designed for repeatable, controlled business processes that contain tasks and supporting-document requirements. An Action Plan Template defines the standard sequence once, including task ownership, due dates, dependencies, and document checklist items. Each onboarding engagement can then instantiate an Action Plan from that approved template. Salesforce positions Action Plans as a mechanism for capturing repeatable tasks and automating task sequences so that teams execute processes consistently. Action Plans can automatically assign owners and deadlines and provide reporting for monitoring progress and compliance. The feature also supports Document Checklist Items, which is directly relevant to the KYC requirement. Action Plans and templates manage repeatable manual work, while Document Checklist Items enable reviewers to track required documentation and its approval status. Chatter reminders provide communication but do not establish a controlled repeatable process. A custom trigger would unnecessarily duplicate declarative Financial Services capabilities and increase maintenance. Generic flow templates may automate individual operations but do not provide the same reusable combination of predefined tasks, owners, dates, document requirements, tracking, and reporting. An Action Plan Template therefore provides the appropriate standardized control for ensuring onboarding tasks are consistently performed.