Pass the Salesforce Accredited Professional Certification Financial-Services-Cloud Questions and answers with CertsForce

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.

The following statements are true for Rollup By Lookup (RBL) in Financial Services Cloud:

An RBL (Rollup By Lookup) rule displays summary calculations of financial account information, such as account balances. You can use RBL rules to aggregate financial account data across different levels of client relationships.

The Rollup By Lookup (RBL) configuration updates the corresponding RBL summaries at the diem and group levels. You can use RBL configuration to define which fields are rolled up and howthey are calculated for each diem and group type.

Salesforce does not recommend or provide support for creation or customization of Financial Services Cloud RBL rules. RBL rules are complex and require extensive testing and validation. If you need to create or customize RBL rules, you should contact a certified Salesforce partner or consultant. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 75. : Salesforce Financial Services Cloud Implementation Guide, page 76. : Salesforce Financial Services Cloud Implementation Guide, page 77.

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 withother 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.

QUESTIONNO: 114

Early in the discovery and solution meetings, it was determined that the client would primarily use out-of-the-box Financial Services Cloud (FSC) objects and components with minimal custom objects needed. In addition, it was decided that records should be private, but the managerial chain would require visibility into all their direct reports' records.

Which three security settings must be set up in Salesforce to meet these requirements?

A. Only Custom Profiles should be configured and assigned to all users to use FSC components and field-level security. The ^ administrator should configure custom profiles and assign them to all users

B. Organization-wide sharing defaults should be set to meet sharing requirements for all objects in use.

C. Each object sharing should be set up, explicitly sharing each user's record with the manager.

D. The Role Hierarchy in setup should be configured to allow for managers to automatically see records of those under them.

E. Custom permission sets and out-of-the-boxFSC permission sets should be configured or updated and assigned to all users for the use of FSC components and field-level security.

Answer: BDE

The following security settings must be set up in Salesforce to meet the requirements of using out-of-the-boxFinancial 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 toallow 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 RelationshipGroups. You can also create custom permission sets to meet your specific business needs. Verified References: : Salesforce Help Article 1 : Salesforce Help Article 2 : Salesforce Help Article 3

The following steps should be taken by the administrator to configure Financial Services Cloud correctly based on the scenario:

Assign the record typeto users. You need to assign the new record type to the user profiles or permission sets that need to create or access referrals of that type. You can assign record types by going to Setup > Profiles > Object Settings > Leads > Record Types or Setup > Permission Sets > Object Settings > Leads > Record Types.

Create a new record type Referral’ on the Lead object. You need to create a new record type on the Lead object and name it Referral. You can use this record type to distinguish referrals from other types of leads and apply different page layouts, business processes, or validation rules for referrals.

Update the lead page layout. You need to update the page layout for the Referral record type and add or remove fields according to the requirements. You canalso make some fields required or read-only on the page layout level. You can edit page layouts by going to Setup > Object Manager > Lead > Page Layouts. Verified References: : Salesforce Help Article 3 : Salesforce Help Article [4] : Salesforce Help Article [5]

 To model a requirement where more than one person can be joint owners on a Financial Account, the Admin can map additional owners using the Financial Account Role. The Financial Account Role is a junction object that links a contact or an individual to a financial account and defines their role or relationship with that account. By using Financial Account Role, the Admin can addmultiple owners to a Financial Account and specify their ownership percentage, primary status, and other details.

The following statements are correct about the Actionable Relationship Center Manager (ARC):

To enable users to see the ARC, you will need to add the component forARC to the page layout. The ARC is a Lightning component that can be added to any Lightning page that supports components, such as record pages, app pages, or Home pages. You can use the Lightning App Builder to drag and drop the ARC component to the desired location on the page layout.

ARC displays up to 5 related lists that have a configured compact layout. The ARC shows a graphical representation of the account-account relationships for a selected record, as well as related lists of other records that are associated with the account, such as contacts, financial accounts, or opportunities. The ARC can display up to 5 related lists at a time, and each related list must have a compact layout configured to show relevant fields.

The Association Type picklist controls the account-account relationship that display in the ARC. The Association Type picklist is a field on the Account Relationship object that defines the type of relationship between two accounts, such as Household Member, Business Owner, Trustee, orFriend. The ARC uses this field to filter and display the account-account relationships for a selected record. You can customize this picklist to add or remove values according to your business needs. Verified References: : Salesforce Help Article 3 : Salesforce Help Article 4 : Salesforce Help Article 5

The Financial Services Cloud featurethat is most suitable for tracking clients’ hobbies for marketing purposes is Interest Tags. Interest Tags are features that allow users to add tags to contacts or individuals based on their interests or preferences. Users can create custom interest tags or use predefined ones from FSC. By using Interest Tags, the wealth management firm can capture its clients’ hobbies and use them for marketing segmentation or personalization.

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 acustom 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 References: : Salesforce Help Article [4] : Salesforce Help Article [5]

Tohelp 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, suchas 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 References: : Salesforce Help Article 1 : Salesforce Help Article 2