Free Salesforce Financial-Services-Cloud Practice Exam with Questions & Answers

To ensure that all users see Person Accounts, but only specific users can view Financial Accounts, the Admin should take the following steps:

Grant users access to the Financial Account object with permission set, which isa collection of settings and permissions that give users access to various tools and functions. The Admin can use permission sets to grant access to the Financial Account object and its fields to specific users or groups of users1.

Change Organization-wide Defaults (OWD) sharing on the ‘Financial Accounts’ object to Private’, which is a setting that determines the baseline level of access that users have to records they do not own or share. By setting the OWD sharing on the ‘Financial Accounts’ object to Private’, the Admin can ensure that only the record owners and usersabove them in the role hierarchy can view the Financial Accounts. Verified References: 1

To give a group of users access to a Financial Deal, you need to share a financial deal record with a group by adding them as participants to the record from the Financial Deal Participants related list. The Financial Deal Participants related list is a custom related list on the Financial Deal object that allows you to add users, groups, or queues as participants of a financial deal.Participants can have different roles and access levels for a financial deal, such as Owner, Collaborator, Viewer, or Approver. By adding a group as a participant, you can grant access to all the members of that group for a specific financial deal. Verified References: : Salesforce Help Article [6] : Salesforce Help Article [7]

To grant restricted accessto users like Bank Tellers who need only limited access to Financial Services Cloud features, the Admin can use Financial Service Cloud Basic permission set license. This license enables user access to a license with contractual restrictions for FinancialServices Cloud and provides access to core objects such as accounts, contacts, leads, opportunities, cases, activities, reports, dashboards, and custom objects. This license also provides access to some Financial Services Cloud features such as Action Plans, Actionable Relationship Center (ARC), Branch Management, Complaint Management, Data Consumption Framework (DCF), Discovery Framework (DF), Document Generation (DG), Groups (Householding), Intelligent Document Automation (IDA), Intelligent Need-Based Referrals and Scoring (INRS), Referral Management (RM), Relationship Builder (RB), Relationship Groups (RG), Relationship Map (RM), Timeline (TL). 

The solution that the consultant should suggest the client explore to improve its clients’ documentation submission and tracking is the Send Documents flow for Retail Banking. The Send Documentsflow for Retail Banking is a prebuilt flow that allows users to send documents requests to clients via email and track the status of the requests in FSC. The flow uses DocuSign eSignature integration to enable clients to sign and return documents electronically. By using the Send Documents flow for Retail Banking, the consultant can help the client streamline and simplify its document management process and improve its customer service agents’ efficiency

The following statements about Action Plans are true:

When you work with Action Plans, you first create Action Plan Templates, which are reusable sets of tasksthat define a common clientprocess1.

Action Plans make it easy to create reports and dashboards, so you can monitor progress and ensure compliance. Users can use standard report types or custom report types to create reports on action plans, action plan templates, action plan items, action plan item templates, and action plan item owners1.

Action Plans can be used to automatically assign task owners and deadlines for specific client engagements. Users can specify task owners by using assignment logic such as specific user, role, queue, action plancreator, or account team1. Verified References: 1

The following steps are required to migrate customer records from the Individual Model to Person Accounts in Financial Services Cloud:

Ensure Person Accounts is enabled on the org. You need to have Person Accounts enabled before you can convert Individual Model records to Person Accounts. You can enable Person Accounts by contacting Salesforce Support or by using the Enable Person Accounts option in Setup > Account Settings.

Configure your Person Account record types in the Individual Record Type Mapper. You need to map your existing Individual Model record types to the corresponding Person Account record types. You can do this by using the Individual Record Type Mapper option in Setup > Financial Services Settings.

Use a CSV file to map PersonRecordTypeId to the Person Account RecordTypeId and use Data Loader to update Client Records. You need to update the Client records with the correct PersonRecordTypeId value that matches the Person Account RecordTypeId value. You can do this by using a CSV file andData Loader to perform a bulk update operation. Verified References: : Salesforce Help Article 1 : Salesforce Help Article 2 : Salesforce Help Article 3

The following considerations should be reviewed before implementing Flow for customer onboarding:

Use FieldLevel Security on Milestones, which is a setting that controls whether users can view and edit fields on records. The Admin should use Field Level Security to restrict access to the Milestones field on the Flow Template object, which is used to track the progress of customer onboarding flows2.

Flow for Financial Service Cloud is not available for the Individual Object Model, which is an alternative data model that uses the Individual object instead of Person Accounts to store information about people. Flow for Financial Service Cloud only supports Person Accounts as the primary object for customer onboarding flows2. Verified References: 2

The most suitable option for Cumulus Cloud Bank to provide its customer service staff with real-time access to customer accounts, including the ability to view current transactions and balances, is to embed custom Lightning web components on the Account and Financial Account pages, and use custom Apex to make callouts to the core system services. This option allows the bank to leveragethe Lightning Platform features and capabilities, such as Lightning web components, Apex, and callouts, to create a seamless and performant integration with their core systems. By using custom Lightning web components, the bank can create custom user interfaces that display the data from the core systems on the Account and Financial Account pages. By using custom Apex, the bank can write code that makes callouts to the core system services using HTTP requests and responses, and handle any authentication, error handling, or data transformation logic.

 The following considerations should be included when configuring the report with branch management reportable objects:

Bankers with Branches with Opportunities, Accounts, Leads, and Contacts report types are available for creating reports with Branch Unit Related Records. These are standard report types that allow users to create reports that show data from Banker,Branch Unit, Opportunity, Account, Lead, Contact, and Branch Unit Related Record objects.

The reportable objects include Banker, Branch Unit, Branch Unit Related Records, and Branch Unit Customer. These are custom objects that are part of the branch management feature in Financial Services Cloud. Banker is an object that represents a banker or an employee who works at a branch unit. Branch Unit is an object that represents a physical location where bankers provide services to customers. Branch Unit RelatedRecord is an object that represents a record that is related to a branch unit, such as an opportunity, an account, alead, or a contact. Branch Unit Customer is an object that represents a customer who has a relationship with a branch unit.

When Branch Unit is the primary object, the administrator can select Branch Unit Customers or Branch Unit Related Records as related objects. This means that the administrator can create reports that show data from Branch Unit and its related objects by using lookup fields or junction objects

The following objects dosupport Group-Level Rollups:

Financial Accounts: You can use Group-Level Rollups to display the total balance, total market value, and total cost basis of all the financial accounts that belong to a group.

Action Plans: You can use Group-Level Rollups to display the number of action plans, the number of completed action plans, and the completion percentage of all the action plans that are associated with a group.

Opportunities: You can use Group-Level Rollups to display the total amount, expected revenue, and weighted amount of all the opportunities that are related to a group. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 80. : Salesforce Financial Services Cloud Implementation Guide, page 81. : Salesforce Financial Services Cloud Implementation Guide, page 82.