Salesforce Updated AP-208 Exam Questions and Answers by adeline

Agentforce Financial Services record rollups aggregate qualifying records belonging to members of a Primary Group so advisors can see consolidated household information. Some objects are supported automatically, while others require additional configuration.

Salesforce specifically identifies objects such as Cases, Opportunities, Policies, Claims, and Referrals as requiring additional setup for group-level rollups. To make these records available in the household rollup, the administrator adds the appropriate object value, such as Cases, to the Rollup__c picklist on the Account Contact Relationship object.

When group-level record rollups are enabled, Salesforce stamps qualifying records with the household ' s Primary Group. However, the actual lookup used for this purpose is Household__c, not Rollup__c. The Rollup__c field on Account Contact Relationship controls which object categories should participate in rollup behavior. This distinction makes option B incorrect.

Option D reverses the field purposes: Opportunities should be added as a value to Rollup__c; Household__c is not a picklist used to select rollup categories.

Once correctly configured, the rolled-up records become visible through the appropriate household-level related lists or Financial Services components, providing advisors and insurance personnel with a consolidated view of records belonging to members of the Primary Group.

A Screen Flow is the appropriate declarative solution because the process requires an internal agent to enter information into a guided form and then submit that information to an external service.

Screen Flow provides Screen elements that can capture temporary user-entered values such as the customer ' s full name and the last four digits of the Social Security number. Those values do not have to be stored in Salesforce simply because they are collected during the flow interview. They can remain flow variables used only for the authentication transaction.

Flow Builder can then invoke an external authentication service through an HTTP Callout, External Service action, Apex action, or another supported integration mechanism. The flow can send the supplied identity information, receive the authentication response, evaluate the result, and display an appropriate outcome to the customer service agent.

Screen Flows can also be launched from record-page quick actions, embedded directly on Lightning pages, or exposed through supported service-console experiences.

A custom Lightning web component or Canvas application would introduce unnecessary development for a requirement already supported declaratively. OmniScript is also capable of sophisticated guided interactions, but the requirement as stated maps directly to Salesforce ' s Screen Flow and external-callout capabilities.

The Life Events experience is intended to turn significant customer events into actionable advisor workflows rather than merely display historical information. Within the supplied Financial Services curriculum, the advisor actions represented are Create Lead and Referral, Request Record Approval, and Create Opportunity.

Salesforce ' s Events and Milestones architecture implements this behavior through contextual actions. Administrators can create actions on the Person Life Event object and expose those actions in the expanded event card. This allows an advisor to act immediately when a life event indicates a new service need, sales opportunity, referral opportunity, or internal process requirement.

For example, a life event can signal a need that should become an Opportunity, a requirement that should be routed to another line of business through a Lead or Referral, or an internal decision that requires an approval action. The action is launched in the context of the customer and the life event, helping maintain traceability between the event and the resulting business process.

The exact available actions can be tailored by the organization through configuration. The core design principle is that Life Events should translate customer insight into timely, trackable advisor actions rather than remain passive informational records.

Agentforce Financial Services models referrals through the Lead object, so a requirement for another referral variation should be implemented by creating an additional Lead record type rather than introducing a separate custom Referral object.

The administrator creates a new Lead record type using Referral as the basis, assigns an appropriate Lead Process, activates the record type, and makes it available to the required users. This allows the organization to define different required fields, page layouts, or referral experiences for the new type while remaining within the standard Financial Services referral architecture.

The administrator must then configure Referral Record Type Mapper custom metadata. The mapper connects the new Lead record type to Financial Services referral functionality by identifying the referral record type and enabling the packaged referral components to recognize it.

Assigning the record type to the relevant users is essential because users must have access to the new record type before they can select it during Lead or Referral creation. Updating a page layout may subsequently be useful, but it is not one of the three core configuration steps identified by the referral record-type procedure.

The correct implementation therefore uses the existing Lead and referral architecture: create the Lead record type, assign it to users, and create the corresponding Referral Record Type Mapper record.