AP-208 Salesforce Accredited Agentforce Financial Services Professional Free Practice Exam Questions (2026 Updated)

Agentforce Financial Services provides purpose-built objects for modeling customer financial information beyond standard CRM records. Among these are Financial Goal, Financial Holding, and Revenue.

The Financial Goal object represents objectives such as retirement funding, purchasing a home, education planning, or other target financial outcomes. A Financial Holding represents investments or securities held within a financial account. Salesforce references Financial Holding throughout Financial Services capabilities, including financial-detail and portfolio-performance functionality that operates on Financial Account, Financial Account Role, Financial Holding, Financial Goal, and related client records.

The Revenue object is also part of the Financial Services financial model and represents revenue generated from operating a person ' s financial account or through advisory services.

These objects complement other specialized Financial Services records such as Financial Account, Assets and Liabilities, and Identification or Identity Document, allowing institutions to construct a comprehensive view of a client ' s financial position and objectives.

Billing is associated with separate financial or insurance servicing capabilities rather than being one of the client financial-information objects represented by this question. Inheritance likewise is not the corresponding packaged FSC financial object.

The access requirement is determined by the characteristics of the Financial Account records, not by who owns those records. Therefore, the administrator should use a criteria-based Financial Account sharing rule.

Criteria-based sharing rules allow Salesforce to identify records by field values and automatically extend access to a defined user population or public group. A criteria-based sharing rule determines record access by values on the record rather than record ownership.

For this design, the Financial Account data should contain a reliable attribute that identifies employee-only deposit products—for example, an appropriate product type, record type, classification field, or another controlled criterion. The sharing rule can then identify Financial Accounts matching that criterion and extend the required access to the specific customer-service group.

An Account sharing rule would be too broad because the employees themselves must continue to be serviced as ordinary customers. The sensitive information is the special Financial Account, not necessarily the entire customer Account. Similarly, an owner-based Financial Account rule is inappropriate because whether a deposit is an employee product is independent of who owns the Salesforce record.

Salesforce sharing rules create automatic exceptions to restrictive organization-wide defaults while preserving least privilege. A criteria-based Financial Account sharing rule therefore provides the required targeted access without unnecessarily exposing the employee ' s financial products to unrelated users.

ARC custom nodes can be enhanced with OmniStudio FlexCards so that users see contextual information directly within the relationship graph. Salesforce’s configuration sequence is explicit: open or create an ARC relationship graph, select the required node, navigate to the node ' s Display tab, and select Use FlexCard for this Node. The administrator or developer then identifies the FlexCard that should render the node.

FlexCards are suitable because they provide compact, contextual displays and can expose relevant actions without forcing users to leave the relationship visualization. Developers build and activate the FlexCard in OmniStudio and associate it with the ARC node through the graph configuration. An OmniStudio license is required when FlexCards are used for ARC node customization.

The distinction in the answer choices is important. ARC does not require the developer merely to reference an arbitrary Lightning web component in the node ' s display properties. Similarly, an OmniScript action has a different purpose: it can launch a guided process, but it is not the mechanism used to control the node ' s visual representation. The Use FlexCard option on the node’s Display tab is the supported configuration for customized ARC node presentation.

The Financial Account Summary component depends on the relationship between the user ' s Locale setting and the user ' s Currency setting when rendering monetary values. Therefore, the user ' s locale must correspond appropriately with the user ' s configured currency for currency symbols, grouping separators, and other localized formatting to display correctly.

Salesforce identifies this requirement in the documented Agentforce Financial Services availability and limitations. To show commas and currency symbols correctly on the Financial Account Summary component, the user ' s locale in Locale Settings and the user ' s currency must match.

Locale controls regional presentation conventions such as numeric grouping, decimal separators, date formats, and related localization behavior. Currency determines the monetary unit represented by Financial Services values. A mismatch can therefore cause the component ' s visual currency formatting to appear inconsistent with the expected regional conventions.

