Free Practice Questions for Salesforce AP-208 Exam

An Integration Procedure is the preferred solution because the FlexCard must combine data from Salesforce and an external REST API. OmniStudio Integration Procedures are server-side, declarative processes capable of reading Salesforce data, making external REST calls, transforming results, and returning a consolidated response to a FlexCard.

A typical architecture is for an Integration Procedure to use a Data Mapper to retrieve a relevant Account value, such as a ZIP code, and then make a REST call to an external weather service for the current or historical conditions associated with that location.

Salesforce recommends Integration Procedures as FlexCard data sources when several actions or data sources must be combined because multiple operations can execute in a single server call. This improves flexibility, performance, and maintainability compared with moving orchestration logic to the client.

A DataRaptor or Data Mapper Extract alone is appropriate for Salesforce data but does not by itself orchestrate the Salesforce extraction with the external weather service. Custom Apex could perform the work but introduces unnecessary code where OmniStudio provides the required declarative capability. Streaming API addresses event or data streaming rather than this synchronous aggregation requirement.

Custom Field Sets provide a declarative way to tailor the Financial Services interface for different user populations without changing the underlying data model. This is particularly valuable where wealth managers and investment bankers require different information to perform their jobs efficiently.

The Financial Summary component supports field-set-driven configuration. Administrators can define a field set that determines which summary information is presented and configure the Financial Summary component from Lightning App Builder.

Salesforce also provides Financial Services setup procedures for creating custom Account and Financial Account field sets for user-facing Financials experiences. Administrators choose the specific fields that should appear, allowing the presentation layer to be tailored to the operational needs of a persona.

A consultant can therefore create a Wealth Manager-specific field set, associate it with the appropriate Financial Summary or configurable Lightning component, and use persona-specific Lightning-page configuration so that wealth managers receive the information most relevant to their work without forcing the same presentation on investment-banking users.

Creating another Person Account type does not solve a user-interface customization requirement and incorrectly changes the customer data model. The appropriate solution is to use field sets and component configuration to deliver persona-specific experiences while retaining a common underlying financial data model.

Rollup By Lookup aggregates Financial Services data into higher-level summaries. A typical use case is calculating financial-account measures such as account balances and presenting those totals at the individual client or household or group level.

When a Financial Account or Primary Group membership changes, the RBL configuration updates the corresponding client-level and group-level summaries. This allows advisors and bankers to view aggregated financial information without manually totaling every related record.

Salesforce provides packaged RBL configurations for multiple Financial Services objects, including Assets and Liabilities, Claims, Financial Accounts, Financial Account Roles, Insurance Policies, and Revenues. Household RBL rules use household lookups, while client-level financial-account rules use owner-related lookup fields.

Salesforce also warns that creation or customization of the managed-package Financial Services RBL rules is not recommended or supported. This makes statement D correct.

Person Accounts are not an absolute prerequisite for the RBL framework, so statement B is incorrect. RBL also performs aggregate calculations and can create meaningful processing overhead, particularly during high-volume data loads, so statement E is inaccurate.

Therefore, the technically correct statements are that RBL displays summary calculations, updates corresponding client and group summaries, and should not be custom-created or modified outside supported guidance.