Salesforce AP-208 Dumps

Mortgage functionality in Agentforce Financial Services is controlled through the appropriate permission-set and user-access configuration. A user who must create or work with Residential Loan Application records needs access to the mortgage feature and to the mortgage-related objects. Consequently, failure to assign the required Mortgage permissions prevents the consultant from creating the application record.

Salesforce ' s Financial Services setup guidance includes assigning the Mortgage permission set as part of granting users access to mortgage functionality. Salesforce also provides enhanced mortgage permission-set configurations for personas such as loan officers and underwriters.

Current configuration guidance shows that mortgage-oriented permission sets must grant the system permission that licenses the user to access mortgage functionality in Financial Services and must provide the necessary object permissions for Residential Loan Applications and related Loan Applicant and Loan Application objects.

The issue is therefore not resolved by enabling a Residential Loan Application flow or by selecting a user-level Mortgage User checkbox. Nor is there a general Allow Mortgage Access setup switch corresponding to the required user entitlement. Access is established through the prescribed mortgage permissions and associated object-level access.

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.

A transformation from the individual account model to Person Accounts is a significant data-model change and must be approached with strong data-protection controls. The implementation team should therefore prioritize a complete data backup before changing or converting existing customer records.

Salesforce ' s conversion guidance includes performing a backup as a core prerequisite in the transformation sequence. The process ultimately changes individual Account and Contact records into Person Account records, and Salesforce emphasizes that the transformation must first be tested carefully because the Person Account model cannot simply be disabled after it has been enabled.

Salesforce also recommends creating a sandbox to assess how Person Accounts affect the organization ' s technical architecture, integrations, automation, components, reports, and customizations. However, from a migration-risk perspective, preservation of the existing production data is fundamental before irreversible data transformation activities are performed.

Subsequent implementation activities include enabling Person Accounts, enabling them for Agentforce Financial Services, configuring record types through the Individual Record Type Mapper, validating source records, and executing the conversion. These activities depend on careful preparation. A reliable backup provides the implementation team with an authoritative pre-migration data state and should therefore be treated as a top planning priority.

Current Agentforce Financial Services identity-verification architecture relies on Flows or Screen Flows and OmniStudio to guide service representatives through caller verification and integrate with verification services.

Salesforce provides identity-verification flow templates for call-center scenarios. A Verify Customer Identity flow can be added to an Engagement Interaction Lightning record page so an agent can launch a structured verification process while handling the customer ' s interaction. Salesforce also supplies Flow Screen Components for customer search and identity verification, enabling administrators to build Screen Flows tailored to the organization ' s verification requirements.

OmniStudio provides the complementary guided experience and integration architecture used throughout Agentforce Financial Services. External identity-verification requests can be initiated from a Flow or from an Integration Procedure inside an OmniScript, enabling secure orchestration with third-party identity-verification and AML providers.

Process Builder is not the appropriate current architecture for new process automation; Salesforce ' s modern implementation model centers on Flow. Discovery Framework focuses on assessments, questionnaires, and onboarding data collection rather than being the principal call-center identity-verification user experience.

Accordingly, Screen Flows and OmniStudio provide the guided interaction and integration capabilities required to build a modern identity-verification process.

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.

Action Plans can calculate task due dates while excluding configured nonworking days. Salesforce requires administrators to define working and nonworking time in the organization ' s default Business Hours record. To designate a day as nonworking, the administrator leaves that day ' s start and end time fields blank. This is the method used to identify a nonworking day for Action Plan date calculations.

Companywide holidays are configured separately under Setup, Holidays. Importantly, recurring holidays are not treated the same way for Action Plan nonwork-day calculations, so administrators must configure applicable holidays in the supported form rather than assuming recurring-holiday settings will automatically be skipped.

After business hours and holidays are configured, Action Plans can use Skip Nonwork Days when calculating task completion-date offsets. This ensures that tasks with relative due dates do not fall on organizational nonworking days where the feature is configured accordingly.

No automatic configuration occurs merely because Action Plans are enabled. The administrator must establish the working calendar correctly. Therefore, leaving start and end times blank for a nonworking day is the required business-hours configuration.

