Financial-Services-Cloud Salesforce Financial Services Cloud (FSC) Accredited Professional (AP) Exam (SU24) Questions and Answers

To configure Financial Services Cloud to allow users to relate two business accounts, the administrator should update the Role picklist on the Account-Account Relationship object with new value. The Role picklist is a field on the Account-Account Relationship object that defines the type of relationship between two accounts, such as Household Member, Business Owner, Trustee, or Friend. The Role picklist is used to filter and display the account-account relationships in the Actionable Relationship Center (ARC). To update the Role picklist, you need to go to Setup > Object Manager > Account-Account Relationship > Fields & Relationships > Role and add or remove values according to your business needs. Verified References: : Salesforce Help Article [10] : Salesforce Help Article [11]

The following things happen when an opportunity record that has opportunity participants with associated share table entries is set to Private:

• The share table records are deleted, which means that any sharing access granted by the opportunity participants is revoked.
• The opportunity participant records are not deleted, which means that they still exist on the opportunity record and can be viewed by users who have access to the opportunity. 

To modify a published Action Plan to support an additional task, Jen should use the Action Plan item feature to add an additional task to the published Action Plan. An Action Plan item is a construct in Financial Services Cloud that allows you to add, edit, or delete tasks in an existing Action Plan. You can use Action Plan items to customize your Action Plans according to your specific needs and preferences. Verified References: : Salesforce Help Article 1

The Admin can change the color of important life events to red by using custom CSS in a Lightning App Builder theme layout component. This way, the agents can quickly scan the Life Events component and find the information they need without much effort. The color red can draw attention and indicate urgency or importance for certain life events.

The following activities should be prioritized by the implementation team during planning for designing the Financial Services Cloud implementation:

• Prepare for integrations with transactional systems, external data sources, custodians, and any other platforms that the company’s business relies on. Integrations are the connections or interactions that allow data or functionality to flow between different systems or platforms. You should prepare for integrations with your existing or new systems or platforms that support your business processes, such as transactional systems, external data sources, custodians, or other platforms. You should also consider the integration methods, tools, requirements, and challenges that you will need to address during the implementation.
• Beyond the preconfigured settings, evaluate whether they need advanced customizations. Customizations are the changes or modifications that you make to Salesforce to meet your specific business needs or preferences. You should evaluate whether you need advanced customizations beyond the preconfigured settings that Financial Services Cloud provides out of the box, such as custom objects, fields, formulas, validation rules, workflows, triggers, or components. You should also consider the impact, benefits, and risks of your customizations on your data model, user interface, performance, security, or maintenance.
• Review the out-of-the-box capabilities and compare them to the company’s current needs. Out-of-the-box capabilities are the features or functions that Financial Services Cloud offers without any customizations or configurations. You should review the out-of-the-box capabilities and compare them to your company’s current needs and expectations. You should also identify any gaps or opportunities for improvement that you can address with configurations or customizations during the implementation. Verified References: : Salesforce Help Article [12] : Salesforce Help Article [13] : Salesforce Help Article [14]

To make sure that Scott’s data is rolling up to the Adams Household, the Banker should make the Adams Household Scott’s primary Group and edit the Activities & Objects to Roll Up. A primary Group is a construct in Financial Services Cloud that allows you to define the main group for a client. You can use primary Group to roll up financial data from all the financial accounts that are related to the client or the group. By making the Adams Household Scott’s primary Group, the Banker can ensure that Scott’s financial data is included in the household summary. The Banker can also edit the Activities & Objects to Roll Up to specify which items, such as financial accounts, goals, or referrals, should be rolled up for Scott. Verified References: : Salesforce Help Article 4

The consultant should design the FlexCards as follows to meet the requirements:

