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.

Explanation:

Why C is correct
In Salesforce Financial Services Cloud, the Referral Dashboards and Reports are not available by default when FSC is installed. To expose these prebuilt dashboards and reports, the Salesforce Admin must install the unmanaged extension package for Intelligent Need-Based Referrals and Scoring.

This extension package delivers:
- Preconfigured Referral dashboards
- Prebuilt Referral reports
- Supporting metadata used by the Intelligent Need-Based Referrals and Scoring feature

Without this unmanaged extension, users will not see the referral analytics even if referrals themselves are enabled.

Why the other options are incorrect
A. Managed extension package ❌
Salesforce explicitly provides the referral dashboards and reports through an unmanaged extension package so admins can customize reports and dashboards. A managed package would restrict customization.

B. Einstein Analytics for Financial Services ❌
Einstein Analytics (now Tableau CRM) is optional and used for advanced analytics. It is not required to access the standard referral dashboards and reports.

D. Salesforce CRM Dashboards ❌
Salesforce CRM Dashboards are a platform feature, but they do not include FSC referral dashboards unless the referral extension package is installed.

References:
Salesforce Help – Intelligent Need-Based Referrals and Scoring

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:

Why it's correct: A field mapping file (or a data mapping specification) is the standard blueprint used in systems integration. It serves as the bridge between the external system's schema and the Salesforce object's API names.
The Process: The consultant defines that External Field $X$ maps to Salesforce Field $Y$. This document is then used to configure the middleware (such as MuleSoft, Informatica, or a custom API) to ensure that when the external system sends a payload, the data "lands" in the correct location.
Key Components: A robust mapping file typically includes the Source Field Name, Target Salesforce API Name, Data Type (e.g., String, Boolean), and any required transformations (e.g., converting a "Yes/No" to "True/False").

Analysis of Incorrect Answers
Option [A]: Create a junction object...
Why it's incorrect: A junction object is used within Salesforce to create a Many-to-Many relationship between two objects. It is a data structure tool, not an integration tool. Creating a junction object does not help the external system understand which fields it should be populating.

Option [B]: Ensure custom metadata is configured...
Why it's incorrect: While Custom Metadata can be used to store mapping logic for custom-built Apex integrations, it is a complex, developer-heavy approach. Option D represents the broader, more standard requirement for ensuring data integrity during any integration project.

Option [C]: Use a CSV file... and Data Loader...
Why it's incorrect: The prompt specifically mentions that records will be created through integration with another system, which implies an automated or real-time process. Data Loader is a manual tool for bulk uploads and is not used for ongoing, automated system-to-system integrations.

Reference
Salesforce Developer Guide: Best Practices for Data Integration
Salesforce Help: Data Mapping for Industry Clouds

Explanation:

A. Account Account Relationship object
To connect a household to a related entity like a business (Smith’sShoes), FSC uses the AccountAccountRelation (account-to-account relationship) record. Salesforce explicitly describes this object as representing relationships between two accounts, such as between a household and a business account.

C. Account object – Household record type
In FSC, a Household is represented using the Account object (with a Household designation/record type, depending on your FSC setup). You relate other entities to the household to view the full relationship picture at the household level.

E. Account object – Business record type
The boutique shoe store (Smith’sShoes) is an organization/entity, so it should be represented as a Business Account (Account with a business-type record type). Then it can be related to the household via AccountAccountRelation.

Why the other options aren’t selected

B. Account Contact Relationship object
This is mainly for linking an individual/person account (contact) to a business account (e.g., employer/decision maker). It’s useful, but the question is specifically about mapping the household ↔ business relationship to reflect household-level relationships; that’s handled by Account-Account Relationship.

D. Contact object
Not required to represent the store itself (that’s an Account), and the client is already modeled as a Person Account (which has an underlying contact).