Discovery Framework is Salesforce’s questionnaire-driven data collection capability for Agentforce Financial Services. It is designed for processes such as customer onboarding, financial-needs analysis, eligibility assessments, and other structured information-gathering scenarios. Administrators can create both independent assessment questions and hierarchical parent-child questions. A related question can be associated with a parent question, enabling dependent question structures appropriate for conditional assessments. Salesforce currently supports a defined hierarchy level for these related assessment questions.

Question lifecycle management is also built into the framework. Assessment questions support versions, and when a new version replaces an active version, the previous version can transition to Archived status. This provides controlled change management and supports auditability of questionnaire content.

Discovery Framework uses OmniStudio, rather than Salesforce Flow as its foundational form technology. OmniStudio enables sophisticated forms incorporating branching, rendering rules, data integration, and conditional logic. Forms can also be activated and deployed through supported Salesforce experiences, including Experience Cloud scenarios, so option E is incorrect. Salesforce specifically describes Discovery Framework as combining its assessment-question data model with OmniStudio to support complex digital forms.

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 Send Documents flow for Retail Banking is the appropriate standard capability because the business problem centers on sending customer documentation through a controlled Financial Services process while giving service representatives a consistent Salesforce-based experience.

Salesforce provides several preassembled flows for common Retail Banking and Insurance service requests through the Financial Services flow package. These flows are delivered as standard templates that organizations can clone and customize to match their service processes.

The Send Documents flow includes a predefined list of commonly used documents. Administrators can extend that list directly by modifying the Correspondence Selection screen and adding document choices. This means the institution can tailor the standard flow to its required banking documents while keeping service execution within the Agentforce Financial Services environment.

A Marketing Cloud integration would primarily address communication campaigns rather than the underlying retail-banking service process. Process Builder is not the appropriate architecture for this guided document workflow, and custom Apex introduces unnecessary code when Salesforce already provides a configurable standard flow.

Using the Retail Banking flow centralizes the service process and reduces dependence on disconnected tools, giving agents a consistent workflow for handling customer-document requests and helping the organization standardize document-related interactions.

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.

Compliant Data Sharing supplements Salesforce ' s standard record-sharing architecture with participant-based access. Record owners can add participants and assign Participant Roles that determine whether those users receive read-only or read/write access. Salesforce also permits non-owner participants who have Edit access through CDS to manage participants, giving them sharing capabilities comparable to the record owner. Users above the owner can separately retain access through role hierarchy where hierarchy access applies.

Salesforce also imposes a lifecycle dependency between object enablement and Participant Roles. If Compliant Data Sharing must be disabled for a supported object, the participant roles associated with that object must first be removed.

CDS is not limited exclusively to Financial Services objects plus Account and Opportunity. Current Salesforce implementations support additional standard and custom objects and use CDS across multiple Salesforce industry solutions.

For Organization-Wide Defaults, supported objects can use Private or Public Read Only for CDS to provide meaningful incremental access. Public Read/Write makes CDS ineffective because all users already have record access. Therefore, the assertion that OWD must always be Private is too restrictive under the current implementation.

Salesforce ' s native Multiple Currencies functionality is designed for organizations that operate across countries while maintaining centralized corporate reporting. Once multiple currencies are enabled, the administrator defines a corporate currency, representing the currency used by corporate headquarters, and activates the additional currencies required by regional operations. Individual users can maintain personal currencies, while records can retain their applicable transaction currencies.

Salesforce reports preserve monetary amounts in their original currencies while allowing report totals and converted columns to be displayed in another active currency. This enables regional branches to operate using their local currencies while headquarters reviews consolidated amounts using the corporate reporting currency. The corporate currency serves as the reference currency for conversion rates.

Advanced Currency Management supplements this architecture by supporting dated exchange rates for opportunities, allowing historical transactions to use conversion rates appropriate to their effective periods rather than relying exclusively on a static rate.

A third-party application or spreadsheet-based conversion process introduces unnecessary complexity because Salesforce already provides the required international currency and reporting functionality. The appropriate design is therefore to enable native multi-currency capabilities, establish the corporate currency, configure active currencies and conversion rates, and use Advanced Currency Management where dated rates are required.

Record Alert Categories are optional, but Salesforce recommends them because they provide a structured mechanism for organizing alerts by priority, severity, type, or another business classification. For example, an administrator can define a High Priority category and associate relevant client alerts with that category so advisors can quickly distinguish urgent information from routine notifications.

