Financial-Services-Cloud Practice Test

C.   Collect input from internal users with a form placed on a Lightning page cKlaunched by a button.

Explanation:

A suitable use case for Flow Builder is to collect input from internal users with a form placed on a Lightning page or launched by a button. Flow Builder is a tool that allows users to automate business processes by building flows that guide users through screens, execute logic, manipulate data, and interact with Salesforce and external systems. By using Flow Builder, the system administrator can create a flow that collects input from internal users with a form and performs actions based on the input.

A.   Action Plans create repeatable tasks and automate the task sequences when executed

B.   When you create an action plan from a template for a specific target record, items that have no assigned user are assigned to the owner of that " target record.

D.   Action Plans enhance collaboration and productivity by automatically assigning task owners and deadlines for specific client processes.

Explanation:

Action Plans are a feature that allows users to create templates for common client processes, such as loan approval, account opening, or financial review. Action Plans can create repeatable tasks and automate the task sequences when executed. When an action plan is created from a template for a specific target record, such as an account or an opportunity, items that have no assigned user are assigned to the owner of that target record. Action Plans can also enhance collaboration and productivity by automatically assigning task owners and deadlines for specific client processes.

A.   FSC Foundations permission set

B.   FSC Extension permission set

Explanation:

The Access Interest Tags for Financial Services Cloud permission is included in two permission sets that are provided by FSC:

FSC Foundations permission set: This permission set grants access to the core features of FSC, such as financial accounts, account groups, households, goals, referrals, and interest tags7.

FSC Extension permission set: This permission set grants access to additional features of FSC that extend beyond the core functionality, such as action plans, relationship groups, relationship maps, client tasks, client notes, and interest tags8.

To create a new FSC permission set that includes the Access Interest Tags for Financial Services Cloud permission, either of these permission sets can be cloned and modified as needed.

References:

FSC Foundations Permission Set
FSC Extension Permission Set

D.   The Person Account is a virtual object displaying data from Accounts and Contacts objects. It represents all aspects of the person and includes D data such date of birth or tax ID number.

E.   The Person Account model uses the standard Account object to hold all of the details about a person The Account object has been extended " with custom fields and a Person Account Record Type

Explanation:

The following statements are true for the Financial Services Cloud Person Account Data Model:

The Person Account is a virtual object displaying data from Accounts and Contacts objects. It represents all aspects of the person and includes data such as date of birth or tax ID number. You can use Person Accounts to store information about individual people by combining certain Account and Contact fields into a single record.

The Person Account model uses the standard Account object to hold all of the details about a person. The Account object has been extended with custom fields and a Person Account Record Type. You can use Person Accounts to simplify your data model and reduce the number of records you need to manage.

C.   The administrator can define up to 300 total sharing rules for each object.

Explanation:

The architect at Cumulus Insurance should be aware of the limitation that the administrator can define up to 300 total sharing rules for each object when using the Role Hierarchy and sharing rules to implement the franchise business model. Sharing rules are a way of granting additional access to records based on criteria, such as record owner, role, or field values. The Role Hierarchy is a way of organizing users into a hierarchy that reflects the reporting structure of the company. The Role Hierarchy and sharing rules can be used together to control the access and visibility of records for different users in Financial Services Cloud. However, there is a limit of 300 sharing rules per object, which means that the administrator may need to use other methods, such as public groups or manual sharing, to grant access to records beyond this limit.

References:

[Sharing Rules]
[Role Hierarchy]
[Sharing Rule Limits]