An exact management firm that is moving to Subadvisor from its old CMM wants to be able to bring over its client data on drivers ' licenses and passports. Which Financial Services Cloud object should a consultant recommend?
Correct 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.
AP-208 Exam Question 2
A financial services company would like its users to be able to relate two business accounts. What should the administrator configure to meet the requirement?
Correct Answer: B
Relationships between two business accounts are modeled through Account-Account Relationships, with reciprocal relationship definitions specifying the role each account plays relative to the other. Therefore, the administrator should create the appropriate Account Reciprocal Role rather than simply adding an arbitrary value to a relationship-object picklist. Salesforce Financial Services relationship modeling supports connections among households, businesses, trusts, professional organizations, and other entities. Reciprocal roles describe the meaning of each side of a relationship-for example, Proprietor and Business, or another organization-specific pair. Salesforce provides commonly used reciprocal role records and permits administrators to configure additional roles when the packaged options do not represent the organization ' s business relationships. The Account-Account Relationship object is the structural record that relates business accounts, while the relationship-role definition supplies the semantics of that relationship. Account-Contact and Contact reciprocal roles apply to relationships involving contacts or individuals, so they do not satisfy a two-business-account requirement. The proper configuration is therefore a new Account Reciprocal Role.
AP-208 Exam Question 3
Cumulus Bank has implemented Compliant Data Sharing in Agentforce Financial Services. Which two things happen when an opportunity record that has opportunity participants with associated share table entries is set to Private?
Correct Answer: A,C
Compliant Data Sharing has specific behavior when an Opportunity is changed to Private. A private Opportunity cannot be shared through Compliant Data Sharing, so Salesforce removes the sharing entries that previously granted participant-based record access. Salesforce documents that when an Opportunity contains Opportunity Participants with associated share-table records and the Opportunity is made Private, the share-table records are deleted. However, the Opportunity Participant records themselves remain in Salesforce. This distinction is important because the participant record represents the business relationship or participation assignment, while the share-table record represents the actual access grant generated by Compliant Data Sharing. Setting the Opportunity to Private removes the access mechanism without automatically destroying the participant data. Salesforce recommends removing participants before making an Opportunity private when appropriate. If an Opportunity is subsequently made shareable again, the participant may need to be recreated or toggled inactive and then active so that the required sharing entry is regenerated. Therefore, manual deletion of the share-table entries is unnecessary. Salesforce performs that cleanup automatically, while preserving the underlying participant records.
AP-208 Exam Question 4
Culmus Insurance has a franchise business model with a large number of franchisees who operate independently but report to regional managers who are Cumulus employees. The company would like the franchise owners and their employees to have access to the Cumulus Salesforce Financial Services Cloud (FSC) instance. The company plans to use the Role Hierarchy and sharing rules to implement this. What should the architect at Cumulus Insurance be aware of for this solution?
Correct 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.
AP-208 Exam Question 5
Salesforce provides a robust set of automation features to help save time and resources. For example, a system administrator can use Flow Builder to automate most of an organization ' s repetitive business processes. Which use case is a suitable fit for Flow Builder?
Correct Answer: A
A Screen Flow created in Flow Builder is specifically designed to collect information interactively from users. Administrators can present screens containing inputs, choices, record fields, instructions, and other components and then use the submitted information to query, create, update, or otherwise process Salesforce data. Salesforce supports several standard methods for distributing a screen flow to internal users. A flow can be embedded directly in a Lightning page, started through a button or action, exposed through a URL, or surfaced through supported Lightning components. This directly matches the requirement in option A. The remaining options correspond more closely to other automation capabilities. Very-large-scale operations can require other asynchronous or batch-processing approaches when Flow execution limits are inappropriate. Personalized recommendations can use dedicated decisioning or Next Best Action capabilities. Coordinating several flows across teams and individuals is characteristic of Flow Orchestration, which provides stages, steps, and work items rather than a standard standalone Flow Builder screen-flow use case. For Agentforce Financial Services implementations, Screen Flow is particularly useful for guided internal processes such as identity verification, customer servicing, structured intake, and other processes in which an employee must enter information through a controlled user interface.