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

To help onboarding new customers, the consultant should recommend using Action Plan and Action Plan Template. Action Plan is a feature in Financial Services Cloud that allows you to automate and standardize common business processes or service requests, such as customer onboarding, account opening, or loan origination. You can use Action Plan to create templates that define the tasks, owners, and deadlines for each process or request. You can also use Action Plan to enforce task dependencies and completion criteria, so that bankers cannot skip or miss any tasks or move to the next stage of the onboarding process without meeting the requirements. Verified

Reference: : Salesforce Help Article1: Salesforce Help Article2

To document the current state business process for implementing Salesforce Financial Services Cloud, the consultant should create an end-to-end visual map of the process using personas, systems, inputs, and outcomes. A visual map is a tool that can help illustrate the flow of a business process from start to finish, showing the steps, decisions, and dependencies involved in each stage. A visual map can also include personas, systems, inputs, and outcomes to provide more context and detail for each step of the process. Personas are fictional characters that represent the different roles or users that participate in or interact with the process. Systems are the tools or applications that are used to perform or support the process. Inputs are the data or information that are required or provided for each step of the process. Outcomes are the results or outputs that are achieved or delivered by each step of the process. Verified

Reference: : Salesforce Help Article3: Salesforce Help Article [4]

To prevent the data import from creating duplicates when importing records from a system outside of Salesforce, you should use External ID. External ID is a custom field type that can be used to store unique identifiers from other systems. You can use External ID to match records during data import and avoid creating duplicate records in Salesforce. You can also use External ID to enable upsert operations, which can insert new records or update existing records based on the External ID value. Verified

Reference: : Salesforce Help Article [5] : Salesforce Help Article [6]

To configure a custom field for reporting when relating two-person accounts to each other, the Financial Services Cloud consultant should configure the custom field on the Account Account Relationship object. The Account Account Relationship object is a junction object that links two accounts together and defines their relationship type and role. By configuring a custom field on the Account Account Relationship object, the consultant can capture additional information about how two-person accounts are related to each other and use it for reporting purposes.

The Financial Services Cloud capability that provides the ability to accommodate the request of sharing specific records with certain users who are not typically engaged in that account is Compliant Data Sharing. Compliant Data Sharing is a feature that allows users to share records with other users based on criteria such as record type or field value. Users can create sharing rules for objects such as account, contact, individual, financial account role, opportunity participant role, or case team role. By using Compliant Data Sharing, the financial institution can share records with legal and compliance members who must be engaged for particular deals based on a field value that indicates the deal type.

The following security settings must be set up in Salesforce to meet the requirements of using out-of-the-box Financial Services Cloud objects and components with minimal custom objects and private record sharing with managerial visibility:

Organization-wide sharing defaults should be set to meet sharing requirements for all objects in use. Organization-wide sharing defaults are the baseline level of access that users have to records that they do not own or are not explicitly shared with them. You can use organization-wide sharing defaults to specify the default access level for each object, such as Public Read/Write, Public Read Only, or Private. You can also use organization-wide sharing defaults to enable or disable features such as grant access using hierarchies, external access, or external org-wide defaults.

The Role Hierarchy in setup should be configured to allow for managers to automatically see records of those under them. The Role Hierarchy is a structure that represents the levels of data visibility and access that users have in an organization based on their role or position. You can use the Role Hierarchy to define the roles and subordinates for each user and grant access to records owned by or shared with users below them in the hierarchy. You can also use the Role Hierarchy to control the visibility of dashboards, reports, and territories.

Custom permission sets and out-of-the-box FSC permission sets should be configured or updated and assigned to all users for the use of FSC components and field-level security. Permission sets are a collection of settings and permissions that give users access to various tools and functions in Salesforce. You can use permission sets to grant additional permissions or access levels to users without changing their profile. You can also use permission sets to control the field-level security for each object and field, which determines whether users can view, edit, or delete data in those fields. Financial Services Cloud provides several out-of-the-box permission sets that grant access to FSC components and features, such as Action Plans, Financial Accounts, or Relationship Groups. You can also create custom permission sets to meet your specific business needs. Verified

Reference: : Salesforce Help Article1: Salesforce Help Article2: Salesforce Help Article3

To configure a custom field for reporting when relating two business accounts to each other, the administrator should configure the custom field on the Account-Account Relationship object. The Account-Account Relationship object is a custom object in Financial Services Cloud that allows you to create and manage relationships between two accounts, such as Household Member, Business Owner, Trustee, or Friend. You can use the Account-Account Relationship object to store additional information about the relationship between two accounts, such as role, start date, end date, or status. You can also use the Account-Account Relationship object to report on the account-account relationships and analyze their impact on your business. Verified

Reference: : Salesforce Help Article [4] : Salesforce Help Article [5]

The following objects should be used when planning to use the Mortgage Data Model to integrate with external Loan Origination and Customer Onboarding applications to accurately track the pipeline:

Opportunity: An Opportunity is a standard object that represents a potential sale or deal for your products or services. You can use the Opportunity object to track and manage the stages, amounts, probabilities, and expected revenue of your deals. You can also use the Opportunity object to associate products, price books, quotes, contracts, orders, or assets with your deals.

Account: An Account is a standard object that represents a person or an organization that has a business relationship with your company. You can use the Account object to store information about your customers, such as name, address, phone number, website, industry, or rating. You can also use the Account object to associate contacts, opportunities, activities, cases, or notes with your customers.

Financial Account: A Financial Account is a custom object in Financial Services Cloud that represents a financial product or service that is owned by an account holder or related to an account holder's financial goal. You can use the Financial Account object to store information about your customers' financial accounts, such as type, balance, status, or interest rate. You can also use the Financial Account object to associate financial transactions, financial account roles, or financial goals with your customers' financial accounts. Verified

Reference: : Salesforce Help Article [6] : Salesforce Help Article [7] : Salesforce Help Article [8]

The following insurance processes are managed by the Policy Administration component:

Payments: Payments are the amounts that a policyholder pays to an insurance company for a policy or a claim. You can use the Policy Administration component to manage the payment schedules, methods, and statuses for your policies and claims. You can also use the Policy Administration component to integrate with external payment systems and track the payment transactions and balances for your policies and claims.

Approvals: Approvals are the processes that an insurance company follows to review and authorize a policy or a claim. You can use the Policy Administration component to configure and automate the approval workflows, rules, and criteria for your policies and claims. You can also use the Policy Administration component to assign approvers, send notifications, and monitor the approval statuses and histories for your policies and claims.

Endorsements: Endorsements are the changes or modifications that a policyholder requests or an insurance company makes to a policy. You can use the Policy Administration component to manage the endorsement requests, types, and statuses for your policies. You can also use the Policy Administration component to update the policy details, coverages, premiums, or terms based on the endorsements for your policies. Verified

Reference: : Salesforce Help Article [9] : Salesforce Help Article [10] : Salesforce Help Article [11]