Total 171 Questions
Last Updated On : 29-Jan-2026
What capability included in the Financial Services Cloud license can assist bankers in focusing on the most promising referrals?
A. Referral Approval Processes
B. Intelligent Need-Based Referrals and Scoring
C. Einstein Referral Scoring for Financial Services Cloud
D. Referral Routing Rules
Explanation:
Intelligent Need-Based Referrals and Scoring is a native FSC capability that helps bankers prioritize referrals by automatically scoring them based on client needs, likelihood of success, and other criteria.
A. Referral Approval Processes – While referral approvals are part of workflow management, they don't inherently help prioritize or identify the "most promising" referrals.
B. Intelligent Need-Based Referrals and Scoring – Correct. This FSC feature uses data and rules to score and rank referrals, helping bankers focus on high-potential opportunities. It's specifically designed to increase referral conversion rates through intelligent prioritization.
C. Einstein Referral Scoring for Financial Services Cloud – This is a distractor. While Einstein AI capabilities exist in Salesforce, the specific feature name is "Intelligent Need-Based Referrals and Scoring." There isn't a separately named "Einstein Referral Scoring" feature in core FSC.
D. Referral Routing Rules – These help direct referrals to appropriate bankers but don't provide scoring or prioritization intelligence about which referrals are most promising.
References:
Salesforce Help: "Intelligent Need-Based Referrals and Scoring" – describes how this feature analyzes client data to score and prioritize referrals.
Financial Services Cloud Release Notes: "Increase Referral Conversion with Intelligent Scoring" – explains the business value of this capability.
FSC Implementation Guide: "Set Up Referral Scoring" – provides configuration steps for enabling referral prioritization.
Key Concept:
FSC includes industry-specific intelligence features like referral scoring that go beyond basic CRM functionality. This capability uses client data (financial holdings, life events, interactions) to automatically assess referral quality, helping bankers focus on high-value opportunities rather than treating all referrals equally.
An insurance company needs to ensure the record rollups aggregate information from related records for several objects in the Financial Services Cloud at a client or group level. What should the administrator configure to meet the requirement?
A. To show all Primary Group member cases on a related list at the group level, the administrator should add Cases as a picklist value to the Rollup__c field on Account Contact Relationship.
B. Client-level records are aggregated by setting up client-level rollups to all primary group members.
C. When the administrator enables record rollups at the group level, all corresponding records are stamped with the Primary Group in the Rallup_c lookup field
D. To show all Primary Group member opportunities on a related list at the group level, the administrator should add Opportunities as a picklist value to the Household__c field on Account Contact Relationship.
Explanation:
In Salesforce Financial Services Cloud (FSC), record rollups aggregate data from related records (e.g., financial accounts, assets/liabilities, cases, opportunities) at both the client level (default, no setup needed) and group level (e.g., household or primary group).
To enable aggregation at the group level for multiple objects:
- The administrator enables group-level record rollups (via setup or managed package settings).
- This automatically stamps relevant records with the Primary Group in the Rollup__c (or sometimes referenced as Household__c) lookup field on objects like Account, Contact, Account Contact Relationship, and others.
- The stamping allows related records from primary group members to roll up and display aggregated summaries or related lists at the group record (e.g., total assets, open cases).
This meets the requirement for holistic aggregation at client or group level without custom development.
Why not A? Adding "Cases" to the Rollups__c picklist on Account Contact Relationship enables group-level related lists for Cases specifically (common for insurance scenarios), but it's not the general configuration for aggregating multiple objects at group level.
Why not B? Client-level aggregation is automatic and does not require "setting up rollups to primary group members."
Why not D? Opportunities would use the Rollups__c picklist (not Household__c), and this is object-specific, not the broad group-level enablement.
References:
Trailhead: Configure Record Rollups – Describes enabling group-level rollups and stamping records with the Primary Group in the lookup field (variously noted as Household__c or Rollup__c).
Trailhead: Meet Record Rollups – "You can enable group-level rollups to aggregate related records for all primary group members."
Salesforce Help/Trailhead: Adding specific objects (e.g., Cases) to Rollups__c picklist for related list visibility.
Scott Adams is opening a joint savings account with his mom, Rachel Adams. Rachel Adams is the primary member of the Adams Household. Personal Banker Hank Burton wants to make sure that Scott's data is rolling up to the Adams Household. How can the Banker accomplish this?
A. Make the Adams Household Scott's primary Group and edit tie Activities & Objects to ft* Up.
B. Add Scon as a Related Contact to the Adams Household.
C. Make the Adams Household Scotts pnmary Group and make Scott the pnmary member
D. Disable the Primary Group setting fof Scon on the Adams Household
Explanation:
In Financial Services Cloud (FSC), rollups aggregate data (activities, opportunities, financial accounts, etc.) from primary group members up to the household or group level.
For Scott’s data to roll up to the Adams Household, the banker must:
- Set the Adams Household as Scott’s primary group.
- Configure the Activities & Objects to roll up so that Scott’s records (e.g., savings account activity) are included in the household view.
This ensures that Rachel, as the primary member, and the banker can see Scott’s joint account information at the household level.
❌ Why not the other options?
B. Add Scott as a Related Contact to the Adams Household → Related contacts don’t trigger rollups; only primary group membership does.
C. Make the Adams Household Scott’s primary group and make Scott the primary member → Making Scott the primary member would incorrectly replace Rachel as the household’s primary member.
D. Disable the Primary Group setting for Scott on the Adams Household → This would prevent rollups entirely, which is the opposite of what’s needed.
📚 Reference:
From Salesforce FSC documentation:
“Record rollups aggregate information from primary group members to the household or business group. To enable rollups, set the household as the client’s primary group and configure the rollup settings for activities and objects.”
The Salesforce Administrator for Lake Tahoe Bank is receiving a report that a members Financial Account Balances are not adding up to the Financial Summary field in the related Household. Which two steps should the admin take to troubleshoot the issue?
A. Ensure the Primary Group flag in the Account record is checked.
B. Ensure RollUpByLookup Configuration is Active
C. Ensure a RollUpByLookup batch job is scheduled to run every 15 mins.
D. Ensure that the member is the Primary Member in that Household
E. Ensure the reported Household is the Primary Group for the member
Explanation:
B. Ensure RollUpByLookup Configuration is Active:
Why it's correct: In FSC, Rollup By Lookup (RBL) is the specific technology used to aggregate numeric values (like account balances) from the Financial Account object up to the Account/Household level. These are managed via the Rollup By Lookup Configuration custom metadata or settings. If the specific RBL rule for "Total Financial Account Balance" is inactive, the system will not update the summary field, even if the data is correct.
E. Ensure the reported Household is the Primary Group for the member:
Why it's correct: As established in the FSC data model, an individual can belong to multiple groups, but the system only rolls up financial data to the group designated as the Primary Group (via the Account Contact Relationship record). If the Household in question is not marked as "Primary" for that specific member, their individual balances will not be included in that Household's summary total.
Analysis of Incorrect Answers
A. Ensure the Primary Group flag in the Account record is checked:
Why it's incorrect: The "Primary Group" checkbox is not located on the Account record itself; it is a field on the Account Contact Relationship (ACR) record that connects the person to the household.
C. Ensure a RollUpByLookup batch job is scheduled to run every 15 mins:
Why it's incorrect: While RBL can be run in batch mode, it is typically triggered in real-time or via a daily batch job. There is no standard requirement or recommended "15-minute" interval for this specific job, and if the configuration is inactive (Option B), the frequency of the job won't matter.
D. Ensure that the member is the Primary Member in that Household:
Why it's incorrect: Every member of a household can have their balances roll up to the total, not just the "Primary Member." A child’s savings account or a spouse’s IRA will roll up to the Household total as long as the Household is their Primary Group.
Reference
Salesforce Help: Rollup By Lookup (RBL) in Financial Services Cloud
Salesforce Help: Set Up and Configure RBL Rules
Lake Tahoe Bank would like to reslricl their Financial Services Cloud users from viewing certain types of milestones that might be irrelevant to their customers or might cause negative sentiment. How can the Salesforce Admin implement such a requirement?
A. The Salesforce Admin can manage sensitive Life Evenls using sharing rules.
B. The Salesforce Admin can hide the life Event or Business Milestone type, by removing it from the Event Type picklist.
C. The Salesforce Admin can hide sensitive Life Events on Ihe Life Events component on the Lightning Page using the Properties pane.
D. The Salesforce Admin can manage sensitive Life Events using Permission Sets.
Explanation:
In Salesforce Financial Services Cloud (FSC), the Life Events or Business Milestones Lightning component (added to record pages like Person Account or Household) displays events and milestones based on their Event Type or Milestone Type.
To restrict users from viewing certain types that are irrelevant or could cause negative sentiment (e.g., sensitive events like "Divorce" or "Death"):
- Edit the Lightning Record Page in App Builder.
- Select the Life Events or Business Milestones component.
- In the Properties pane, there is a section to select/deselect specific Event Types or Milestone Types to show or hide them in the component.
This declaratively hides selected types across all users viewing the page, preventing display of potentially sensitive or irrelevant milestones without affecting data creation or other views.
Why not A? Sharing rules control record-level access (who can see individual Life Event records), not the visibility of entire event types in the component.
Why not B? Removing a value from the Event Type picklist would prevent creation of that type entirely (and could impact existing records), which is too restrictive and not the intended way to hide display in the component.
Why not D? Permission sets control object/field access or feature permissions but do not filter specific picklist value types within the Life Events component.
References:
Salesforce Help: Hide Sensitive Event Types and Milestone Types – Describes configuring visibility of event/milestone types directly in the component properties.
Trailhead: Insurance for FSC Admin modules (e.g., Set Up Life Events and Business Milestones) – Covers adding the component and customizing displayed types via properties.
FSC Documentation & Release Notes: Confirms selective hiding of types in the Lightning component properties pane for sensitivity or relevance.
A consultant is looking to create a guided screen to be used by customer service agents answering the phone to authenticate the caller and positively identify them. The agent will ask the caller to provide their full name and the last four digits of their social security number, which is not stored in Salesforce. The agent will enter the provided information into a form, and upon clicking submit, a web service call is made to an external authentication service to authenticate the caller. What should the consultant do to fulfill the needed requirements?
A. Create a screen flow.
B. Create a Lightning web component.
C. Create a Canvas application for the Authentication module.
D. Create an OmniScript flow.
Explanation:
Why this is correct
An OmniScript (OmniStudio) is designed for guided, multi-step agent scripts (perfect for call center authentication) and can:
- Collect input that isn’t stored in Salesforce (captured as JSON during the interaction)
- Execute external service callouts using Action elements (often via an Integration Procedure that performs HTTP actions / API calls)
- Support conditional/branching logic and step-by-step screens for agents
Salesforce explicitly describes OmniScripts as guided interactions that can get/update data from Salesforce and external data sources, and notes that OmniScript actions can use APIs / Integration Procedures to call external systems.
Why the other options are less suitable
A. Screen Flow — Flows can integrate with external services (e.g., HTTP Callout / External Services), but the scenario is a classic Industries/FSC guided agent script pattern where OmniScript is the intended tool, especially when capturing transient inputs and orchestrating an external verification step.
B. Lightning Web Component — Would require custom development for the UI and integration orchestration; not necessary when OmniScript provides this declaratively.
C. Canvas application — Overkill for a guided authentication script; Canvas is typically used to embed an external UI app inside Salesforce.
Lake Tahoe Bank would like to capture their commercial customers in FSC. A commercial customer can be owned by multiple groups. How can Lake Tahoe Bank SF Admin configure FSC to capture and display commercial customer and its parent company ? (3 correct answers)
A. Add the Business record type to the Group record type mapper
B. Capture the majority owner as parent account using Account hierarchy
C. Leverage Groups to capture the majority owner and Account hierarchy to capture minority owner
D. Enable Relationship Group Hierarchy in Custom Metadata
E. Link multiple owners to the business entity as a Group
Explanation:
A. Add the Business record type to the Group record type mapper
To model a commercial customer as a “Group” (not just a generic business account), FSC uses record-type mapping so Salesforce knows which custom/Account record types should behave like standard FSC Group types. This is done through GroupRecordTypeMapper (custom metadata) which maps your custom Group record type(s) to FSC’s standard group behavior.
D. Enable Relationship Group Hierarchy in Custom Metadata
Because the commercial customer can be owned by multiple groups and you also need to display the commercial customer and its parent company, you enable Relationship Group Hierarchy so FSC can represent and visualize group-to-group hierarchies/relationships (expanded relationship group hierarchies). Salesforce explicitly calls out enabling this via the Enable Relationship Group Hierarchy custom metadata types.
E. Link multiple owners to the business entity as a Group
FSC’s Party Relationship Groups are designed to connect clients, households, and business entities, and can include relationships to other groups—which is the right pattern when a business entity can be associated with multiple owning groups.
Why the others aren’t correct
B. Capture the majority owner as parent account using Account hierarchy — Account hierarchy is standard Salesforce, but it doesn’t address the FSC requirement of multiple group ownership and FSC relationship-group modeling.
C. Leverage Groups to capture the majority owner and Account hierarchy to capture minority owner — This mixes two different modeling patterns in a way that doesn’t align with FSC’s intended group-to-group relationship/hierarchy approach for multiple owning groups.
An administrator is logged into Data Loader with their own credentials to insert new Business Account records into their Salesforce environment. They forget to specify the Account Owner field in the import file. Assuming there are no other issues, what should happen when the administrator uploads the import file?
A. The import will succeed, and the Account Owner field will be left blank.
B. The import will succeed, and the administrator will be prompted to select a user.
C. The import will fail, since all records in Salesforce must have an owner.
D. The import will succeed, and the administrator will be named as the default Account Owner.
Explanation:
Why it's correct: Salesforce enforces a rule that every record must be owned by a User or a Queue. When using the API (which Data Loader utilizes), if a specific owner is not provided during an Insert operation, the system automatically assigns ownership to the context user—the person whose credentials were used to log into the Data Loader.
The "Blank" Logic: Since the administrator is logged in, their User ID is used as the default value for the OwnerId field for all successfully inserted records in that batch.
Analysis of Incorrect Answers
Option [A]: The import will succeed, and the Account Owner field will be left blank.
This is impossible in Salesforce for the Account object. OwnerId is a system-required field. A record cannot exist without an owner.
Option [B]: The import will succeed, and the administrator will be prompted to select a user.
Data Loader is a bulk processing tool and does not provide interactive prompts during the execution of a job. It relies entirely on the CSV mapping and the user's settings.
Option [C]: The import will fail, since all records in Salesforce must have an owner.
While it is true that all records must have an owner, the import won't fail for this specific reason. Salesforce handles the requirement by defaulting to the user performing the upload. The import would only fail if the user lacked "Create" permissions or if other required custom fields were missing.
Reference
Salesforce Help: Data Loader Considerations
Salesforce Developers: Insert, Update, or Delete Data Using Data Loader
A financial institution has custom security and visibility rules where certain users need to see specific records even though they are not typically engaged in that Account. This includes legal and compliance members who must be engaged for particular deals. Which Financial Services Cloud capability provides the ability to accommodate this request?
A. Compliant Data Sharing
B. Custom Sharing»Rules
C. Business Rules Engine
D. Interaction Summaries
Explanation
As of January 2026, Compliant Data Sharing (CDS) remains the primary FSC feature designed for granular, role-based record visibility required by strict regulatory environments.
Why A is correct: Compliant Data Sharing allows administrators and compliance managers to define Participant Roles (such as "Legal Observer" or "Compliance Officer") with specific access levels (Read or Read/Write). It is specifically built for scenarios where specific records—such as high-value Deals or Accounts—must be shared with users who are not part of the standard account team or role hierarchy. It provides a "clicks-not-code" way to manage access to sensitive data, including Material Non-Public Information (MNPI).
Why others are incorrect:
B: While standard Sharing Rules can grant access, they are typically broad (based on public groups or roles) and lack the granular, record-by-record "Participant" model required for specific deal-based engagement.
C: The Business Rules Engine is used for automating complex decision-making logic (like calculating loan eligibility), not for record-level security and visibility.
D: Interaction Summaries are used to capture meeting notes and call logs; while they integrate with CDS to ensure notes are shared securely, they are not the mechanism that provides the visibility to the underlying Account or Opportunity.
Reference
To learn more about implementing this security model, refer to the Salesforce Help: Compliant Data Sharing and the Salesforce Architect's Guide to CDS.
A Salesforce administrator updating a record page to add a Chatter component to the Action Plan Lightning record page is unable to find the Chatter components for selection. What is the reason for this?
A. Feed tracking has to be enabled for the Action Plan object.
B. Chatter has to be enabled for Action Plans via Chatter settings in setup.
C. Salesforce is yet to roll out Chatter for the Action Plan object.
D. Admin users have to be assigned the Action Plans permission set.
Explanation:
Chatter components (like the Chatter publisher or feed) can only be added to a Lightning record page if Feed Tracking is enabled for that specific object. This applies to standard and custom objects, including the Action Plan object in Financial Services Cloud.
A. Correct: Feed Tracking must be enabled for the Action Plan object (Setup → Object Manager → Action Plan → Feed Tracking). Without this, Chatter components won't appear in the Lightning App Builder component palette for that object's record page.
B. Incorrect: Chatter is enabled org-wide, not per object via Chatter settings. The issue is object-specific feed tracking, not global Chatter activation.
C. Incorrect: Chatter is fully supported for the Action Plan object once Feed Tracking is enabled. There's no pending rollout limitation.
D. Incorrect: Permission sets control user access to records or features, but don't affect whether Chatter components are available in Lightning App Builder for page editing.
References:
Salesforce Help: “Enable Chatter Feed Tracking for an Object” – explains that feed tracking must be enabled to use Chatter components on record pages.
Lightning App Builder Guide: “Add Chatter Components to Record Pages” – states Chatter components only appear if the object has feed tracking enabled.
| Page 2 out of 18 Pages |
| Financial-Services-Cloud Practice Test Home |
Our new timed Financial-Services-Cloud practice test mirrors the exact format, number of questions, and time limit of the official exam.
The #1 challenge isn't just knowing the material; it's managing the clock. Our new simulation builds your speed and stamina.
You've studied the concepts. You've learned the material. But are you truly prepared for the pressure of the real Salesforce Financial Services Cloud (FSC) Accredited Professional - AP-208 exam?
We've launched a brand-new, timed Financial-Services-Cloud practice exam that perfectly mirrors the official exam:
✅ Same Number of Questions
✅ Same Time Limit
✅ Same Exam Feel
✅ Unique Exam Every Time
This isn't just another Financial-Services-Cloud practice questions bank. It's your ultimate preparation engine.
Enroll now and gain the unbeatable advantage of:
Copyright © - All Rights Reserved