AP-208 Practice Exam Questions

The bank should replace spreadsheet-driven processing with Salesforce ' s standard mortgage flow templates and use Flow Builder to customize the mortgage journey according to the bank ' s requirements.

Salesforce installs mortgage flows as standard Flow templates. Administrators can create a new Flow based on a standard mortgage template, customize its screens and processing logic in Flow Builder, save the resulting implementation, and activate it for users. Mortgage templates support borrower information, assets and liabilities, and related mortgage processes.

This approach moves data capture into a controlled Salesforce process rather than repeatedly importing spreadsheets. Guided flows can collect borrower information consistently, enforce required fields, perform validation, invoke automation, and write information directly to the supported mortgage data model.

Creating a new custom Mortgage Application object is unnecessary because Agentforce Financial Services already provides dedicated mortgage application capabilities and associated data structures. Building duplicate custom objects would increase maintenance and complicate integration with standard Financial Services functionality. Similarly, Data Import Wizard merely transfers existing spreadsheet information into Salesforce and would leave the underlying manual collection process largely unchanged.

Combining standard mortgage templates with Flow Builder gives the organization a reusable, maintainable, and declarative solution that improves efficiency while retaining flexibility to customize the mortgage process.

Agentforce Financial Services extends the standard Salesforce Lead object with record types appropriate to financial-services acquisition and referral processes. The relevant Lead record types are General, Referral, and Retirement Planning.

The General record type supports ordinary prospect-management scenarios. Salesforce ' s Financial Services configuration documentation identifies General as an available Lead record type and provides a corresponding Lead page-layout assignment. Retirement Planning is a business-to-consumer Lead record type intended for retirement-focused prospect scenarios.

The Referral record type is particularly important in Financial Services. Salesforce uses it to allow users to create and route referrals based on an expressed customer interest. Administrators can also create additional referral record types by deriving a custom Lead record type from Referral and configuring the corresponding Referral Record Type Mapper custom metadata.

Salesforce ' s Financial Services data model identifies the Lead record types as General, Referral, and Retirement Planning.

Opportunity is a separate Salesforce object and therefore is not a Lead record type. Adjustments likewise is not one of the standard Financial Services Lead record types applicable to this configuration.

Record Alerts are designed to surface actionable notifications directly in the context of client and financial records. They can represent information maintained in Salesforce or supplied by external banking systems and can be displayed through OmniStudio-based components. Consequently, the access model spans both Agentforce Financial Services permissions and OmniStudio runtime capabilities.

The Financial Services Cloud Foundations permission set supplies access to common Financial Services capabilities and the underlying objects required by features such as Record Alerts. The Financial Services Cloud Standard permission model provides access to standard Financial Services functionality and components used by licensed Financial Services users. The OmniStudio User permission set extends runtime access to the OmniStudio capabilities used by Financial Services implementations, including the components through which alerts can be surfaced.

Salesforce separates ordinary feature consumption from administrative design responsibilities. OmniStudio administrative permissions are associated with configuration and management of artifacts such as FlexCards and Integration Procedures rather than representing the ordinary Financial Services end-user permission layer tested by this question. Record Alerts themselves support alert severity, categories, snoozing, dismissal, external-system data, and hierarchical presentation of related alerts.