This requirement is distinct from the rules governing financial-summary rollup calculations. When Multiple Currencies and Rollup By Lookup are enabled, accurate aggregation can require the user currency and account currency to correspond to the organization ' s default currency. That calculation requirement should not be confused with the display-formatting condition tested here.

The question specifically asks about the correct presentation of commas and symbols, making the user ' s locale matching the user ' s currency the applicable configuration requirement.

Reciprocal roles define the semantic relationship between two parties—for example, Client and Attorney, Parent and Child, or Spouse and Spouse. The Related Role lookup can only return reciprocal-role records that actually exist and that the current user is permitted to access.

If appropriate reciprocal roles have not been created, the lookup has no suitable role records to return. Salesforce ' s relationship model uses reciprocal or party-role relationship records to describe Contact-Contact and Account-Account relationships, and administrators can define additional role pairs when the standard vocabulary does not satisfy the business requirement.

Record visibility must also permit the user to access the reciprocal-role records. Financial Services relationship components require users to have appropriate access to the Reciprocal Role object and its fields; the preconfigured ARC relationship experience similarly requires read access to the Reciprocal Role data involved in the graph. Appropriate sharing and security configuration therefore matters when role records exist but do not appear to the user.

The issue is not fundamentally resolved by substituting a Member Relationship action or Edit Group operation. Those interfaces support different relationship-management activities. The stated problem is specifically that the Related Role lookup contains no available reciprocal roles, which points to either the absence of the reciprocal-role records or insufficient visibility to those records.

The correct Financial Services architecture is to store the confidential transaction in Financial Deal and control access through Compliant Data Sharing, with Financial Deal hierarchy-based sharing disabled.

Financial Deal Management is specifically designed for investment-banking transactions and confidential deal information. It captures deal stage, status, probability, parties, products, interactions, and related information while providing compliant, role-based data sharing for authorized stakeholders.

By default, Financial Deal participates in Salesforce role hierarchy access. However, Agentforce Financial Services provides a dedicated Role Hierarchy-Based Sharing for Financial Deals setting that can be disabled. Disabling this setting prevents users above the deal owner from automatically gaining access to deals owned by or shared with subordinates.

After hierarchy access is disabled, the administrator enables Compliant Data Sharing for Financial Deal. The banking associate can then add the trusted analyst as a Financial Deal Participant and assign an appropriate Participant Role and access level. This produces an explicit, auditable sharing grant limited to the analyst and other specifically authorized participants.

Opportunity is less appropriate because its standard hierarchy-sharing behavior cannot be disabled in the same Financial Deal-specific manner. Restriction Rules are unnecessary for this requirement because Financial Deal already provides the required combination of hierarchy suppression and participant-based CDS.

In a multi-currency Salesforce organization, currencies must first be configured as active currencies. Salesforce administrators maintain active currencies through Manage Currencies, and only active currencies can be used for record currency amount fields. Therefore, if GBP has not been activated in the org, users cannot properly create or work with GBP-denominated records.

When multiple currencies are enabled, Salesforce uses the standard CurrencyIsoCode field to identify the record ' s currency. Appropriate user-interface configuration must expose this currency identification where testers need to inspect and work with the record ' s currency.

Advanced Currency Management does not determine whether GBP is available. Its purpose is to maintain dated conversion rates, especially for opportunity-based currency conversion. Likewise, an administrator ' s personal default currency being CAD does not deactivate GBP or prevent other users from working with active currencies. Each Salesforce user can have a personal currency while records retain their individual CurrencyIsoCode values.

Therefore, the configuration should ensure that GBP is active and that the relevant record currency information is exposed to users.

Flow Orchestration structures complex, multi-user business processes by organizing work into Stages and Steps, with Work Items representing the executable assignments created for interactive steps. A Stage groups related work into a logical phase and controls when the orchestration can progress to the next phase. Steps reside within stages and can execute sequentially or concurrently depending on the process design. Salesforce supports interactive, background, and MuleSoft steps.

