Explanation:

In Financial Services Cloud (FSC) Action Plan Templates, when configuring a task, the administrator can choose assignment logic for the task owner. The available options include Action Plan Creator, Specific User, Role (which can be resolved to account/opportunity team roles or general roles), and Queues.
To have the task picked up by the next available Advisor, the best approach is to assign it to a Queue (e.g., an "Advisor Queue" containing multiple Advisor users). Queues allow group ownership of tasks, enabling any queue member to claim and assign the task to themselves—ideal for load balancing and ensuring the next available person handles it.

A. Action Plan Creator: Assigns to the user who launches the action plan—not suitable for round-robin or next available.
B. Specific User: Assigns to one fixed user.
C. Account Team: This refers to assigning via Account Team Roles (e.g., Primary Advisor), which resolves to a specific team member on the record, not a pool for next available.
D. Role: Typically resolves to the action plan creator if the role is shared, or a specific person; not designed for queue-like distribution.

Queues require initial setup (e.g., enabling queue assignment for tasks via guided setup in FSC), but they directly support the "next available" scenario through manual claiming or automation (e.g., assignment rules).

References:
Trailhead: Understanding Action Plans in Financial Services Cloud ("assign each task... to a person, a role, a queue, or the action plan creator").
FSC Documentation/Release Notes: Supports assigning Action Plan tasks to queues for group handling.
Hello Kloud & other FSC resources: Confirms queues for tasks needing distribution among users like advisors.

Explanation:
This question focuses on the core Mortgage Data Model within FSC and which objects are central to tracking the sales/funding pipeline and integrating with external Loan Origination Systems (LOS). The pipeline is about tracking the progression of a potential loan.

Why B is Correct:
The Opportunity object is the primary Salesforce object for tracking a sales pipeline. In a mortgage context, the Opportunity represents the loan application pipeline—from pre-qualification to underwriting to closing/funding. It tracks the stage, amount, probability, and close date. Integrating with an external LOS would involve syncing the status and details of the loan application to/from this object.

Why D is Correct:
The Account object represents the client (as a Person Account or Household) and potentially the property (as a Commercial/Business Account). The client is the central entity to which the mortgage opportunity is related. Accurate client data is foundational for any loan process and integration.

Why E is Correct:
The Financial Account object is used to represent the actual loan product itself (e.g., the mortgage) once it is originated/funded. It tracks the financial details like balance, terms, and payment history. When planning an integration, the flow often involves an Opportunity converting to a Financial Account upon closing. The Financial Account is the system of record for the holding post-origination.

Why the Other Options Are Incorrect:
A (Assets & Liabilities): While Assets & Liabilities are critical data points for loan underwriting (and are part of the broader FSC data model), they are typically attributes or child records of the Financial Account or related to the Account. They are not the primary objects for tracking the moving pipeline; they are more static financial data points used in qualification.
C (Case): The Case object is used for customer service and inquiry tracking, not for tracking a sales or origination pipeline. It would be used for post-origination servicing issues, not for the pre-funding application pipeline mentioned in the scenario.

Reference:
The FSC Mortgage Data Model documentation and implementation guides center on the Account (client), Opportunity (application pipeline), and Financial Account (funded loan) objects as the core triad for loan origination. Integration with LOS platforms focuses on synchronizing data across these key objects to maintain a single source of truth in Salesforce for the loan lifecycle.

Explanation

Option A (✅): Register a subdomain using the My Domain wizard and then deploy it
Correct. The admin must go to Setup → My Domain, register a custom subdomain, test it, and then deploy it to all users. This is the official process to enable My Domain.

Option B (❌): Open a case with Salesforce Support
Incorrect. My Domain can be enabled directly by the admin in Setup. No support case is required.

Option C (❌): Enable Communities
Incorrect. Communities require My Domain, but enabling Communities does not itself enable My Domain.

Option D (❌): Go to Custom Settings and edit the Industries Settings
Incorrect. Industries Settings are unrelated to My Domain.

📚 Reference
Salesforce Help: Set Up My Domain
FSC Implementation Guide: My Domain is required for Lightning Components, FSC features, and secure login policies.

📝 Key Takeaway
To enable My Domain:

Use the My Domain wizard in Setup.
Register a subdomain, test it, and deploy it.

This unlocks FSC Lightning Components and other advanced features.

Explanation:

✅ FSC options to view and update relationships (Account–Account, Account–Contact, Contact–Contact)

Financial Services Cloud (FSC) provides multiple relationship-centric UI tools out of the box to help bankers visualize and manage complex client relationships.

A. Actionable Relationship Center — ✅ Correct
The Actionable Relationship Center (ARC) is the primary FSC workspace for viewing and managing:

Account–Account
Account–Contact
Contact–Contact relationships

It allows users to view, create, edit, and act on relationships from a single place.
This is the most comprehensive FSC relationship management tool.

C. Relationship Map — ✅ Correct
The Relationship Map provides a visual, graph-style view of relationships between people and businesses.
Users can view and update relationship roles and understand how clients are connected.
It supports all major FSC relationship types and is frequently tested on the exam.

D. Group Members Component — ✅ Correct
The Group Members component is used within Households and Business Groups.

It allows users to:

View members of a group
Add or remove people and businesses
Update roles within the group

This directly supports Account–Contact and Account–Account relationships in a grouped context.

❌ Why the other options are incorrect

B. Family Members Component — ❌ Not correct
FSC does not provide a standard component named Family Members.
Household relationships are managed via Groups, not a standalone family component.

E. Life Events Component — ❌ Not correct
The Life Events component tracks milestones (marriage, retirement, home purchase).
It does not manage or edit relationship records.

📌 Exam takeaway
If the question asks about relationship visualization or management, think:

Actionable Relationship Center
Relationship Map
Group Members

These three cover viewing and updating relationships in FSC.

Explanation:

Financial Services Cloud (FSC) provides out-of-the-box Lead & Referral Management capabilities designed for need-based and intelligent referrals in retail banking, wealth management, and insurance scenarios. The standard features include:

A. Referral Conversion
Out-of-the-box support to convert a referral (modeled as a Lead) directly into an Opportunity, Account, or other object, with field mapping and status updates.

B. Assigning a Referral
Manual or rule-based assignment of referrals to advisors, specialists, or queues directly from the referral record.

D. Accepting a Referral
Referral owners can explicitly accept a referral (changing status to "Accepted"), triggering next steps like task creation or notifications.

Why not the others?

C. Round Robin Referral Routing
Not available out of the box. Standard FSC uses basic assignment rules or queues, but round-robin distribution requires custom configuration (e.g., Flow, Apex, or third-party tools).

E. Referral Automated Approvals
Not a standard out-of-the-box feature. While approval processes can be built on Leads or custom referral objects, FSC does not include prebuilt automated approval workflows for referrals.

Reference:
Salesforce FSC documentation and Trailhead modules on "Intelligent Need-Based Referrals" highlight conversion, manual/routine assignment, and acceptance as core out-of-the-box capabilities in the referral lifecycle. Advanced routing (like round-robin) and automated approvals require customization.