Cumulus Insurance has a franchise business model with a large number of franchisees who operate independently but report to regional managers who are Cumulus employees. The company would like the franchise owners and their employees to have access to the Cumulus Salesforce Financial Services Cloud (FSC) instance. The company plans to use the Role Hierarchy and sharing rules to implement this. What should the architect at Cumulus Insurance be aware of for this solution?
A. Franchise users will need to switch their browsers to a platform that supports Lightning Web Components.
B. Salesforce FSC only allows 1,024 public groups.
C. The administrator can define up to 300 total sharing rules for each object.
D. Franchise users can have multiple roles in the hierarchy.
Explanation:
Cumulus Insurance plans to use Role Hierarchy and sharing rules to grant franchise owners and their employees access to the FSC instance. Regional managers (Cumulus employees) will be higher in the role hierarchy, and sharing rules will likely be used to extend access across franchisees or to specific records.
The key limitation the architect must be aware of is:
Salesforce allows a maximum of 300 sharing rules per object (this includes owner-based and criteria-based sharing rules combined).
In a franchise model with a large number of independent franchisees, each potentially requiring distinct sharing rules (e.g., to share records with their own franchise public group or role), the 300-rule limit per object can become a significant constraint. Exceeding it would force the architect to explore alternatives like manual sharing, Apex sharing, or restrictive sharing models.
Why not A? Lightning Web Components are fully supported on all modern browsers; there is no requirement to switch browsers for external users (e.g., via Experience Cloud).
Why not B? The limit on public groups is 10,000 per org, not 1,024. While public groups are often used in sharing rules, this is not the primary constraint here.
Why not D? Salesforce users cannot have multiple roles in the role hierarchy. A user is assigned one role at a time. Multiple roles are not supported (though a user can belong to multiple public groups or have multiple permission sets).
References:
Salesforce Help: Sharing Rule Limits – Confirms maximum of 300 sharing rules per object.
Salesforce Help: Role Hierarchy Overview – A user can have only one role.
FSC Implementation Considerations: Large partner/franchisee models often hit sharing rule limits when using criteria-based or group-based sharing extensively.
Cumulus Cloud Bank, a major financial services provider, has engaged Salesforce Professional Services to transform its operations with Financial Services Cloud (FSC). The Addams family are wealth management clients with the following relationships:
• The wife and her husband are part of the Addams Household.
•The wife is the primary member, and together the couple run the Addams Charitable Trust.
• The wife is also part of the Symonds Household with her father as the primary member.
Which tool should the Salesforce FSC consultant recommend so a wealth manager could make sense of this complex data to provide impeccable service to the Addams family and discover new business opportunities?
A. Data Filtering and Sorting in Tableau Desktop
B. Financial Services Cloud Einstein
C. Data Visualization with Marketing Cloud Intelligence
D. Actionable Relationship Center (ARC), an advanced visualization engine
Explanation:
The Actionable Relationship Center (ARC) is specifically designed in Financial Services Cloud to visualize complex client relationships and household structures—exactly like the multi‑household, multi‑role scenario described.
A. Incorrect: Tableau Desktop is a powerful analytics tool, but it is not native to FSC and does not provide the interactive, contextual relationship visualization that ARC offers directly within Salesforce for relationship managers.
B. Incorrect: FSC Einstein provides AI insights (e.g., scoring, predictions), but it is not primarily a relationship visualization tool for untangling complex household and group affiliations.
C. Incorrect: Marketing Cloud Intelligence (formerly Datorama) is for marketing analytics, not for visualizing client relationship hierarchies and household structures within FSC.
D. Correct: ARC is FSC’s advanced relationship visualization engine. It displays connections between individuals, households, groups, and related records (accounts, opportunities, interactions) in an interactive graph, allowing wealth managers to:
- See that the wife belongs to two households (Addams and Symonds)
- Understand her role as primary member in the Addams Household
- View the Addams Charitable Trust as a related group
- Navigate easily between relationships to provide holistic service and identify new opportunities
References:
Salesforce Help: “Visualize Relationships with the Actionable Relationship Center” – explains how ARC maps complex client connections.
Financial Services Cloud Implementation Guide: “ARC for Wealth Management” – highlights how wealth managers use ARC to understand multi‑household relationships.
Release Notes: “Actionable Relationship Center Advanced Visualization” – describes ARC as the tool for making sense of intricate family and group structures.
Key Concept:
ARC is the central relationship visualization tool in FSC. It turns complex relationship data (multiple households, groups, roles) into an intuitive, interactive graph, enabling financial advisors to:
- Quickly understand client affiliations
- Navigate between related records
- Identify hidden connections for new business opportunities
- Provide context‑aware service based on the full relationship picture
This is a core differentiator of FSC for wealth management and private banking.
An asset management firm that is moving to Salesforce from its old CRM wants to be able to bring over its client data on drivers’ licenses and passports. 55m 058 Which Financial Services Cloud object should a consultant recommend?
A. Document Checklist Item
B. Received Document
C. Identification Document
D. Identity Document
Explanation:
In Financial Services Cloud (FSC), the Identification Document object is specifically designed to store personal identification details such as:
- Driver’s license
- Passport
- National ID card
It allows financial institutions to securely capture and manage client identity information for compliance, KYC (Know Your Customer), and onboarding processes.
❌ Why not the other options?
A. Document Checklist Item → Used to track required documents in a process (e.g., loan application checklist), not to store actual ID details.
B. Received Document → Used to track documents received from clients (e.g., signed forms), not structured ID data.
D. Identity Document → This is a distractor; the correct FSC object name is Identification Document, not Identity Document.
📚 Reference:
From Salesforce FSC documentation:
“Use the Identification Document object to capture details of government-issued IDs such as driver’s licenses and passports.”
What actions can a Wealth Advisor take from the Life Events card7
A. Create Case
B. Create Lead & Referral
C. Open an Account
D. Request Record Approval
E. Create Opportunity
Explanation:
B. Create Lead & Referral:
Why it's correct: Life events (like the birth of a child or a job change) are natural triggers for new services. This action allows an advisor to immediately capture a lead for a new product or refer the client to a different department (e.g., Mortgage or Insurance) based on that event.
D. Request Record Approval:
Why it's correct: In highly regulated environments, certain updates or milestones might require a manager's review or compliance sign-off. The Life Events card supports triggering an Approval Process directly to ensure the data captured meets the bank's quality and regulatory standards.
E. Create Opportunity:
Why it's correct: Similar to leads, life events often represent a concrete sales opportunity (e.g., an "Education Savings" opportunity triggered by a "Birth" event). Creating an opportunity directly from the card automatically links it to the specific life event, providing a clear audit trail of why the deal was initiated.
Analysis of Incorrect Answers
A. Create Case:
Why it's incorrect: While cases are used for service requests, they are typically initiated from the "Actions" menu, the "Related" list, or a "Global Action." Standard FSC configuration for the Life Events hover card focuses on Growth (Leads/Opportunities) and Compliance (Approvals) rather than transactional service tickets.
C. Open an Account:
Why it's incorrect: "Opening an Account" is a complex business process that usually involves a multi-step Flow, OmniScript, or integration with a core banking system. While a Life Event might trigger the need for a new account, the account opening itself is too heavy a process to be executed directly from a simple hover card action; instead, you would create an Opportunity or Lead to start that journey.
Reference
Salesforce Help: Create and Configure Contextual Actions for Events and Milestones
Salesforce Help: Events and Milestones for Financial Services Cloud
Lake Tahoe Bank is implementing Financial Services Cloud. The bank's new business processes require that Financial Advisors can add individuals to more than one Group or Household using Multiple Relationship Groups. Where do Admins enable Multiple Relationship Groups?
A. Object Settings
B. Custom Settings
C. Lightning Page Editor
D. Profiles
Explanation:
Why B is correct?
In Financial Services Cloud, Multiple Relationship Groups is controlled by an FSC managed-package configuration flag, not by object permissions or page layout settings. Admins enable it from Setup → Custom Settings → Industries Application Config → Manage → Edit, then check Multiple Relationship Groups (or ensure it’s enabled).
Why the other options are wrong
A. Object Settings — Object settings control CRUD/FLS, record types, etc., but this feature is governed by FSC package configuration.
C. Lightning Page Editor — Lightning pages control UI visibility/placement, not whether a person can belong to multiple relationship groups.
D. Profiles — Profiles affect access/visibility, but they don’t enable/disable the Multiple Relationship Groups capability itself.
Reference
Steps and location: Custom Settings → Industries Application Config
A bank recently sold its wealth management division and wants to improve its customers’ digital experience. The bank engaged Salesforce Professional Services to upgrade its existing Salesforce CRM to Financial Services Cloud and deliver its Bank of the Future vision. Which three expected outcomes can serve as return on investment (ROI) justifications to the bank's chief financial officer (CFO) and investment committee?
A. 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.
B. 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.
C. Simplify the client onboarding process with proper tools to streamline customer discovery and internal reviews through renewal.
D. Manage policy holder’s interactions with customer service agents intelligently through the underwriting process.
E. Modernize client-advisor experiences from engagement to relationship management to effectively drive long-term, trusted relationships.
Explanation:
A. Unify and improve team collaboration by sharing and managing customer leads and referrals across multiple lines of business
Why this is correct:
Financial Services Cloud enables cross-line-of-business collaboration (Retail Banking, Commercial, Wealth, etc.) using shared client profiles, relationship groups, and referrals. This directly improves revenue growth, cross-sell opportunities, and operational efficiency — all strong ROI drivers.
ROI impact:
Increased wallet share
Better lead conversion
Reduced data silos
B. Deliver connected and personalized digital experiences through a 360-degree customer view
Why this is correct:
A core value of FSC is creating a single source of truth by consolidating data from multiple systems (CRM, core banking, marketing, service, etc.). This enables personalized digital journeys and improves customer satisfaction and retention.
ROI impact:
Higher customer engagement
Improved retention and lifetime value
Reduced servicing costs
E. Modernize client-advisor experiences to drive trusted long-term relationships
Why this is correct:
FSC is designed to modernize advisor workflows, relationship insights, and engagement tools—especially critical after divesting a business unit like wealth management. This directly supports productivity and relationship-driven revenue growth.
ROI impact:
Faster advisor productivity
Better relationship management
Increased client trust and loyalty
❌ Incorrect Options
C. Simplify the client onboarding process with proper tools
While onboarding improvements are supported in FSC, this option is more operational than strategic and is not typically highlighted as a top-level ROI justification for a CFO compared to revenue growth, experience modernization, and cross-LOB enablement.
D. Manage policy holder interactions through underwriting
This is Insurance Cloud, not Financial Services Cloud for Banking. Key terms like policy holder and underwriting apply to insurance, not banking.
Lake Tahoe Bank is rolling out Financial Services Cloud and the VP of IT is concerned about the cost of the licenses. The System Admin recommends using restricted licenses for users that need only limited access to Financial Service Cloud features. Which Financial Services Cloud permission set license enables user access to a license with contractual restrictions for Financial Services Cloud and can be used to grant restricted access to users like Bank Tellers?
A. Financial Services Cloud Standard
B. Client Segmentation
C. Financial Service Cloud Basic
D. Financial Service Cloud Extension
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.
An insurance company wants to create a car insurance quote process for its website. The process should include the following functionality:
• The user has to enter contact and address information.
• The user has to enter the driver's age and the car model and year.
• The process should calculate an insurance quote based on the data the customer provided and save the offer to the client's record.
Which three OmniStudio tools should the consultant use to design a solution that meets these requirements?
A. OmniScripts
B. Integration Procedures
C. FlexCards
D. APEX Code
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.”
A major Japanese bank is expanding geographically and opening additional branches in Asia. As such, they hired a regional consulting firm to implement Financial Services Cloud (FSC) locally. What are the two expectations from implementing multi language features in FSC?
A. Referrals in Singapore and Hong Kong will be shared in English, but in Macau, referrals will be shared in Portuguese.
B. Bankers in Japan have been accessing FSC in Japanese, but the new bankers in China will be accessing FSC in Chinese.
C. In Tokyo branches, the names of the Account, Prospect & Contact are in Japanese, but the package Advisor, Personal Banker, D Relationship Manager, and Client Associate profiles are in English.
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.
A new custom object has been created, and the records of this object will be created through integration with another system What should a consultant do to ensure the data is loading into the correct fields in Financial Services Cloud?
A. Create a junction object between the external system and the new customer object where the data will reside
B. Ensure custom metadata is configured and each custom metadata record details where the data will be sent
C. Use a CSV file with the data created and use Data Loader to map to the correct field
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
Which three of these statements are true for Rollup By Lookup (RBL) in Financial Services Cloud?
A. An RBL (Rollup By Lookup) rule displays summary calculations of financial account information, such as account balances.
B. Person Accounts need to be enabled in order to use the Rollup by Lookup functionality.
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
E. RBL rules do not require a lot of processing power.
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.
Cumulus Bank is migrating its CRM software from a legacy application to Salesforce Financial Services Cloud (FSC). The bank hired Salesforce Professional Services to configure/deploy the new Salesforce FSC org and migrate data. Which order should a consultant follow when performing the data migrations?
A. Individuals, then Financial Account Roles, then Financial Accounts, then Financial Account Transactions
B. Individuals, then Financial Accounts, then Financial Account Roles, then Financial Account Transactions
C. Financial Accounts, then Financial Account Roles, then Individuals, then Financial Account Transactions
D. Financial Accounts, then Financial Account Transactions, thenVinancial Account Roles, then Individuals
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.
| Page 3 out of 15 Pages |
| Previous |