• Parent FlexCard with multiple Child Flex Cards and Card Actions. A Parent FlexCard is a construct in Financial Services Cloud that allows you to display information from one record in a card-like format on a Lightning page. A Child FlexCard is a construct in Financial Services Cloud that allows you to display information from related records in a card-like format within a Parent FlexCard. A Card Action is a construct in Financial Services Cloud that allows you to perform actions on a record from within a FlexCard, such as edit, delete, renew, or view details. You can use Parent FlexCards, Child FlexCards, and Card Actions to create an agent console that provides a 360-degree view of your customers and enables quick actions on their records. Verified References: : Salesforce Help Article [6] : Salesforce Help Article [7] : Salesforce Help Article [8]

 In an existing Financial Services Cloud org using the individual account model, custom objects are used to represent other assets, liabilities, and goals. These objects are related to the Account object via lookup relationships. For example:

• The Other Asset object is used to represent non-financial assets owned by an account holder, such as real estate properties, vehicles, or jewelry.
• The Other Liability object is used to represent non-financial liabilities owed by an account holder, such as mortgages, loans, or taxes.
• The Financial Goal object is used to represent financial objectives pursued by an account holder, such as retirement planning, education funding, or debt reduction. Verified References: : Salesforce Help Article [10] : Salesforce Help Article [11] : Salesforce Help Article [12]

Identification Document is the Financial Services Cloud object that should be recommended for storing client data on drivers’ licenses and passports. Identification Document is a standard object that represents a document that verifies a person’s identity, such as a driver’s license, passport, or national ID card. You can create identification document records for individual clients and link them to their person accounts. You can also store information such as document type, number, issue date, expiration date, and country of issuance. References: [Identification Document Object], [Manage Identification Documents]

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 how they 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 best way for the Admin to access a Financial Services Cloud pre-configured org, including data and the right licenses, to learn about the product is to request a 30-day Financial Services Cloud trial org. You can sign up for the 30-day trial using this form 4. You get preconfigured and preloaded sample data so you can start playing around in your new org right away. Once you’re done testing it out, you can transition your trial org to a production org with the help of your account executive or solution engineer. Verified References: : Trailhead Module 5

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

Process Builder and Screen Flows are two features that can be used to design a business process for identity verification. Process Builder is a tool that allows you to automate business processes by creating workflows that trigger actions based on certain criteria. Screen Flows are a type of flow that guide users through a series of screens to collect and update data. You can use Process Builder to launch a Screen Flow when a customer contacts the bank, and use the Screen Flow to capture and verify the customer’s identity information. References: [Process Automation], [Screen Flows]

A Relationship Group is a construct in Financial Services Cloud that allows you to model complex and dynamic relationships between clients and accounts. You can use Relationship Groups to link duplicate client records and create a consolidated view of their financial data, activities, and interactions. You can also use Relationship Groups to sync data between Salesforce and the source system using external IDs and integration tools. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 67.

To meet the requirements of sharing special deposit products for employees, the administrator should create a Financial Account sharing rule based on criteria. A Financial Account sharing rule is a sharing rule that grants access to financial account records based on record owner or field values. A sharing rule based on criteria is a type of sharing rule that grants access to records that meet certain criteria. By creating a Financial Account sharing rule based on criteria, the administrator can share the special deposit products with the customer service employees within a specific group based on a field value that indicates the product type.

To design the future state business process using FSC features, the administrator should create an action plan with tasks to follow up in 2 days, 2 weeks, and 2 months when an account status is changed to “Customer”. An action plan is a feature that allows users to create templates for common client processes, such as account opening, loan application, or financial review. An action plan template consists of action plan items that define the tasks, subtasks, and deadlines for each step of the process. By creating an action plan with tasks to follow up in 2 days, 2 weeks, and 2 months when an account status is changed to “Customer”, the administrator can automate the email reminder process and track and report on the progress in FSC

