Explanation:

Financial Deal Object: This is the industry-standard FSC object designed specifically for corporate and investment banking (CIB). It is separate from the standard Opportunity object, allowing for a cleaner separation of high-stakes deal data from general sales pipelines.

Compliant Data Sharing (CDS): This feature is specifically designed to handle "Wall" requirements in investment banking. In a standard Salesforce sharing model, managers in the Role Hierarchy automatically gain access to records owned by their subordinates.

Hierarchy Bypass: When CDS is enabled for the Financial Deal object, Role Hierarchy-based sharing is disabled by default for that object. This ensures that only the record owner and the specifically assigned Participants (in this case, the trusted analyst) can view the sensitive data. Users up the management chain will not have access unless they are explicitly added as participants.

Why Other Options are Incorrect

Option A: Manual sharing does not block the Role Hierarchy. Managers would still automatically see any record their subordinates can access.

Option C: While Restriction Rules can narrow access, they are not the primary industry-standard tool for managing deal participation in FSC. CDS is the purpose-built framework for this scenario and provides a better audit trail for compliance managers.

Option D: While CDS can be enabled for the Opportunity object, the Financial Deal object is the preferred architectural choice for investment banking in 2026 as it provides better support for deal-specific metadata and lifecycle management. [2]

References for 2026
Control Access to Records with Compliant Data Sharing
Salesforce Help: Create and Manage Financial Deals

Explanation:

In Salesforce Financial Services Cloud with the Intelligent Need-Based Referrals and Scoring managed extension package installed, referral tracking uses the standard Lead object with specific record types, including the out-of-the-box Referral record type. To support a new type of referral requiring different fields (e.g., specialized data for partner referrals, employee referrals, or affinity programs), the administrator must extend the existing referral functionality without creating a custom object.

The three required steps are:
B. Create a new record type 'Referral' on the Lead object: Create a new record type on the Lead object (e.g., "Partner Referral" or "Employee Referral"). This allows different page layouts and required fields specific to the new referral type.

A. Assign the record type to users: Assign the new record type to the appropriate profiles or permission sets (via Record Type Settings) so users can select and create leads with this record type.

C. Create a new referral record type mapper record: In the Referral Record Type Mapper custom setting/metadata (provided by the managed package), add a mapping for the new Lead record type to the Referral object/process. This ensures the new record type is recognized as a referral, enabling scoring, referral-specific fields, dashboards, and incentive tracking.

These steps maintain integration with FSC's referral features (e.g., scoring, performance reports) while allowing field-level customization via page layouts.

Why not the others?
D: Incorrect — Creating a custom Referral object breaks the out-of-the-box Intelligent Referrals functionality (scoring, dashboards, conversion). FSC uses the Lead object for referrals.

E: Updating the Lead page layout is necessary for the new fields but is not sufficient alone—the record type and mapper are required to properly classify and process the new referral type.

References:
Salesforce Help & Trailhead: "Intelligent Need-Based Referrals and Scoring" (covers adding new Lead record types for referral variations and configuring the Referral Record Type Mapper).

FSC Managed Package Documentation: Referral Record Type Mapper ensures custom Lead record types participate in referral processes.

Accredited Professional exam resources: Common multi-select question testing extension of referral types via Lead record types + mapper + assignment.

Explanation:

This question focuses on the FSC-specific tool of Custom Field Sets and how to apply them within the Lightning App Builder to tailor the user experience for specific roles (Wealth Managers) without disrupting others.

Why B is Correct:
The first step is to create a Custom Field Set that contains the fields most relevant to the Wealth Managers' workflow. This is a non-invasive customization that groups fields logically. Crucially, creating it "solely for the Wealth Managers" implies it is designed for their specific use case, separate from other roles like Investment Bankers. This is the foundational object for the customization.

Why C is Correct:
The Financial Summary component is a standard, key component in FSC's Financial Account page layouts and Lightning pages. Assigning the custom field set to this specific component is how you surface those tailored fields directly in the context where Wealth Managers need them, boosting productivity by putting critical data front and center.