A category can have a configured severity value. When an advisor selects that category while creating a Record Alert, the category ' s severity becomes the default, but the user can change that value. This makes the statement that the severity cannot be changed incorrect.

Record Alerts are available on all custom objects and on a defined list of supported standard objects rather than indiscriminately on every standard object. Financial Services also provides specialized alert experiences for person accounts, financial accounts, and financial account transactions through its Record Alerts framework.

The relevant configuration principle is therefore that categories improve organization and usability while remaining optional. Administrators can design a category structure that reflects the institution ' s servicing and risk priorities, but a Record Alert can still be created without assigning a category when the business process permits it.

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.

The broker organization should be represented by an Account, while each individual broker is represented as a Contact associated with that organization. This preserves the distinction between the business entity and the individual professionals who operate within it and allows each broker to receive individually controlled portal access.

The assistant should likewise be modeled as a Contact. Where an assistant works across multiple broker relationships, Salesforce ' s Contacts to Multiple Accounts architecture provides a scalable way to represent those associations without duplicating the Contact record. The model maintains one Contact as the authoritative individual record while using relationship records to connect that Contact to additional relevant Account relationships.

This structure is preferable to creating separate Account-and-Contact pairs for every individual broker because it would unnecessarily duplicate business entities and complicate relationship management. A Contact-to-Contact relationship can describe interpersonal relationships but does not provide the same account-based affiliation model required where one person participates across multiple broker organizations or account contexts.

Record access for portal users is handled separately through Experience Cloud sharing and security controls. Modeling brokers individually as Contacts does not require brokers to see one another ' s information. The sharing architecture can restrict users to their own records and specifically authorized relationships.

The Account-plus-Contact approach therefore best satisfies the required broker and assistant data model.

A formal field mapping should define how each source-system data element corresponds to its destination field in Salesforce. This is a fundamental integration-design control because it creates an explicit contract between the external data structure and the Salesforce object model. For each source attribute, the mapping identifies the appropriate destination object and field, transformation requirements, data type, lookup behavior, and any required validation.

Salesforce uses this same principle throughout its data-import and integration tooling. Field mappings define which input columns or external-system fields correspond to Salesforce fields, and administrators should review mappings before records are loaded. Data Loader batch processing similarly uses a field mapping file to map input-file columns to corresponding Salesforce object fields.

Using a CSV and Data Loader would describe one particular import mechanism rather than the integration design required by the scenario. A junction object is appropriate for modeling many-to-many relationships, not simply for ensuring incoming attributes reach the correct fields. Custom metadata can support configurable integration behavior, but it is not inherently required merely to define source-to-target field correspondence. A documented field mapping provides the precise source-to-target definition necessary for reliable external-system integration.

The custom reporting field belongs on the Contact-Contact Relationship object because Agentforce Financial Services uses that relationship object to represent relationships between two individuals represented as Person Accounts.

A Person Account combines Account and Contact characteristics, but person-to-person relationship modeling occurs at the Contact relationship layer. Salesforce ' s Groups and Households data model states that Contact Contact Relationship relates person accounts to each other. For an inverse relationship such as spouses, two Contact Contact Relationship records can be used to model both directions of the relationship.

Salesforce household examples use Person Accounts for the client, spouse, and child, while Contact Contact Relationship records model client-to-spouse, client-to-child, spouse-to-child, and their inverse relationships. The relationship ' s semantic meaning is further described through associated reciprocal or party-role relationship records.

Therefore, if the financial institution needs a custom attribute specifically about the relationship between two individuals—and subsequently needs that value for reporting—the field should reside on the relationship record itself rather than on either Person Account.

Account Contact Relationship is used primarily for person-to-business or person-to-group membership relationships. Account Account Relationship connects business accounts. Neither accurately represents a direct relationship between two Person Accounts. The appropriate object for relationship-specific reporting data is therefore Contact-Contact Relationship.

The appropriate Financial Services access level for Personal Banker users is the Financial Services Cloud Standard entitlement represented by option A.

Salesforce ' s Personal Banker configuration guidance instructs administrators to create the user with the Personal Banker profile and then assign the Financial Services Cloud Standard and Personal Banker Access permission sets. This combination supplies the Financial Services capabilities required by the retail-banking persona together with the persona-specific permissions required for personal-banking functionality.