When an interactive step becomes active, Salesforce creates an Orchestration Work Item and assigns it to the designated user, group, or queue. The assignee completes the associated Screen Flow through the Orchestration Work Guide. Work Items therefore operationalize the human work represented by interactive steps and provide assignment, completion, and tracking information.

Current Salesforce terminology formally describes Stages and Steps as the building blocks of an orchestration, while Work Items are generated during orchestration runtime. The terminology in this question uses the broader architecture in which Steps, Stages, and Work Items constitute the three operational elements being tested. Processes and Blocks are not defined Flow Orchestration structural elements.

The Life Events experience is intended to turn significant customer events into actionable advisor workflows rather than merely display historical information. Within the supplied Financial Services curriculum, the advisor actions represented are Create Lead and Referral, Request Record Approval, and Create Opportunity.

Salesforce ' s Events and Milestones architecture implements this behavior through contextual actions. Administrators can create actions on the Person Life Event object and expose those actions in the expanded event card. This allows an advisor to act immediately when a life event indicates a new service need, sales opportunity, referral opportunity, or internal process requirement.

For example, a life event can signal a need that should become an Opportunity, a requirement that should be routed to another line of business through a Lead or Referral, or an internal decision that requires an approval action. The action is launched in the context of the customer and the life event, helping maintain traceability between the event and the resulting business process.

The exact available actions can be tailored by the organization through configuration. The core design principle is that Life Events should translate customer insight into timely, trackable advisor actions rather than remain passive informational records.

Branch Management provides reportable objects and predefined report structures that allow management to analyze branch activity, productivity, customer acquisition, and business performance. Salesforce identifies Banker, Branch Unit, Branch Unit Related Record, and Branch Unit Customer among the branch-management objects that can participate in reporting. Therefore, option B correctly describes the reporting data model.

Salesforce also provides report types such as Bankers with Branches with Opportunities, Accounts, Leads, and Contacts, enabling reporting against records associated with branch operations. These report types support analysis of operational records created or associated with particular branch units, making option A correct.

Option C reverses an important reporting limitation. When Branch Unit is used as the primary object, Branch Unit Customer and Branch Unit Related Record do not appear as selectable related objects. Salesforce recommends creating a report type where Branch Unit Customer or Branch Unit Related Record is itself the primary object and then grouping results by Branch Unit Name.

Branch Unit Related Records are specifically designed to track operational records associated with a branch and can be customized with additional fields and logic as needed.

Discovery Framework is the appropriate capability when onboarding inefficiency is caused by manual questionnaire-driven information collection and the organization must validate captured information according to business or compliance policies.

Salesforce describes Discovery Framework as the Financial Services capability for creating and managing assessment questions, surfacing digital assessments, and collecting information during customer onboarding. It can be combined with Know Your Customer data structures and other onboarding components to support structured, compliant customer intake.

Its data model allows users to collect and validate customer information in compliance with organizational policies. Discovery Framework is positioned for needs analysis, digital onboarding, and questionnaire-driven information collection. OmniStudio provides the guided digital forms, while assessment questions provide reusable, governed questionnaire content. This replaces manual forms and inconsistent data-entry practices with a controlled digital process.

Document tracking is handled through dedicated document-management capabilities such as Document Checklist Items, while Action Plans are primarily designed to orchestrate repeatable engagement tasks, owners, deadlines, and related process work. These features can complement Discovery Framework in a complete onboarding implementation, but they address different concerns.

For the problem stated—manual questionnaires, inefficient customer-data collection, and the need to comply with company policies—Discovery Framework directly addresses the primary onboarding deficiency.

The Mortgage Data Model connects the prospective borrower, financial position, and sales pipeline through Account, Assets and Liabilities, and Opportunity. These objects collectively provide the core CRM context required when Salesforce integrates with external loan-origination and onboarding platforms.

