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

Action Plans are a feature of Financial Services Cloud that allow users to create and execute repeatable tasks based on predefined templates. Action Plans can help streamline and standardize business processes, such as onboarding new clients, conducting annual reviews, or resolving service requests. Action Plans can also assign tasks to different users or teams, set deadlines and priorities, and track progress and status.

Omni Scripts are a feature of Vlocity that allow users to create and run guided interactions based on predefined scripts. Omni Scripts can help automate and simplify complex workflows, such as opening new accounts, applying for loans, or updating personal information. Omni Scripts can also integrate with other systems, capture user inputs, perform calculations, and display dynamic content.

Action Plans are a feature of Financial Services Cloud that allow users to create and execute repeatable tasks based on predefined templates. Action Plans can help streamline and standardize business processes, such as onboarding new clients, conducting annual reviews, or resolving service requests. Action Plans can also capture detailed notes for client meetings and add action items to follow up.

Unify and improve team collaboration by sharing and managing customer leads and referrals across multiple lines of business at the bank to drive customers' financial needs and deepen client relationships; Deliver connected and personalized digital experiences to the bank's customers thanks to a 360-degree view of its customer data consolidating multiple customer databases and sources from diverse channels at the bank; Modernize client-advisor experiences from engagement to relationship management to effectively drive long-term, trusted relationships.

Financial Services Cloud is a platform that enables banks to deliver seamless and personalized customer experiences across multiple channels and devices. Financial Services Cloud can help banks achieve the following outcomes:

Unify and improve team collaboration by sharing and managing customer leads and referrals across multiple lines of business at the bank to drive customers' financial needs and deepen client relationships. Financial Services Cloud provides tools such as Lead Conversion, Referral Management, Relationship Groups, and Compliant Data Sharing to facilitate cross-team collaboration and coordination.

Deliver connected and personalized digital experiences to the bank's customers thanks to a 360-degree view of its customer data consolidating multiple customer databases and sources from diverse channels at the bank. Financial Services Cloud provides a unified data model that integrates customer data from various sources, such as core banking systems, online banking portals, mobile apps, social media, and third-party providers. Financial Services Cloud also provides features such as Customer Profile, Actionable Relationship Center, Interaction Summaries, and Einstein Analytics to provide a comprehensive and holistic view of the customer's financial situation, needs, preferences, and interactions.

Modernize client-advisor experiences from engagement to relationship management to effectively drive long-term, trusted relationships. Financial Services Cloud provides features such as Client Onboarding, Action Plans, Goals-Based Planning, Financial Accounts, Financial Deals, Next Best Action, and Einstein Bots to enable advisors to deliver proactive and personalized advice, recommendations, and solutions to their clients.

Permission set licenses are a way to grant additional permissions and access settings to users based on their job function or role. Permission set licenses can extend the functionality of the user's existing license type without changing it. Financial Services Cloud provides four permission set licenses that correspond to different user personas and use cases:

FSC Foundations: This permission set license grants access to basic Financial Services Cloud features, such as Client Segmentation, Relationship Groups, Relationship Map, Financial Accounts, Financial Goals, and Financial Summary. This permission set license is suitable for users who need to view and manage client data and relationships, such as personal bankers or service representatives.

FSC Basic: This permission set license grants access to advanced Financial Services Cloud features, such as Action Plans, Interaction Summaries, Interaction Participants, Financial Deals, Financial Deal Participants, and Record Alerts. This permission set license is suitable for users who need to track and execute client interactions and transactions, such as advisors or specialists.

FSC Extension: This permission set license grants access to additional Financial Services Cloud features that are not included in the other permission set licenses, such as Household Rollups and Compliant Data Sharing. This permission set license is suitable for users who need to perform complex calculations or comply with data regulations, such as analysts or compliance managers.

FSC Standard: This permission set license grants access to all Financial Services Cloud features that are included in the other permission set licenses. This permission set license is suitable for users who need full access and functionality of Financial Services Cloud, such as super users or administrators.

To ensure the correct profiles and permissions for an API integration between Salesforce and a risk control system, the consultant should do the following steps:

