Salesforce Certified Financial Services Cloud Practice Test - Questions Answers, Page 14

Financial Services Cloud functionality is available from two packages: the managed package and the unmanaged extension packages. The managed package contains most of the Financial Services Cloud functionality, such as custom fields and objects, list views and profiles of clients and households, and administrative configurations. The unmanaged extension packages provide additional functionality that is not included in the managed package, such as:

The Commercial Banking dashboard: This is a dashboard that provides insights into commercial banking activities and performance, such as loan portfolio health, deposit growth, referral pipeline, and customer satisfaction. The Commercial Banking dashboard is included in the unmanaged commercial banking extension package.

Field sets that configure how fields display in the client and household profiles: These are field sets that determine which fields are displayed in different sections of the client and household profiles, such as Client Overview, Household Overview, Client Details, Household Details, etc. The field sets are included in the unmanaged extension package.

Compliant Data Sharing (CDS) is a feature of Financial Services Cloud that allows granular control over access to sensitive data in Account and Opportunity objects. CDS can help financial services companies comply with regulations and policies that restrict data visibility based on user roles. Some considerations regarding CDS are:

Participant Roles provide another way to grant data access without overwriting sharing behavior from existing sharing features. Participant Roles are custom objects that define the possible roles for users who need access to Account or Opportunity records. For example, a Participant Role can be Advisor, Client, Specialist, or Decision Maker. Each Participant Role has an associated access level that determines what data fields the user can view or edit. For example, an Advisor can have full access to all fields, while a Client can have read-only access to some fields.

Compliance managers and Salesforce administrators can enable CDS for Account and Opportunity objects. CDS is not enabled by default in Financial Services Cloud. To enable CDS, compliance managers or administrators need to create an integration definition record for each object that they want to enable CDS for. An integration definition record specifies the object name, the field name that contains sensitive data (such as Notes), the field name that contains the record owner (such as OwnerId), and the field name that contains the record type (such as RecordTypeId).

Role Hierarchy---based sharing is disabled by default in CDS. Role Hierarchy is a feature of Salesforce that allows users to inherit access to records from their managers or peers in the role hierarchy. For example, if a user has access to an Account record, their manager also has access to that record by default. However, in CDS, role hierarchy---based sharing is disabled by default for Account and Opportunity objects. This means that users do not inherit access to records from their role hierarchy unless they are explicitly granted access through Participant Roles or other sharing features.

Record types are a way to categorize records in Salesforce based on different business processes or requirements. Record types can have different page layouts, picklist values, and business logic. For the Lead object, a financial services company can create different record types to capture different types of leads based on their source, interest, or qualification. Some examples of record types for the Lead object are:

Referral: This record type can be used to capture leads that are referred by existing clients or partners. Referral leads can have fields such as Referrer Name, Referrer Account, and Referral Type to track the source and nature of the referral.

General: This record type can be used to capture leads that are generated from general marketing campaigns or events. General leads can have fields such as Campaign Name, Campaign Source, and Lead Score to track the effectiveness and potential of the marketing efforts.

Retirement Planning: This record type can be used to capture leads that are interested in retirement planning services or products. Retirement planning leads can have fields such as Retirement Age, Retirement Goal, and Current Savings to assess the needs and suitability of the leads.

Multiple currencies is a feature of Salesforce that allows organizations to work with more than one currency in their records, reports, and forecasts. Multiple currencies can help organizations that operate in different countries or regions to manage their financial data in local currencies, while also providing a consistent view of the data in a single corporate currency. Advanced currency management is a feature of Salesforce that allows organizations to track historical exchange rates and apply them to records based on their close date. Advanced currency management can help organizations that deal with fluctuating exchange rates to accurately report on their revenue and performance over time.

To enable and apply multiple currencies, the administrator needs to do the following steps:

From Setup, in the Quick Find, search for Company Information, then select Company Information.

Click Edit.

Check Activate Multiple Currencies.

Click Save.

From Setup, in the Quick Find, search for Manage Currencies, then select Manage Currencies.

Click Enable Advanced Currency Management.

Click Save.

Set the corporate currency for the corporate headquarters office by editing the currency field on the account record.

Process Builder and Screen Flows are two features that can be used to design a business process for identity verification. Process Builder is a tool that allows you to automate business processes by creating workflows that trigger actions based on certain criteria. Screen Flows are a type of flow that guide users through a series of screens to collect and update data. You can use Process Builder to launch a Screen Flow when a customer contacts the bank, and use the Screen Flow to capture and verify the customer's identity information.

Reference: [Process Automation], [Screen Flows]

Feed tracking has to be enabled for the Action Plan object in order to add a Chatter component to the Action Plan Lightning record page. Feed tracking allows you to see updates on records in Chatter feeds. You can enable feed tracking for custom objects, such as Action Plan, from the setup menu. Once feed tracking is enabled, you can add Chatter components, such as Feed or Publisher, to the record page using the Lightning App Builder.

Reference: [Feed Tracking], [Chatter Components]

Identification Document is the Financial Services Cloud object that should be recommended for storing client data on drivers' licenses and passports. Identification Document is a standard object that represents a document that verifies a person's identity, such as a driver's license, passport, or national ID card. You can create identification document records for individual clients and link them to their person accounts. You can also store information such as document type, number, issue date, expiration date, and country of issuance.

Reference: [Identification Document Object], [Manage Identification Documents]

The administrator did not assign the Mortgage permission set to the user. The Mortgage permission set is required to access the Residential Loan Application object and its related objects, such as Loan Application Form, Loan Assessment, and Loan Product. Without this permission set, the user cannot create, edit, or view residential loan application records. The administrator can assign the Mortgage permission set to the user from the user detail page in Setup.

Reference: [Mortgage Permission Set], [Residential Loan Application Object]

Interaction Summary is the Financial Services Cloud feature that should be recommended in this scenario. Interaction Summary is a standard object that represents a summary of an interaction with a client or a group of clients. It allows the user to capture meeting notes, specify confidentiality level, link related records, and associate interaction participants. Interaction Summary can be created from the Interaction Summary component on a record page or from the New Interaction Summary action on a list view or related list.

Reference: [Interaction Summary Object], [Create an Interaction Summary]