Financial-Services-Cloud Practice Test Questions

C.   Financial Service Cloud Basic

Explanation:

Financial Services Cloud offers tiered licensing to control costs. The Financial Service Cloud Basic license is the restricted, lower-cost license designed for users who need limited FSC access, such as bank tellers or customer service agents.

A. Financial Services Cloud Standard: This is not a standard FSC license name. The primary FSC license types are FSC (full) and FSC Basic (restricted).

B. Client Segmentation: This is an FSC feature or capability, not a license type.

C. Financial Service Cloud Basic: Correct. FSC Basic is the restricted license that provides access to core FSC objects (Household, Financial Account, etc.) but excludes advanced features like Action Plans, Goals, or certain advisor tools. It is cost-effective for frontline staff who need limited access.

D. Financial Service Cloud Extension: This is a permission set that grants access to extended FSC features (e.g., Interest Tags, Need-Based Referrals), but it is not a license type. Extension permission sets are assigned to users who already have an FSC or FSC Basic license.

References:
Salesforce Help: “Financial Services Cloud Licensing” – explains the difference between FSC (full) and FSC Basic licenses.

FSC Implementation Guide: “Assign FSC Basic Licenses to Frontline Users” – recommends FSC Basic for tellers, call center agents, and other limited-access roles.

Salesforce Pricing & Packaging: Lists FSC Basic as the restricted, lower-cost license option for financial institutions.

Key Concept:
FSC Basic is the restricted license designed for high-volume, limited-access users such as:

- Bank tellers
- Call center agents
- Back-office operations staff

It provides access to essential FSC data (client profiles, accounts, households) without the full cost of a full FSC license, enabling cost-effective scaling while maintaining a unified client view across the organization.

A.   OmniScripts

B.   Integration Procedures

E.   Business Rules Engine

Explanation:

OmniScripts (A):
Used to build guided, multi-step processes for customers.
Perfect for collecting contact info, address, driver’s age, car model/year via forms on the website.
Provides the user-facing experience.

Integration Procedures (B):
Executes server-side logic without user interaction.
Ideal for calling external systems or Salesforce APIs to save the offer to the client’s record.
Ensures efficient data handling and avoids multiple round trips.

Business Rules Engine (E):
Applies decision logic to calculate the insurance quote based on customer-provided data (e.g., age, car year/model).
Centralizes business rules so they can be reused and updated without code.
Ensures compliance and consistency in quote calculations.

❌ Why not the other options?

C. FlexCards: Used for displaying contextual information (e.g., showing quotes or client data), not for guiding input or calculating quotes.
D. APEX Code: Not required here; OmniStudio tools provide a declarative, no-code solution for this use case.

📚 Reference:
From Salesforce OmniStudio documentation:
“Use OmniScripts to create guided interactions, Integration Procedures to orchestrate data calls, and Business Rules Engine to apply decision logic for calculations such as insurance quotes.”

B.   Bankers in Japan have been accessing FSC in Japanese, but the new bankers in China will be accessing FSC in Chinese.

D.   In Seoul, South Korea, the branch managers will be reviewing their FSC dashboards every morning in Korean, while their colleagues in " Shanghai, China, will be doing so in Chinese.

Explanation:

Salesforce Financial Services Cloud (FSC) supports multi-language implementations through Salesforce's platform-wide Translation Workbench and user language settings. This allows the same org to serve users in different countries with the user interface (UI)—including labels, buttons, picklists, page layouts, Lightning components, reports, dashboards, and FSC-specific elements—translated into each user's preferred language.
The two realistic and expected outcomes from enabling multi-language features are:

B: Users set their personal language in their user record (e.g., Japanese for existing bankers, Simplified Chinese for new bankers in China). The entire FSC experience (navigation, fields, components like ARC, Action Plans, etc.) renders in that language automatically.

D: Dashboards (including FSC prebuilt ones like Branch Performance or Referral dashboards) are fully translatable. Branch managers in different countries can view the same dashboards in their local language (Korean in Seoul, Chinese in Shanghai), improving adoption and usability.

These reflect standard multi-language benefits: localized UI per user while sharing a single org.

