Explanation:

In Financial Services Cloud, Person Life Event records track important client milestones. To ensure data integrity for “once‑in‑a‑lifetime” events, Salesforce provides a native configuration option at the picklist level.

Option A is incorrect: While an Apex trigger could technically enforce this, it is not the recommended or simplest approach. Using native declarative features is preferred over custom code when available.

Option B is correct: The Event Type field on the Person Life Event object is a picklist. On the picklist entry itself (e.g., “Birth”), there is a Unique checkbox. When checked, Salesforce prevents duplicate Person Life Event records with that same event type for the same person. This is the standard, out‑of‑the‑box way to enforce one‑time life events.

Option C is incorrect: Removing creation access is too restrictive and impacts business process. The goal is to prevent accidental duplicates, not eliminate the ability to record these events.

Option D is incorrect: A validation rule could be written, but it would be a custom solution. The native Unique checkbox is simpler to maintain, performs better, and is specifically designed for this use case.

References:
Salesforce Help: “Create Life Event Picklist Values” – explains that marking a picklist value as Unique prevents users from creating more than one life event of that type for the same person.

Financial Services Cloud Administrator Guide: “Manage Person Life Events” – documents the configuration of life event types and the purpose of the Unique checkbox.

Key Concept:
Financial Services Cloud includes specialized objects like Person Life Event with built‑in mechanisms (such as unique picklist values) to support financial‑services‑specific data integrity requirements.

Explanation:

Person Accounts as Accounts
In the Financial Services Cloud data model, when using Person Accounts, every individual client is modeled as an Account record with the IsPersonAccount field set to true.

Relationship Modeling
Relationships between these clients, such as Spouse, Business Partner, or Child, are managed using a junction object designed to link two Account records together: the Account Account Relationship object (API name: AccountAccountRelation).

Custom Fields for Reporting
To track specific details about how two people are related, such as a partnership start date or custom reporting metrics, the custom fields must be added to this junction object. This is because the data describes the relationship itself, not attributes of either individual client.

Why Other Options are Incorrect

A. Account Contact Relationship
This object is primarily used in the Individual Data Model, where a client is modeled as a Contact linked to a generic Account record, such as a Household or Business. It is not the correct object when using the Person Account model.

B. Contact-Contact Relationship
This object is also specific to the Individual Data Model, where relationships link two Contact records rather than Account records.

C. Person Account
Custom fields on the Person Account object track attributes of the individual person, such as hobbies or addresses, not the relationship between two people.

Explanation:

Why B is correct

In Financial Services Cloud, Commercial Banking features are enabled for end users by assigning the packaged FSC permission sets / permission set licenses (i.e., user access is granted via permission sets). This includes access to the Commercial Banking Console Lightning app and related feature permissions. Salesforce’s FSC guidance for Commercial Banking explicitly points admins to use permission sets to grant access.

Why the other options are wrong

A. Update Industries Settings…
Industries settings can control certain org-level behaviors, but user access to the console/app and features is handled through permission sets, not just an Industries setting toggle.

C. Update the user profiles…
Profiles can grant object access, but FSC best practice (and how packaged access is typically delivered) is through permission sets/permission set licenses for incremental feature access.

D. Install the Commercial Banking Managed Package
Installation is required to have the functionality in the org at all, but the question asks what’s required to give users access. That step is assigning permission sets.

Explanation:

To use the OmniScript metadata type in the context of Financial Services Cloud (AP-208 focus), the org must have Discovery Framework enabled—because OmniScripts used for Discovery Framework rely on the Discovery Framework metadata enablement setting (often referenced as “Discovery Framework Metadata Enabled”).

Why A is correct
Salesforce’s FSC documentation notes that when you deploy/use OmniScripts of the “Discovery Framework” type, you must enable the Discovery Framework metadata setting in the org.
Discovery Framework is the FSC capability that uses OmniStudio-style guided processes (OmniScripts) to collect/validate client data via digital forms.

Why the other options are not correct
B. Lightning Experience for Financial Services Cloud: Lightning is required for many UI experiences, but it’s not the org switch that enables the OmniScript metadata type for Discovery Framework usage.

C. Custom Domain: relates to My Domain / URL branding and security; unrelated to enabling OmniScript metadata.

D. Einstein Relationship Insights: Einstein feature for relationship intelligence; unrelated to OmniScripts/Discovery Framework metadata.

Explanation:

Financial Services Cloud offers tiered licensing to control costs. The Financial Service Cloud Basic license is the restricted, lower-cost license designed for users who need limited FSC access, such as bank tellers or customer service agents.

A. Financial Services Cloud Standard: This is not a standard FSC license name. The primary FSC license types are FSC (full) and FSC Basic (restricted).

B. Client Segmentation: This is an FSC feature or capability, not a license type.

C. Financial Service Cloud Basic: Correct. FSC Basic is the restricted license that provides access to core FSC objects (Household, Financial Account, etc.) but excludes advanced features like Action Plans, Goals, or certain advisor tools. It is cost-effective for frontline staff who need limited access.

D. Financial Service Cloud Extension: This is a permission set that grants access to extended FSC features (e.g., Interest Tags, Need-Based Referrals), but it is not a license type. Extension permission sets are assigned to users who already have an FSC or FSC Basic license.

References:
Salesforce Help: “Financial Services Cloud Licensing” – explains the difference between FSC (full) and FSC Basic licenses.

FSC Implementation Guide: “Assign FSC Basic Licenses to Frontline Users” – recommends FSC Basic for tellers, call center agents, and other limited-access roles.

Salesforce Pricing & Packaging: Lists FSC Basic as the restricted, lower-cost license option for financial institutions.

Key Concept:
FSC Basic is the restricted license designed for high-volume, limited-access users such as:

- Bank tellers
- Call center agents
- Back-office operations staff

It provides access to essential FSC data (client profiles, accounts, households) without the full cost of a full FSC license, enabling cost-effective scaling while maintaining a unified client view across the organization.