The broader Agentforce Financial Services user-creation guidance follows the same access pattern. Personal Banker, Advisor, and Relationship Manager personas use Financial Services Cloud Standard together with their persona-specific permission sets.

Salesforce distinguishes between permission sets and permission set licenses. A permission set license extends the underlying Salesforce user license so that features covered by the purchased Financial Services product can be used, while permission sets grant the associated permissions. Users therefore need the applicable license entitlement as well as required permission assignments.

For the Personal Banker group described in the question, the Standard Financial Services entitlement is the appropriate baseline rather than the Basic, Foundations, or Extension alternatives.

Salesforce imposes specific data-integrity requirements before individual-model Account and Contact records can be converted into Person Accounts. First, every individual account being transformed must have only one direct Account Contact Relationship and one associated Contact. This is necessary because the resulting Person Account combines the Account and individual Contact information into a single person-oriented record.

The account must also not be the parent of another Account. Salesforce requires the Account ' s Parent Account field to be blank and explicitly states that an account being converted cannot be the parent account of any other Account records.

The conversion should also be tested comprehensively in a sandbox. Salesforce describes the conversion as irreversible and instructs organizations to create a sandbox first so they can evaluate the effects of Person Accounts on technical architecture, integrations, automation, and customizations.

Additional documented requirements include matching Account and Contact owners, matching currency values where applicable, ensuring that the Contact ' s Reports To field is blank, and ensuring that no other contacts report to that Contact. There is no requirement for the Account Phone field to be blank, nor does Salesforce require linked Opportunities to be reassigned to the Account owner as a conversion prerequisite. Therefore, A, B, and E are the mandatory preparations represented in the answer choices.

Financial Services data migration must respect object dependencies and relationship references. Salesforce recommends loading customer identities before relationship groups and then loading financial-account information only after the required customer and household structures exist.

The sequence starts with Accounts and Contacts because these records represent the customers or individuals to whom subsequent Financial Services records will relate. Household or relationship-group records are then created so those individuals can be organized into the appropriate household structure. Financial Accounts follow after these foundational customer and group records exist.

The reason is referential integrity. Household records depend on identifiable customers and their relationship structures. Financial Accounts, in turn, must connect to owners and other participants through Financial Account relationships and therefore require existing customer records.

The broader migration sequence can continue after Financial Accounts with Financial Account Roles, transactions, cards, holdings, statements, and other dependent records. Loading child or transactional data before the referenced parent records would create lookup failures or incomplete relationships.

Therefore, among the supplied choices, the correct high-level migration order is Accounts and Contacts, then Households, then Financial Accounts.

The correct design uses Salesforce ' s Organization-Wide Defaults to establish different baseline visibility for customer records and sensitive financial records.

Person Accounts should have Public Read Only visibility so that users who have the required object-level permissions can view customer records throughout the organization. Public Read Only allows records to be viewed broadly while preventing unrestricted modification.

Financial Accounts contain sensitive information such as deposit accounts, investment accounts, loans, mortgages, credit cards, and other financial relationships. Their OWD should therefore 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, teams, manual sharing, Compliant Data Sharing, or other approved mechanisms.

Setting Financial Accounts to Public Read Only would expose them broadly and directly contradict the 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 retrieve the information through reports, search, APIs, related lists, or another Salesforce interface.

Therefore, Public Read Only for Person Accounts and Private for Financial Accounts provides the appropriate least-privilege foundation.

Agentforce Financial Services supports Person Account-based household modeling. Individual household members can be represented as Person Accounts, while the household itself is represented through the household or group Account structure. This provides a single individual record for each member while preserving group-level aggregation and relationship management.

Both Opportunity and Financial Deal participate in the Financial Services compliant-sharing architecture. Compliant Data Sharing enables explicitly authorized participants to receive controlled access to supported records rather than relying only on broad organizational sharing mechanisms. Financial Deal also provides a critical additional security control: administrators can disable Role Hierarchy-Based Sharing for Financial Deals. Doing so prevents managers from automatically receiving access to their subordinates ' confidential deals.

Standard Opportunity hierarchy access cannot be disabled through the comparable object-level hierarchy setting, which makes the distinction in option E important.