The Account represents the borrower or customer relationship and provides the customer context against which mortgage activity is tracked. Assets and Liabilities capture the applicant ' s financial position, including assets, debts, and other obligations, which is critical during mortgage qualification and underwriting. Opportunity represents the commercial pipeline component. Financial Services uses standard Leads and Opportunities to represent prospects and opportunities to provide customers with financial products.

Using Opportunity allows mortgage activity to participate in normal pipeline tracking, stages, reporting, and forecasting while the dedicated mortgage objects maintain detailed application information. Financial Account represents an established financial product relationship rather than the primary pre-origination pipeline object. Case is intended for service and support management.

Consequently, Account, Assets and Liabilities, and Opportunity provide the appropriate surrounding objects for integrating mortgage origination and onboarding while accurately tracking prospective business through the pipeline.

Salesforce provides a layered integration architecture in which MuleSoft, OmniStudio Integration Procedures, and OmniStudio DataRaptors or Data Mappers can work together to connect Agentforce Financial Services with external core systems.

MuleSoft Anypoint Platform provides enterprise integration capabilities for connecting Salesforce with banking platforms, transactional systems, APIs, and other back-end applications. Financial Services integration guidance specifically references MuleSoft for bringing external financial-account and transaction information into Salesforce.

Integration Procedures are server-side OmniStudio processes designed to retrieve, transform, orchestrate, and save data without requiring direct user interaction. They can invoke HTTP endpoints, coordinate multiple actions in one server call, and connect OmniScripts or FlexCards to internal and external sources.

DataRaptors, now referred to as OmniStudio Data Mappers, provide declarative extraction, transformation, and persistence of Salesforce data. They commonly operate inside Integration Procedures and handle data mappings between Salesforce records and the JSON structures required by OmniStudio components.

Data Processing Engine is primarily intended for high-volume transformation and calculation workloads. Data Consumption Framework provides an external-data consumption architecture, but the integration-development capabilities specifically represented here are MuleSoft, Integration Procedures, and DataRaptors or Data Mappers.

A Financial Services household can have only one Primary Member. Both Oliver and Macie have Primary Member enabled, which violates this household-modeling rule and causes the configuration error.

Salesforce household guidance states that designating a primary member is optional, but a household can have only one primary member. The primary member commonly represents the principal client or primary relationship within the household. Other members receive roles that describe their relationship to that primary member, such as Spouse or Dependent.

The other settings shown are valid. Multiple members can designate the same household as their Primary Group. Primary Group identifies the household to which a person ' s qualifying records and activities should roll up. A spouse can be a valid relationship role, and multiple household members can have their eligible activities and financial information summarized to the same primary household.

The advisor should therefore retain one individual—typically the principal client—as Primary Member and clear Primary Member for the spouse while leaving the appropriate relationship and Primary Group settings in place.

The consultant should use the packaged Insurance Flow Templates and associated guided insurance service processes rather than creating a custom user interface from scratch. Salesforce ' s insurance capabilities provide prebuilt guided processes that standardize common policy-servicing activities and reduce the amount of manual navigation and data entry required by service representatives.

Current Agentforce Financial Services documentation continues this architecture through prebuilt insurance service-process templates. These templates provide ready-made process attributes, intake forms, and fulfillment flows and are intended to accelerate insurance service delivery across assisted and self-service channels.

Premium-payment servicing is a concrete example. Salesforce supplies guided processes in which an agent selects the active policy, reviews the current premium due date and frequency, selects the new payment frequency and effective date, and submits the change through an OmniScript. Insurance policy processes similarly use OmniScripts to guide users through payment-plan information and payment-frequency selection.

This packaged approach is preferable to custom Lightning web components because it reduces development and maintenance while enforcing consistent data capture. An Action Plan manages tasks and deadlines but does not replace a guided data-entry process for updating beneficiary or premium-payment information.

Organization-Wide Defaults establish the baseline record visibility for users who otherwise have the required object-level permissions. To make Person Account records broadly visible, the Account or Person Account sharing model should provide Public Read Only access. Public Read Only allows all applicable users to view and report on records while reserving editing rights for users who receive additional access.

