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.