To skip non-work days in Action Plan when setting task completion dates, the administrator should configure the day without business hours, as it is considered a non-work day, even if the day is a recurring holiday. This means that the administrator should leave the start and end time fields blank for any day that is not a working day, such as Saturday or Sunday. Action Plans will then automatically omit those days when calculating the task completion dates based on the business hours1. Recurring holidays are not considered by Action Plans when determining the non-work days to skip2.

References:

• Set Business Hours
• Set Up Company-wide Holidays

The following are the building blocks of Flow Orchestration:

• Steps: Steps are discrete units of work that can be performed by a user or a system within a flow orchestration. Steps can have different types, such as user input steps, system action steps, decision steps, or subflow steps. Steps can also have different attributes, such as name, description, icon, input variables, output variables, or preconditions.
• Stages: Stages are logical groupings of steps that represent phases or milestones within a flow orchestration. Stages can have different attributes, such as name, description, icon, entry criteria, exit criteria, or completion actions.
• Work Items: Work Items are instances of flow orchestrations that track the progress and status of each execution. Work Items can have different attributes, such as name, description, owner, assignee, due date, priority, status, stage history, or step history. Verified References: : Salesforce Help Article [7] : Salesforce Help Article [8] : Salesforce Help Article [9]

The following considerations indicate that a new Salesforce org is the better choice for implementing Financial Services Cloud:

• The bank wants to use this project as an opportunity to retire customization. A new org will allow the bank to start fresh and avoid carrying over unnecessary or outdated customization that may conflict with Financial Services Cloud features or best practices.
• The current implementation is using a product-centric view and the bank wants to move to a customer-centric view. A new org will allow the bank to adopt the Financial Services Cloud data model, which is designed to provide a holistic view of the customer and their relationships, goals, financial accounts, activities, and interactions.
• Existing business capabilities and processes can be redesigned to deliver a higher business impact. A new org will allow the bank to leverage the Financial Services Cloud capabilities, such as Action Plans, Relationship Groups, Rollup By Lookup, Service Processes, etc., to optimize their business processes and enhance their customer experience. Verified References: : Salesforce Help Article 6

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.

Rollup By Lookup (RBL) summaries are available for the following objects:

• Financial Accounts, which are records that represent financial products or services that a client owns or uses1.
• Assets and Liabilities, which are records that represent the value of what a client owns or owes1.
• Contacts, which are records that represent individuals who are associated with an account3.

The Referral Score is updated when an opportunity associated with the Referral is Closed Won. The Referral Score is a metric that measures the quality and quantity of referrals that a user creates or receives. The Referral Score is calculated as the number of referrals converted to opportunities divided by the total number of referrals. The Referral Score is displayed in the Referral Summary component on the user’s Home page or record page. The Referral Score is updated whenever a referral is converted to an opportunity or an opportunity is closed as won or lost. Verified References: : Salesforce Help Article 2 : Salesforce Help Article 4

 The following actions regarding functionality and features should be suggested to help guide Cumulus Insurance users through their complex business processes:

• Configure Dynamic Actions for Lightning pages. Dynamic Actions are a feature that allows you to customize the actions that appear on a Lightning page based on criteria such as record type, field value, device type, or user profile. You can use Dynamic Actions to show or hide actions that are relevant or irrelevant for each stage of the business process, such as creating a case, sending an email, or generating a quote.
• Enable In-App Guidance to provide walk-throughs. In-App Guidance is a feature that allows you to create prompts and guided tours that appear within the Salesforce app to help users learn new features, complete tasks, or adopt best practices. You can use In-App Guidance to provide step-by-step guidance for complex business processes, such as onboarding a customer, submitting a claim, or renewing a policy.
• Use flows to remove the need for complex Lightning pages. Flows are a tool that allows you to automate business processes and guide users or customers through screens that collect and display information. Flows can have multiple steps and branching logic that ask for different information depending on the responses. You can use flows to simplify and streamline complex business processes, such as applying for a loan, enrolling in a plan, or changing a beneficiary. Verified References: : Salesforce Help Article [12] : Salesforce Help Article [13] : Salesforce Help Article [14]