Financial Accounts contain sensitive financial information, so their baseline sharing should instead be Private. With Private sharing, users do not automatically gain access merely because they can access the Financial Account object. Access can subsequently be expanded only to authorized users through record ownership, role hierarchy where appropriate, sharing rules, manual sharing, Compliant Data Sharing, or another approved mechanism.

Setting Financial Accounts to Public Read Only would expose them broadly and directly contradict the stated privacy requirement. Likewise, removing a Financial Accounts tab or component from a Lightning page is not a security mechanism. A user who retains record access could still potentially retrieve the information through reports, search, APIs, related lists, or another Salesforce interface.

Therefore, the appropriate record-level model is Public Read Only for Person Accounts and Private for Financial Accounts, followed by selective access grants for authorized Financial Account users.

Insurance Policy Administration manages operational activities associated with an insurance policy after the policy has been established, including changes during its lifecycle, payment schedules, and commission-related processing.

Salesforce identifies endorsements as a core policy transaction. An endorsement represents a mid-term change to an existing policy and can produce a corresponding premium adjustment. Policy Administration maintains policy versions and the resulting transaction history so the insurer can preserve both the previous and updated policy state.

Policy Administration also includes Policy Payment Schedules, which define the agreed payment plan between the insurer and policyholder and cover premiums, taxes, fees, and scheduled payment entries. Salesforce ' s Policy Administration documentation additionally provides dedicated functionality to track commissions, making commissions part of the supported policy-management lifecycle.

Approvals and underwriting occur primarily in other portions of the insurance lifecycle. Underwriting evaluates risk and determines whether and under what conditions insurance should be offered, while approval mechanisms can participate in broader workflows. They are not the three policy-administration processes identified here.

Therefore, the processes aligned with Policy Administration are Endorsements, Payments, and Commissions, covering policy modification, financial servicing, and producer or intermediary compensation after policy issuance.

Salesforce applies platform limits to the number of sharing rules configured for an object. The standard allocation is 300 total sharing rules per object, including owner-based and criteria-based rules. This limitation matters when designing a franchise architecture because creating separate sharing rules for every franchise, region, or user population can result in an unnecessarily complex sharing model and eventually approach platform limits.

Architects should prefer scalable mechanisms such as roles, public groups, role-and-subordinate relationships, sharing sets or appropriate Experience Cloud sharing constructs, and criteria-driven sharing where those mechanisms meet the security requirements.

The default total sharing-rule limit can in some circumstances be increased through Salesforce Support, but the standard architectural limit tested here is 300 rules per object.

A user occupies one role in Salesforce ' s role hierarchy, not multiple simultaneous roles. Browser selection is unrelated to the fundamental role-and-sharing architecture. Public groups are supported as reusable sharing targets, but the stated 1,024 limit is not the relevant restriction identified in this scenario.

Therefore, the architect must account for the per-object sharing-rule allocation when designing a large franchise access model and should avoid a design that depends on a separate rule for every franchise unless absolutely necessary.

Agentforce Financial Services provides participant-based sharing for Financial Deals. To give a particular user or group access to a Financial Deal record, the deal owner or authorized user should add that user or group as a participant through the Financial Deal Participants related list.

From a Financial Deal record, the user creates a new Financial Deal Participant, selects the required user or group, assigns a Participant Role, marks the participant active, and saves the record. Compliant Data Sharing must be enabled for the Financial Deal object for this sharing mechanism to operate.

Salesforce also offers the Manage Participants component, which can add multiple users or groups and assign roles directly from the Financial Deal record. Both approaches use the same participant-based Financial Services sharing architecture.

Changing OWD to Public Read/Write would fundamentally undermine the confidentiality model because every qualifying user would receive broad access rather than only the intended deal team. A permission set can grant object-level capability, but object permission alone does not grant access to a particular restricted Financial Deal record. Industries Settings likewise is not the record-sharing mechanism.

Therefore, adding the group as an active Financial Deal Participant is the required record-level access configuration.