Interaction Summary is not a wholesale replacement for Salesforce Activity. It is a specialized Financial Services structure for recording detailed client-interaction notes, participants, confidentiality information, and compliant sharing. Activities remain appropriate for tasks, calls, meetings, and other standard activity-management scenarios.

Therefore, A, D, and E correctly describe the Financial Services object and sharing behavior that consultants must consider during implementation delivery.

The required architecture combines Document Generation with a DataRaptor, now called an OmniStudio Data Mapper in current Salesforce terminology.

Document Generation merges Salesforce or OmniStudio data into predefined document templates and can produce documents that are subsequently converted to PDF. It is designed for outputs such as forms, contracts, proposals, reports, and customer correspondence where variable information must be populated dynamically.

The DataRaptor or Data Mapper supplies the data used to populate the template. An Extract retrieves fields from Salesforce, while mapping capabilities connect those extracted values to document tokens. Salesforce document-generation architecture supports automatic resolution of template token data from configured mappings such as DataRaptor Extracts.

In this scenario, the customer ' s newly entered address must populate predetermined address placeholders in the generated document. Document Generation produces the document, while the DataRaptor or Data Mapper provides and maps the Salesforce data.

Calculation Procedures perform calculations, and Integration Procedures orchestrate integrations. Neither replaces the dedicated document-generation and data-mapping capabilities required to create the prefilled PDF.

Agentforce Financial Services models referrals through the Lead object, so a requirement for another referral variation should be implemented by creating an additional Lead record type rather than introducing a separate custom Referral object.

The administrator creates a new Lead record type using Referral as the basis, assigns an appropriate Lead Process, activates the record type, and makes it available to the required users. This allows the organization to define different required fields, page layouts, or referral experiences for the new type while remaining within the standard Financial Services referral architecture.

The administrator must then configure Referral Record Type Mapper custom metadata. The mapper connects the new Lead record type to Financial Services referral functionality by identifying the referral record type and enabling the packaged referral components to recognize it.

Assigning the record type to the relevant users is essential because users must have access to the new record type before they can select it during Lead or Referral creation. Updating a page layout may subsequently be useful, but it is not one of the three core configuration steps identified by the referral record-type procedure.

The correct implementation therefore uses the existing Lead and referral architecture: create the Lead record type, assign it to users, and create the corresponding Referral Record Type Mapper record.

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.

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.

Delegated Administration allows selected business users to perform a controlled subset of administrative functions without receiving unrestricted System Administrator authority. The capability is therefore suitable for franchise administration where local administrators need to support their users but must remain constrained to a defined administrative scope.

Delegated administrators can administer users within the roles and subordinate roles specified in their delegated group. Appropriately configured delegated administrators can perform user-management operations, including unlocking users, when the necessary permissions are granted.

Delegated administration also supports management of designated public groups. A delegated administrator can create or maintain membership for public groups made available within the delegated-administration configuration, allowing franchise administrators to manage group membership without receiving organization-wide administration rights.

Salesforce additionally allows delegated administrators to assign or remove permitted permission sets for users within the delegated group. The assignable permission sets must be explicitly included in the delegated group ' s configuration.

Changing organization-wide sharing defaults is an organization-level security architecture function and is not an appropriate delegated administrative capability. OWD changes could alter record access across the entire organization and therefore remain under higher-level administrative control.

Interest Tags are specifically designed to capture customer interests, needs, preferences, and prospecting opportunities in Agentforce Financial Services. They are therefore the appropriate capability for storing information such as a client ' s hobbies.

Salesforce gives hobbies such as golf and skiing as examples of information that can be represented using Interest Tags on person accounts. Interest Tags can also represent investment interests and other topics discovered during customer interactions.

Interest Tags can be organized into hierarchical Tag Categories, enabling institutions to establish a controlled taxonomy. For example, an organization could create a Hobbies category and define tags such as Golf, Skiing, Sailing, or Travel. Because this vocabulary is structured, organizations can report across clients and identify common themes or potential engagement opportunities.

Topics provide the underlying platform capability and are a prerequisite for Interest Tags, but Topics alone are not the Financial Services feature designed for this client-interest requirement. Alerts communicate conditions requiring attention rather than persistent customer interests. Interest Tags therefore provide the Financial Services-specific functionality required for tracking hobbies and supporting personalized client engagement.