Create a dedicated Integration User that will be used to authenticate and authorize the API calls between Salesforce and the risk control system. The Integration User should have a unique username, password, and security token that are not shared with other users or systems. The Integration User should also have the minimum permissions and access settings required to perform the integration tasks.

Create a new custom profile and ensure API Only is selected. The API Only option restricts the user from logging in to the Salesforce user interface, but allows the user to access the Salesforce API. The custom profile should also have the appropriate object permissions, field-level security, record types, page layouts, and other settings that are relevant for the integration. The custom profile should be assigned to the Integration User.

Some considerations when adopting FSC-related objects are:

In a household, each household member is modeled as a Contact, and the household is modeled as an Account. A household is a type of relationship group that represents a group of clients who have a direct relationship with one another and shared financials, such as spouses and their dependent children. A household is modeled as an Account record with a custom record type of Household. Each household member is modeled as a Contact record that is related to the household Account. A household can also have related accounts and contacts that are not part of the household, but are associated with it for some reason.

Both the Financial Deal object and the Opportunity object support Compliant Data Sharing. Compliant Data Sharing (CDS) is a feature of FSC 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. CDS can also be enabled for the Financial Deal object, which is a custom object that represents a business opportunity or transaction with a client. The Financial Deal object can be used instead of or in addition to the Opportunity object, depending on the business needs.

Interaction Summary is an enhancement of the standard Activity object. FSC implementations should use Interaction Summary as a replacement for the Activity object. Interaction Summary is a custom object that captures the details of a client interaction, such as a meeting, a call, or an email. Interaction Summary can be linked to other FSC objects, such as Financial Accounts, Financial Goals, Financial Deals, or Relationship Groups. Interaction Summary can also have participants, which are records that represent the people or groups involved in the interaction.

The Actionable Relationship Center (ARC) is a feature of FSC that allows users to view their customers' relationships in an easy-to-navigate graph. ARC helps users understand relationships between people, groups, accounts, contacts, opportunities, deals, and other records. ARC also allows users to view and manage related lists for each node in the graph. Related lists are collections of records that are related to another record by a lookup or master-detail relationship.

The related lists that are visible within ARC depend on the node type and configuration. For example, for an Account node with Household record type, some of the related lists that are visible are:

Household Financial Accounts: This related list shows all the financial accounts that are related to the household members by either ownership or beneficiary relationships.

Cases: This related list shows all the cases that are related to the household account or its members.

Client Financial Goals: This related list shows all the financial goals that are related to the household account or its members.

Other related lists that can be visible for different node types include:

Contacts

Opportunities

Financial Deals

Interaction Summaries

Action Plans

Notes

Attachments

To use the OmniScript metadata type, the administrator should enable a custom domain in the Salesforce org. A custom domain is a unique URL that replaces the standard Salesforce domain (such as https://yourcompany.my.salesforce.com) with a branded domain (such as https://yourcompany.force.com). A custom domain allows users to access OmniScripts and other Vlocity features from a web browser or a mobile app. A custom domain also provides enhanced security and performance for the org.

To enable a custom domain, the administrator needs to do the following steps:

From Setup, in the Quick Find box, enter My Domain, then select My Domain.

Enter a subdomain name and check its availability.

Click Register Domain.

After receiving an email confirmation that the domain is ready, click Deploy to Users.

An Integration Procedure is a feature of Vlocity that allows users to create and execute data integration tasks between Salesforce and external systems. An Integration Procedure can perform various operations, such as extract, transform, load, query, or update data from different sources and targets. An Integration Procedure can also invoke other Vlocity features, such as DataRaptors, OmniScripts, or Calculations.

To implement a Flex Card for weather conditions in the console, the consultant should use an Integration Procedure that can do the following steps:

Query the weather API using an HTTP action and pass the account address as a parameter.

Extract the relevant fields from the weather API response, such as temperature, humidity, precipitation, etc.

Query the account field from Salesforce using a DataRaptor Extract action and pass the account ID as a parameter.

Merge the weather API fields and the account field into a single data set using a List Merge action.

Return the data set to the Flex Card using a Return action.