Record alerts are a feature of Financial Services Cloud that let users create and display alerts on record pages to highlight important information or actions. Record alerts are based on OmniStudio, a low-code platform for building digital experiences in Salesforce. To access or extend permissions for record alerts in Financial Services Cloud, users need to have one of the following permission sets:

• FSC Standard permission set: This permission set grants access to the core features of Financial Services Cloud, including record alerts. Users with this permission set can view and create record alerts on supported objects, such as accounts, contacts, financial accounts, and opportunities1.
• FSC Foundations permission set: This permission set grants access to the common features of Financial Services Cloud that are shared across subverticals, such as retail banking, wealth management, and insurance. Users with this permission set can view and create record alerts on supported objects2.
• OmniStudio User permission set: This permission set grants access to the OmniStudio features, such as OmniScripts, DataRaptors, Integration Procedures, and Record Alerts. Users with this permission set can view and create record alerts on any object that has the Record Alert component enabled3.

References:

• FSC Standard Permission Set
• FSC Foundations Permission Set
• OmniStudio User Permission Set

The order that the consultant should follow when performing the data migrations is Individuals, then Financial Accounts, then Financial Account Roles, then Financial Account Transactions. This order ensures that the data dependencies and relationships are maintained and that the data integrity and quality are preserved. By migrating Individuals first, the consultant can create the records that represent the customers of the bank. By migrating Financial Accounts next, the consultant can create the records that represent the financial products or services that the customers own or use. By migrating Financial Account Roles next, the consultant can create the records that link the individuals to the financial accounts and define their roles or relationships with those accounts. By migrating Financial Account Transactions last, the consultant can create the records that represent the transactions or activities that occur on the financial accounts. 

To configure customized nodes for display in Actionable Relationship Center (ARC), developers should reference the FlexCard in the Display properties of the custom ARC relationship graph. A FlexCard is a tool that allows users to create custom user interfaces for displaying data from Salesforce or external systems using OmniScripts and Integration Procedures. A custom ARC relationship graph is a metadata type that defines the nodes and edges of a custom relationship graph for ARC. By referencing the FlexCard in the Display properties of the custom ARC relationship graph, developers can customize the look and feel of the nodes and display data from various sources on them. 

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. 

 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 add multiple owners to a Financial Account and specify their ownership percentage, primary status, and other details.

Group Membership is a construct in Financial Services Cloud that allows you to define the relationship between a group and its members. You can use Group Membership to specify the following information:

• The role of the member within the group, such as Owner, Beneficiary, Trustee, etc.
• Whether the group is the primary group for the member, which affects how financial data is rolled up and displayed. Verified References: : Salesforce Financial Services Cloud User Guide, page 38.

The following standard fields are available to track a customer’s retirement goal progress:

• Actual value, which is a currency field that represents the current value of the goal.
• Target value, which is a currency field that represents the desired value of the goal.
• Target Date, which is a date field that represents the expected date of achieving the goal.

The functionality that Rollup By Lookup (RBL) can provide for rolling up customer data at the client and group levels are as follows:

• An RBL rule displays summary calculations of financial account information, such as account balances, net worth, total assets, total liabilities, and so on1.
• When you edit a financial account record or primary group membership, the Rollup By Lookup (RBL) configuration updates the corresponding RBL summaries at the client and group levels1.
• Rollup By Lookup (RBL) displays associated records for Financial Accounts, Financial Goals, and Opportunities on the client and group pages1. Verified References: 1

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.

Salesforce provides features and tools to help financial institutions improve the efficiency of their mortgage processes and provide better experiences for their customers. Some of the features and tools that a consultant can suggest to Cumulus Bank to implement are:

