Salesforce AP-208 Practice Test Questions Answers

Salesforce provides three primary sets of preassembled Financial Services flows: Mortgage, Retail Banking, and Insurance. These templates accelerate implementation by supplying guided business processes that consultants can clone and adapt rather than constructing every user journey from the beginning.

Financial Services includes different sets of preassembled flows tailored to specific business requirements: mortgage flows, insurance flows, and retail banking flows. Mortgage flows are supplied with Financial Services Cloud, while insurance and retail banking flows are provided through the Lightning Flow for Financial Services package. The installed flows are delivered as standard flow templates and can be cloned and customized according to organizational processes.

Mortgage templates support activities associated with collecting borrower information and assets and liabilities. Retail banking and insurance packages similarly include predefined service-request flows.

Commercial Banking and Institutional Banking have dedicated Financial Services capabilities, but they are not the three categories of preassembled flow sets described by this package architecture. Therefore, the correct selections are Mortgage, Retail Banking, and Insurance.

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.