Why E is Correct:
More broadly, Custom Field Sets can be assigned to various Lightning components (like the Financial Account List or Client Profile component) that support them. This step ensures the customization can be deployed flexibly across different pages in the Lightning Experience, wherever it enhances the Wealth Managers' view.

Why A is Incorrect:
Creating a new type of person account is a significant, architectural data model change. It is not a "customization" for user productivity in this context; it's a complex development project with broad implications for data integrity, sharing, and reporting. It does not directly address the need to tailor the UI for a specific user group.

Why D is Incorrect:
Permission Sets control user access to objects, fields, and features. A Custom Field Set is a layout/UI tool, not a secured object. You do not assign a Field Set's permissions; you assign the Field Set itself to a component. Furthermore, assigning it to "all users" contradicts the goal of customizing the experience specifically for Wealth Managers.

Reference:
Salesforce Financial Services Cloud implementation focuses heavily on role-specific page layouts using Lightning App Builder. The Custom Field Set feature is a primary method for creating reusable, role-based field groupings. The official Financial Services Cloud Consultant Guide and Lightning Experience Customization modules cover using Field Sets with standard FSC Lightning components like the Financial Summary to tailor the client workspace.

Explanation:

Intelligent Need-Based Referrals and Scoring is a native FSC capability that helps bankers prioritize referrals by automatically scoring them based on client needs, likelihood of success, and other criteria.

A. Referral Approval Processes – While referral approvals are part of workflow management, they don't inherently help prioritize or identify the "most promising" referrals.

B. Intelligent Need-Based Referrals and Scoring – Correct. This FSC feature uses data and rules to score and rank referrals, helping bankers focus on high-potential opportunities. It's specifically designed to increase referral conversion rates through intelligent prioritization.

C. Einstein Referral Scoring for Financial Services Cloud – This is a distractor. While Einstein AI capabilities exist in Salesforce, the specific feature name is "Intelligent Need-Based Referrals and Scoring." There isn't a separately named "Einstein Referral Scoring" feature in core FSC.

D. Referral Routing Rules – These help direct referrals to appropriate bankers but don't provide scoring or prioritization intelligence about which referrals are most promising.

References:
Salesforce Help: "Intelligent Need-Based Referrals and Scoring" – describes how this feature analyzes client data to score and prioritize referrals.

Financial Services Cloud Release Notes: "Increase Referral Conversion with Intelligent Scoring" – explains the business value of this capability.

FSC Implementation Guide: "Set Up Referral Scoring" – provides configuration steps for enabling referral prioritization.

Key Concept:
FSC includes industry-specific intelligence features like referral scoring that go beyond basic CRM functionality. This capability uses client data (financial holdings, life events, interactions) to automatically assess referral quality, helping bankers focus on high-value opportunities rather than treating all referrals equally.

Explanation:

Highly Capable Forms (A): The Discovery Framework is deeply integrated with OmniStudio. This allows developers to use OmniScripts to build complex, branded forms that include advanced branching logic and real-time integrations with external systems (such as credit bureaus or KYC databases) to validate responses during the onboarding process.

Question Structures (D): The framework allows for both standard questions (single data points) and hierarchical/branching questions. Hierarchical questions enable "conditional logic" within the assessment; for example, if a customer answers "Yes" to having foreign assets, the form can dynamically surface a sub-set of more detailed questions regarding those assets.

Archiving (E): To maintain compliance and historical accuracy without cluttering the active user interface, the Discovery Framework allows administrators to archive questions. This ensures that if a regulatory question changes, the old version is preserved for audit purposes while the new version is deployed to active onboarding flows.

Why Other Options are Incorrect:
Option B: This is incorrect. Discovery Framework forms (via OmniScripts) are fully compatible with and frequently deployed to Experience Cloud (Communities) to allow customers to self-onboard.

Option C: This is incorrect. The Discovery Framework is built primarily on OmniStudio (OmniScripts and DataMappers), not standard Salesforce Flow. While it can interact with Flow, its core engine is OmniStudio.

References:
Salesforce Help: Discovery Framework in Financial Services Cloud
Trailhead: Gather Information with Discovery Framework