• The standard mortgage flow templates to build a mortgage flow in Financial Services Cloud: These are prebuilt flow templates that guide users through the steps of creating a mortgage application, capturing borrower information, and submitting the application for approval7. The templates can be customized to suit the bank’s specific needs and requirements8.
• Flow Builder to automate these business processes: Flow Builder is a point-and-click tool that lets users create flows to automate business processes in Salesforce9. Flow Builder can be used to create custom mortgage flows that integrate with other Salesforce features, such as data models, objects, fields, validation rules, and actions10.

References:

• Flow Builder for Mortgage
• Customize Mortgage Flows
• Flow Builder
• Create a Mortgage Flow

To configure customized nodes for display in ARC, developers should reference the Lightning Web Component in the Display properties of the custom ARC relationship graph. A Lightning Web Component is a custom framework for creating reusable web components that run natively in browsers and leverage modern web standards. A custom ARC relationship graph is a metadata type in Financial Services Cloud that defines how account-account relationships are displayed in ARC, such as node shape, color, size, label, or icon. You can use Lightning Web Components and custom ARC relationship graphs to create customized nodes for ARC that show additional information or functionality for each account. Verified References: : Salesforce Help Article [9] : Salesforce Help Article [10]

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

Enable Compliant Data Sharing for Interaction Summaries, Use Interaction Summary Participants to provide the right access to individuals or groups, and Disable Role-Hierarchy-Based Sharing for Interaction Summaries.

To enable advisors to capture Once-in-a-Lifetime events and prevent users from accidentally creating more than one event of such an event type, the consultant should configure Unique event types. Unique event types are event types that can only be created once for each contact or individual, such as birth, death, or marriage. By using Unique event types, the consultant can ensure that advisors can capture important life events for their customers and avoid duplication or inconsistency. 

Discovery Framework is a scalable assessment framework that financial institutions use to gather and evaluate customer information through digital and human channels. Some of the things to consider regarding Discovery Framework are:

• Discovery Framework creates highly capable forms with integrations and advanced logic. The forms can be customized with various types of questions, validations, calculations, branching, and integrations with external systems1.
• Discovery Framework can create both standard and hierarchical questions. Standard questions are single-level questions that can be grouped into sections. Hierarchical questions are multi-level questions that can have subquestions based on the answer to the parent question2.
• FSC Discovery Framework allows archiving questions. Archiving a question removes it from the active question pool and prevents it from being added to new forms. Archived questions can be restored if needed3.

References:

• Discovery Framework
• Create Questions for Discovery Framework
• Archive Questions for Discovery Framework

The following things must be kept in mind when creating Action Plan Templates:

• When creating Action Plan Templates with the UI, you can designate a plan owner different from the plan creator. The plan owner is the user who is responsible for executing the tasks in the Action Plan. The plan creator is the user who creates the Action Plan Template or the Action Plan from the template. You can assign a different plan owner for each Action Plan Template or Action Plan.
• An Action Plan is a run-time instance of the template that allows you to automate the sequence of the tasks you defined in the template. An Action Plan Template is a reusable blueprint that defines the tasks, owners, and deadlines for a common business process or service request. An Action Plan is a specific implementation of the template that applies to a particular target record, such as an account, contact, or opportunity.
• When you create an Action Plan from a template for a specific target record, item deadlines are calculated using the start date and date offset defined in the Action Plan Template. The start date is the date when you create the Action Plan from the template. The date offset is the number of days before or after the start date when each task is due. You can specify different date offsets for each task in the template. Verified References: : Salesforce Help Article 2 : Salesforce Help Article 3 : Salesforce Help Article 4

The solution that the consultant should suggest the client explore to improve its clients’ documentation submission and tracking is the Send Documents flow for Retail Banking. The Send Documents flow for Retail Banking is a prebuilt flow that allows users to send documents requests to clients via email and track the status of the requests in FSC. The flow uses DocuSign eSignature integration to enable clients to sign and return documents electronically. By using the Send Documents flow for Retail Banking, the consultant can help the client streamline and simplify its document management process and improve its customer service agents’ efficiency