Why not A? Referrals are data records (extended Leads). Record data (e.g., referral description) is entered in whatever language the user chooses, but it is not automatically translated. The system does not force or share referrals in specific languages by region—data remains as entered.

Why not C? Standard FSC objects (Account, Contact/Individual) and fields support translated labels, but record data (e.g., client names) is stored as entered (often in local script like Kanji). More importantly, permission sets/profiles (Advisor, Personal Banker, etc.) are internal setup elements—their names and permissions are not translated; they remain in English regardless of user language.

References:
Salesforce Help: Multi-Language Support in Salesforce – UI elements translate based on user language.
Salesforce Help: Translate Financial Services Cloud – FSC components, dashboards, and reports support full translation.
Trailhead: Global Implementations with FSC – Emphasizes per-user language for UI and dashboards in multi-country rollouts.

D.   Utilize a field mapping file with the external system (allocation and the corresponding field in Salesforce

Explanation:

Why it's correct: A field mapping file (or a data mapping specification) is the standard blueprint used in systems integration. It serves as the bridge between the external system's schema and the Salesforce object's API names.
The Process: The consultant defines that External Field $X$ maps to Salesforce Field $Y$. This document is then used to configure the middleware (such as MuleSoft, Informatica, or a custom API) to ensure that when the external system sends a payload, the data "lands" in the correct location.
Key Components: A robust mapping file typically includes the Source Field Name, Target Salesforce API Name, Data Type (e.g., String, Boolean), and any required transformations (e.g., converting a "Yes/No" to "True/False").

Analysis of Incorrect Answers
Option [A]: Create a junction object...
Why it's incorrect: A junction object is used within Salesforce to create a Many-to-Many relationship between two objects. It is a data structure tool, not an integration tool. Creating a junction object does not help the external system understand which fields it should be populating.

Option [B]: Ensure custom metadata is configured...
Why it's incorrect: While Custom Metadata can be used to store mapping logic for custom-built Apex integrations, it is a complex, developer-heavy approach. Option D represents the broader, more standard requirement for ensuring data integrity during any integration project.

Option [C]: Use a CSV file... and Data Loader...
Why it's incorrect: The prompt specifically mentions that records will be created through integration with another system, which implies an automated or real-time process. Data Loader is a manual tool for bulk uploads and is not used for ongoing, automated system-to-system integrations.

Reference
Salesforce Developer Guide: Best Practices for Data Integration
Salesforce Help: Data Mapping for Industry Clouds

A.   An RBL (Rollup By Lookup) rule displays summary calculations of financial account information, such as account balances.

C.   The Rollup By Lookup (RBL) configuration updates the corresponding RBL summaries at the diem and group levels

D.   Salesforce does not recommend or provide support for creation or customization of Financial Services Cloud RBL rules

Explanation:

Rollup By Lookup (RBL) is the underlying mechanism FSC uses to aggregate data dynamically across different objects and hierarchies (like accounts in a household) to populate the Financial Summary component.

A: The core function of RBL is exactly this: calculating summaries (totals, counts, etc.) of related records, such as rolling up individual account balances to a household or client level.

C: RBL is designed to work at two main levels: the individual client level (on the Contact record, typically for Person Account models) and the group/household level (on the Account record). It ensures consistency across these summaries.

D: This is a crucial compliance and support statement from Salesforce. RBL is a core, highly complex, managed package feature. Salesforce officially recommends against customizing or creating new RBL rules due to the potential for breaking core FSC functionality and losing support. Administrators should use the pre-configured rollups provided by Salesforce.

Why other options are incorrect

B: Person Accounts needed: The RBL functionality works perfectly well in organizations using the standard Business Account/Contact model (B2B/B2C approach). Person Accounts are not a prerequisite.

E: RBL requires processing power: RBL operations can be computationally intensive, especially in large organizations with complex data models. They are often run as scheduled batch jobs overnight because they require significant processing power and can impact system performance during peak hours if run in real-time.

B.   Individuals, then Financial Accounts, then Financial Account Roles, then Financial Account Transactions

Explanation:

When migrating data into Salesforce Financial Services Cloud (FSC), the order is critical due to object dependencies and lookup/master-detail relationships in the FSC data model:

Individuals (or Person Accounts/Accounts + Contacts) must be loaded first.
These represent the clients (people or businesses) and serve as the foundation for the FSC data model.

Financial Accounts are loaded next.
Financial Accounts (e.g., checking, savings, investment accounts) have a lookup to the Account (Individual or Household/Business). The owning client must exist before the account can be created.

Financial Account Roles are loaded after Financial Accounts.
This object links Individuals to Financial Accounts (e.g., Joint Owner, Beneficiary, Authorized Signer). It has master-detail or lookup relationships to both Financial Account and Account/Individual, so both parent records must already exist.

Financial Account Transactions (or FinServ__FinancialAccountTransaction__c) are loaded last.
These are child records with a master-detail relationship to Financial Account. The parent Financial Account must exist first.

Loading in any other order will cause failures due to missing parent records (lookup errors).

Why not the other options?

A: Incorrect because Financial Account Roles must come after Financial Accounts (not before).

C & D: Incorrect because Financial Accounts (and their children) depend on Individuals/Accounts existing first. Starting with Financial Accounts would fail due to missing owner/account lookups.

References:
Salesforce Help: Financial Services Cloud Data Model Best Practices
Trailhead: Prepare Data for Financial Services Cloud – Recommends loading Accounts/Individuals → Financial Accounts → Roles → Transactions/Holdings.
FSC Implementation Guide & Professional Services Data Migration Playbooks: Emphasize dependency-based load order starting with core client records.

B.   Enable Compliant Data Sharing for Interaction Summaries.

D.   Use Interaction Summary Participants to provide the right access to individuals or groups.

E.   Disable Role-Hierarchy-Based Sharing for Interaction Summaries.

Explanation:

Why these three
The bank wants tight control over the sensitive “detailed notes”, while attendees and meeting dates aren’t sensitive. In FSC, the sensitive narrative/notes are typically captured in Interaction Summaries, and Salesforce provides Compliant Data Sharing (CDS) + Participants to control who can see those summaries.

✅ B. Enable Compliant Data Sharing for Interaction Summaries
Why: CDS lets you control access to Interaction Summaries more granularly (beyond standard sharing), which is exactly what you need when notes are sensitive.

✅ D. Use Interaction Summary Participants to provide the right access to individuals or groups
Why: With CDS, access is granted via Participants (users or groups) on the Interaction Summary, so only cleared individuals/groups can view the sensitive content.

✅ E. Disable Role-Hierarchy-Based Sharing for Interaction Summaries
Why: If role-hierarchy sharing stays enabled, supervisors could inherit access automatically—exactly what the bank wants to avoid. Disabling role-hierarchy-based sharing prevents that “automatic visibility” for Interaction Summaries.

Why the other options are not selected

A. Enable Compliant Data Sharing for Interactions — Not required here
The prompt says basic attendee/date info isn’t sensitive, so you don’t need to lock down Interactions themselves with CDS—only the Interaction Summaries that contain detailed notes. (You could enable it, but it’s not necessary to meet the stated requirement.)

C. Disable Role-Hierarchy-Based Sharing for Engagement Interactions — Not needed
Same reason as A: the bank is okay with basic Interaction info being broadly visible, so there’s no requirement to restrict Interaction access via role hierarchy.

A.   Ensure Person Accounts is enabled on the org

B.   Configure your Person Account record types m the Indrvidual Record Type Mapper.

D.   Use a CSV field to map PersonRecordTypeld to the Person Account RecoroTypeld and use Data Loader to update Client Records

Explanation:

Step A: Enable Person Accounts
Why it's necessary: Person Accounts are not enabled by default in all Salesforce environments. Because enabling them is an irreversible action and requires a specific organizational configuration (including setting the Organization-Wide Default for Contacts to "Controlled by Parent"), this is the foundational first step. You must verify that the PersonAccount object is available in the Object Manager.

Step B: Individual Record Type Mapper
Why it's necessary: Financial Services Cloud uses Custom Metadata Types to understand how to treat different record types. The Individual Record Type Mapper tells the FSC managed package code which Account record types should behave like "Individuals" (Person Accounts). Without this mapping, FSC features like the Relationship Map and Rollups may not function correctly for the newly converted records.

Step D: Data Migration via Data Loader
Why it's necessary: Converting existing "Individual" data (Account + Contact) into Person Accounts is essentially a data update. By assigning a Person Account Record Type ID to the RecordTypeId field on the Account record, Salesforce automatically triggers the conversion process for that record. Data Loader is the standard tool used to perform this bulk update using a CSV file containing the Account IDs and the target Person Account Record Type ID.

Analysis of Incorrect Answers

Option [C]: Enable 'Individual to Person Account Migration' in Custom Settings
Why it's incorrect: There is no such specific "Individual to Person Account Migration" toggle in FSC Custom Settings. While FSC has many settings in the Industries Application Config, the migration itself is a platform-level data operation (changing Record Types) rather than a simple checkbox switch.

Option [E]: Log a case with Salesforce to perform the conversion...
Why it's incorrect: While you must log a case to enable the Person Account feature in some older orgs, Salesforce Support does not perform the actual data migration/conversion for you. This is a task for the customer's Data Architect or Administrator to execute using tools like Data Loader.

Reference
Salesforce Help: Enable Person Accounts
Salesforce Help: Map Person Account Record Types for Financial Services Cloud

D.   The Send Documents flow for Retail Banking

Explanation:

As of January 2026, Salesforce FSC continues to emphasize its out-of-the-box (OOTB) industry flows to solve common operational bottlenecks in banking.

Why D is correct: The Send Documents flow for Retail Banking is a prebuilt, templated flow designed specifically to streamline the document collection process. It allows agents to initiate document requests directly from within Salesforce, often integrating with e-signature tools (like DocuSign). Because the request and its status are tracked directly in FSC, customer service agents gain a single, consolidated view of what has been sent, what is pending, and what has been received—eliminating the need to check "multiple systems".

Why others are incorrect:
A: While Marketing Cloud can automate communication, it is an external platform that doesn't inherently solve the problem of agents lacking a unified view of document status within the core FSC service console.
B: Apex is a custom code solution. Salesforce's best practice is to always use declarative tools (like prebuilt Flows) before resorting to custom code.
C: Process Builder is a retired tool that has been superseded by Salesforce Flow. Modern solutions should not be built on Process Builder.

Reference
Salesforce provides industry-specialized workflows in the Lightning Flow for FSC package to automate routine banking tasks.
Salesforce Help: Automate Repeatable Tasks with Action Plans and Flows
Salesforce FSC Admin Guide: Track Required Customer Documents

A.   Member

C.   Trust

E.   Peer

Explanation:

In Salesforce Financial Services Cloud (FSC), the Actionable Relationship Center (ARC) uses the Association Type picklist field (on the Account-Account Relationship object) to categorize and control how account-account relationships are displayed in the relationship graph.
The standard Association Type picklist values that control specific visualizations and behaviors in ARC include:

A. Member – Used for group membership relationships (e.g., an individual or entity that is a member of a household, trust, or business group).
C. Trust – Explicitly defines a trust entity and its relationships (e.g., grantor, trustee, beneficiary) in wealth and estate planning scenarios.
E. Peer – Used for horizontal/sibling relationships (e.g., business partners, co-owners, or affiliated entities at the same level).

These values trigger specific node types, icons, and connection styles in the ARC graph.

Why not B (Group)? There is no standard "Group" value in the Association Type picklist. Group concepts are handled via Member relationships and group record types.
Why not D (Family)? "Family" is not a standard Association Type value. Family relationships are typically modeled using household groups and Member associations.

References:
Salesforce Help: Account-Account Relationship Fields – Lists Association Type values including Member, Trust, Peer, etc.
Trailhead: Enhanced Account-Account Relationships – Describes how Association Types like Trust, Peer, and Member control ARC display.
FSC Data Model Documentation: Confirms standard picklist values used in relationship mapping and ARC graphs.