Authentic Salesforce Certification Exam AP-208 Questions Answers

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.

Mortgage functionality in Agentforce Financial Services is controlled through the appropriate permission-set and user-access configuration. A user who must create or work with Residential Loan Application records needs access to the mortgage feature and to the mortgage-related objects. Consequently, failure to assign the required Mortgage permissions prevents the consultant from creating the application record.

Salesforce ' s Financial Services setup guidance includes assigning the Mortgage permission set as part of granting users access to mortgage functionality. Salesforce also provides enhanced mortgage permission-set configurations for personas such as loan officers and underwriters.

Current configuration guidance shows that mortgage-oriented permission sets must grant the system permission that licenses the user to access mortgage functionality in Financial Services and must provide the necessary object permissions for Residential Loan Applications and related Loan Applicant and Loan Application objects.

The issue is therefore not resolved by enabling a Residential Loan Application flow or by selecting a user-level Mortgage User checkbox. Nor is there a general Allow Mortgage Access setup switch corresponding to the required user entitlement. Access is established through the prescribed mortgage permissions and associated object-level access.

A Financial Services household can have only one Primary Member. Both Oliver and Macie have Primary Member enabled, which violates this household-modeling rule and causes the configuration error.

Salesforce household guidance states that designating a primary member is optional, but a household can have only one primary member. The primary member commonly represents the principal client or primary relationship within the household. Other members receive roles that describe their relationship to that primary member, such as Spouse or Dependent.

The other settings shown are valid. Multiple members can designate the same household as their Primary Group. Primary Group identifies the household to which a person ' s qualifying records and activities should roll up. A spouse can be a valid relationship role, and multiple household members can have their eligible activities and financial information summarized to the same primary household.

The advisor should therefore retain one individual—typically the principal client—as Primary Member and clear Primary Member for the spouse while leaving the appropriate relationship and Primary Group settings in place.