In the Individual Account model, Agentforce Financial Services uses purpose-built custom objects to represent important aspects of a customer ' s financial profile, including identification information, assets and liabilities, financial goals, and revenue. These records are related to the customer ' s Account, which is the central customer entity in the Individual Account architecture.

Salesforce ' s Financial Services data model states that custom objects are used to represent other assets, liabilities, goals, and revenue and that, in the Individual Account model, these objects relate to the Account object. This enables financial institutions to maintain structured, reportable financial data rather than storing those details in generic attachments or notes.

This distinction is important because the Individual Account model differs from the Person Account model. In a Person Account deployment, the underlying Account and Contact architecture is presented as a unified individual record. In the Individual Account model, the financial-information objects remain explicitly associated with the Account representing the customer.

Identification records similarly belong to the Financial Services structured data model rather than being treated merely as Salesforce Files or Attachments. Using dedicated objects allows organizations to manage document types, identifiers, financial values, goals, and revenue information with appropriate relationships, permissions, reporting, and automation.

Therefore, the correct modeling approach is custom Financial Services objects related to the Account.

Financial Account Management provides the Agentforce Financial Services data model and user experience used to represent and manage customers ' financial-product relationships. A Financial Account can represent a checking or savings account, investment account, credit card, mortgage, loan, or another financial product. Related objects can represent account parties, balances, addresses, transactions, and associated information.

Salesforce ' s Financial Services architecture provides Financial Account and associated objects specifically to model financial accounts and their related information. Administrators provide appropriate permissions to advisors, personal bankers, integration users, or other personas that require access.

Financial Services also provides Financial Account Summary experiences on the customer ' s Account page. Advisors can use them to view financial account details and related information in the context of the client relationship. This creates the consolidated account-level visibility financial advisors need for servicing and relationship management.

Performance reporting analyzes business results but is not the underlying client-account management capability. Client onboarding handles customer acquisition and setup processes. Opportunity management addresses potential sales or revenue-generating activities rather than established client financial products.

Therefore, Financial Account Management is the feature directly responsible for representing, tracking, and servicing customers ' financial accounts.

Agentforce Financial Services uses Individual Record Type Mapper custom metadata to map custom individual record types to the appropriate Account and Contact record-type architecture. This allows an organization to differentiate individual personas such as customers and independent advisors while preserving Financial Services behavior that depends on correctly identifying those records as individuals.

The administrator first creates and enables the required Person Account record types. The administrator then opens the Individual Record Type Mapper custom metadata and creates or updates the appropriate mapping records, specifying the record type used for each individual classification.

This metadata is important because Agentforce Financial Services components and processes need to know which Account record types represent individuals. Additional mapping records can be created when an organization has multiple person-oriented business roles that require different page layouts, processes, or referral behavior.

Creating custom fields does not establish record-type semantics. A Contact record type alone is insufficient because Person Accounts are represented through the Account architecture with associated Contact behavior. Likewise, a generic custom setting is not the mechanism used to distinguish the two requested Person Account types.

The correct configuration is therefore to create the necessary Person Account record types and define their corresponding Individual Record Type Mapper metadata.

For an Unlimited Edition production organization, Salesforce supports weekly Data Export and allows an administrator to schedule recurring exports. Therefore, after validating the backup process manually, establishing a weekly scheduled export provides a consistent migration-preparation dataset without requiring repeated manual execution.

Salesforce supports weekly exports for Enterprise, Performance, and Unlimited Editions. Administrators can use Setup, Data Export, and Schedule Export to configure recurring backup generation. A manual weekly export can generally be generated once every seven days, so a daily full Data Export sequence does not align with the platform ' s export interval.

A scheduled backup is especially valuable before migration because successive exports allow the administrator to review changes, perform data profiling, confirm migration mappings, and maintain a recoverable source-data baseline. Salesforce recommends recurring Schedule Export functionality when maintaining backups.

Testing a production Data Export by sending a request from a sandbox to another Salesforce org is not how the native backup mechanism operates. Scheduled Data Export is a production capability rather than a sandbox-based migration test. The data should remain controlled by appropriately authorized administrators rather than being handed directly to a business manager without established migration governance.

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.