AP-208 Salesforce Accredited Agentforce Financial Services Professional Questions and Answers

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.

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.

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 appropriate configuration point is the Role field on the Financial Account Role object. Financial Account Role represents the relationship between a financial account and a person, contact, or account. Examples include primary owner, joint owner, beneficiary, trustee, or another organization-specific participation role.

Salesforce ' s Financial Services data model represents these relationships through the Financial Account Role structure. Current standard data-model mapping carries the same concept into Financial Account Party, where the managed-package Role field maps directly to the standard Role picklist. This confirms that role classification belongs on the relationship record rather than on the Financial Account itself.

A Joint Owner or Primary Owner relationship should therefore not be modeled by creating new values or fields directly on Financial Account. The relationship object is specifically designed to support multiple parties and multiple relationship types for the same financial account. Account-Account Relationship addresses relationships between accounts or business entities and is unrelated to financial-account ownership or participation.

Accordingly, when additional customer-to-financial-account relationship categories are required, administrators should extend the Role picklist on Financial Account Role. This preserves the Financial Services relationship model and supports consistent ownership, reporting, rollups, and financial-account relationship processing.

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.

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.

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.

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.

Interaction Summary is designed specifically for structured client and partner meeting documentation in Agentforce Financial Services. It enables bankers and advisors to record detailed meeting information, capture attendees, specify confidentiality, document next steps, and selectively share sensitive notes with the appropriate stakeholders.

Salesforce describes Interaction Summaries as providing structured note-taking together with compliant, role-based data sharing. Users can create an interaction summary associated with an interaction, while the Interaction Attendees capability allows attendees to be viewed and managed.

When creating an Interaction Summary, bankers and financial advisors can take detailed meeting notes, define the confidentiality level, add action items or next steps, and ensure that notes containing confidential information are shared only with relevant stakeholders. The underlying data model includes Interaction for the meeting itself, Interaction Attendee for participating people, Interaction Summary for the notes and confidentiality information, and Interaction Summary Participant for sharing.

A normal Event is primarily a calendar or activity construct, while standard Notes do not provide the complete Financial Services interaction and compliant-sharing model. Interaction Summary therefore directly aligns with every element of the requirement.

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.

Interaction Summaries are specifically designed to capture structured client or partner interaction information while supporting controlled sharing of sensitive content. Salesforce describes Interaction Summaries as providing structured note-taking together with compliant, role-based data sharing, making them appropriate when a financial institution needs to limit visibility of interaction information according to business or regulatory requirements.

Interaction Summaries can contain detailed meeting notes, confidentiality settings, participants, purposes, next steps, and related records such as opportunities or financial deals. This permits institutions to retain useful customer-engagement information without automatically exposing confidential notes to every user who can access the broader customer record.

Option A misapplies Action Plans. Action Plans manage standardized tasks and sequences; they are not the primary mechanism for capturing confidential meeting notes. Option C describes a requirement better suited to features that capture interests, needs, or engagement topics rather than Interaction Summaries. Option D similarly combines life-event tracking with task management in a way that does not reflect the primary purpose of Action Plans. The correct design principle is to map each business requirement to the capability expressly designed for that data and security model, rather than forcing all customer-engagement processes into a single component.

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.

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.

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.

For a retail-banking transformation, cross-line-of-business collaboration and modernized relationship management are direct strategic outcomes of Agentforce Financial Services. Salesforce positions its banking platform around unified customer information, referrals across lines of business, personalized engagement, and deeper customer relationships.

Referral capabilities allow teams to identify a customer ' s financial need and route the opportunity to the appropriate specialist elsewhere in the institution. This breaks down organizational silos and enables the bank to deepen relationships and increase wallet share. Agentforce Financial Services also modernizes banker and advisor engagement by bringing customer relationships, financial information, interactions, goals, and opportunities into a unified operating environment. This enables more personalized and trusted long-term engagement.

The policyholder and underwriting option is insurance-specific and does not fit the banking scenario. Client onboarding is a supported Financial Services capability and can be a valid ROI outcome,

The verified outcomes represented in the available question content are therefore improved collaboration through leads and referrals and modernization of client-advisor relationship management.

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.

Interest Tags enable Financial Services users to categorize customer interests and associate those interests with supported records, including Interaction Summaries. Access is controlled through specific Financial Services permissions rather than being universally included in every Financial Services permission set.

Salesforce identifies Financial Services Cloud Extension and Financial Services Cloud Foundations as permission sets that provide the relevant Interest Tags capabilities. Current Salesforce documentation lists these permission sets among those used in Financial Services for access to Interest Tags functionality.

Salesforce also states that users who add Interest Tags to Interaction Summaries require appropriate Financial Services access, including Financial Services Cloud Extension or Financial Services Cloud Foundations, depending on the product configuration. Before users can work with the feature, administrators must also enable Topics and Interest Tags and configure the relevant object for Topics.

Cloning one of these permission sets provides an appropriate baseline when an organization needs a specialized permission set while retaining the required Interest Tags permission. The Financial Services Cloud Standard and Basic permission sets serve other user-access patterns and do not constitute the specified source permission sets for this capability. Therefore, Extension and Foundations are the appropriate permission-set templates.

The appropriate object is Identity Document. Drivers ' licenses and passports are formal identity credentials and should be represented using a structured identity-document model rather than as generic checklist or received-document records.

Salesforce uses Identity Document terminology throughout its identity-document processing capabilities. Intelligent Document Reader and related onboarding capabilities can extract structured information from uploaded passports and driver ' s licenses by treating them as identity documents.

Modeling identity credentials explicitly allows an implementation to distinguish personally identifying documentation from ordinary supporting documents used in onboarding, underwriting, servicing, or compliance workflows. Identity-document information can then participate in identity verification, KYC, onboarding, and related Financial Services processes.

A Document Checklist Item serves a different purpose: it tracks whether a required document has been requested, received, reviewed, or otherwise processed as part of a checklist. It does not itself represent the customer ' s identity credential as the principal identity-data entity. Similarly, generic received or resolved document structures address document workflow rather than the semantic representation of the identity credential.

Therefore, when migrating customer information associated with passports and driver ' s licenses, Identity Document is the Financial Services object aligned to the identity-document use case.

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.

Salesforce Insurance Claims Management supports the complete post-loss claims lifecycle, including reserve management, payment processing, and automated adjudication. These processes operate after a covered loss has occurred and are central to evaluating, funding, and settling a claim.

Reserve Management enables adjusters to establish and modify reserves representing expected future claim exposure. The claim workspace consolidates coverages, reserves, loss items, expense items, and other claim financial information so adjusters can assess current and projected financial exposure.

Payment is another core Claims Management process. Adjusters can create payment details and issue payments while Salesforce validates applicable policy limits and updates the corresponding claim-financial records.

Auto Adjudication applies configured rules and policy information to automate claim-processing decisions where appropriate. This reduces manual handling for qualifying claims and supports straight-through processing.

Quoting belongs to the pre-policy acquisition process, while underwriting evaluates risk before coverage is issued. Those functions are part of other insurance lifecycle capabilities rather than Claims Management. Claims Management therefore centers on Reserve Management, Payment, and Auto Adjudication.

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.

Compliant Data Sharing has specific behavior when an Opportunity is changed to Private. A private Opportunity cannot be shared through Compliant Data Sharing, so Salesforce removes the sharing entries that previously granted participant-based record access.

Salesforce documents that when an Opportunity contains Opportunity Participants with associated share-table records and the Opportunity is made Private, the share-table records are deleted. However, the Opportunity Participant records themselves remain in Salesforce.

This distinction is important because the participant record represents the business relationship or participation assignment, while the share-table record represents the actual access grant generated by Compliant Data Sharing. Setting the Opportunity to Private removes the access mechanism without automatically destroying the participant data.

Salesforce recommends removing participants before making an Opportunity private when appropriate. If an Opportunity is subsequently made shareable again, the participant may need to be recreated or toggled inactive and then active so that the required sharing entry is regenerated.

Therefore, manual deletion of the share-table entries is unnecessary. Salesforce performs that cleanup automatically, while preserving the underlying participant records.

Actionable Relationship Center supports object-specific related lists so users can inspect relevant information without leaving the relationship graph. For the Account object, supported lists include Client Financial Goals, Household Financial Accounts, and Cases, making A, C, and D correct.

Salesforce ' s ARC documentation lists supported Account-related lists that include Household Financial Accounts, Household Financial Goals, Household Opportunities, Household Referrals, Financial Account Primary Owner, Client Financial Goals, Household Assets and Liabilities, Client Assets and Liabilities, Related Leads, Opportunities, and Cases.

The distinction between Account and other ARC-supported objects is important. Financial Holdings appears as a related-list option for the Financial Account object, not Account. Similarly, Notes and Attachments is supported for objects such as Contact, Lead or Referral, Opportunity, Asset and Liability, and Financial Holding, but it is not listed among the supported Account related lists in the ARC configuration matrix.

ARC can display up to ten related lists that have appropriate compact-layout configuration, and their display order follows the associated object ' s page-layout arrangement. This allows financial advisors to move from a high-level relationship visualization directly into relevant client financial goals, household account holdings, service cases, and other supported records.

Salesforce defines strict prerequisites for converting the Individual Account model to Person Accounts because the transformation changes the underlying representation of the customer.

Each Account being converted can have only one Contact record through a single direct Account Contact Relationship. Salesforce also requires that the Account must not be the parent of any other Account. The Parent Account field must be blank, and no other Account can reference the converting Account as its parent.

Additional prerequisites include matching Account and Contact owners, matching currency values where applicable, a blank Reports To field on the Contact, and ensuring no other Contact reports to the converting Contact. These controls prevent relationship structures that cannot be represented correctly after the Account and Contact become a Person Account.

The conversion must also be thoroughly tested in a sandbox. Salesforce recommends previewing how Person Accounts affect technical architecture and customizations and instructs organizations to execute the transformation in a sandbox first because migration to Person Accounts is effectively irreversible.

Neither a blank Account Phone field nor Opportunity ownership reassignment is a documented conversion prerequisite. Therefore, the required preparations represented here are C, D, and E.

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.

Interest Tags use Salesforce Topics infrastructure, but reporting begins with a custom report type whose primary object is Tag Categories. Salesforce states that Interest Tags are represented through Topics, so a report that surfaces Interest Tags must include the Topics object.

The administrator first creates a custom report type and selects Tag Categories as the Primary Object. Topics is then added as the related object. This relationship allows the report to group Interest Tags under their configured categories and display details such as the topic name, description, and the record to which the Interest Tag is assigned.

Option C reverses the required report-type relationship because Topics is not the primary object in Salesforce ' s documented Interest Tags report configuration. Option D is also inaccurate in its stated implementation. To limit results to tags assigned to a particular Salesforce object, administrators can use the record key prefix rather than simply choosing an object name from a generic filter.

This reporting architecture provides structured analysis of customer interests while retaining the Tag Category hierarchy used to organize Interest Tags. Therefore, the correct considerations are to report through Topics and make Tag Categories the primary object in the custom report type.

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.

This design requires objects that represent participation in the interaction, sharing of the interaction summary, and participation in the financial deal.

Interaction Participant associates internal users or groups with an Interaction. This enables engagement records to reflect which internal stakeholders participated in the client interaction and provides the connection between the interaction and the involved users or groups.

Interaction Summary Participant controls access to the detailed interaction notes. Salesforce allows an Interaction Summary to be shared with a specific user or group by adding that user or group through the Interaction Summary Participants related list. Compliant Data Sharing must be enabled for Interaction Summary to use this participant-based model.

Financial Deal Participant performs the corresponding function at the deal level. Financial Deal records can be shared with users or groups by adding them as participants, allowing specialists from another line of business to receive controlled access to the relevant transaction.

These objects work together effectively: the Interaction captures the engagement, the Interaction Summary contains the detailed notes, and the Financial Deal represents the underlying transaction. Participant records provide controlled association and sharing across these layers without broadly exposing sensitive information to unrelated users.

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.

Agentforce Financial Services supports this requirement through Unique event types. Events and Milestones provide advisors with an at-a-glance view of significant customer life events and business milestones so that they can understand changing client needs and identify timely engagement opportunities.

For an event that should logically occur only once for a customer, the administrator can mark its Event Type as Unique. Salesforce specifically states that this setting is intended to prevent users from accidentally creating more than one occurrence of the same unique event type.

The configuration is performed on the Person Life Event object ' s Event Type field. The administrator edits the relevant picklist value and selects Unique. Business milestones can be configured similarly by working with the appropriate milestone type. Salesforce also supports activating or deactivating event types, hiding sensitive events, defining contextual actions, changing icons, and controlling the details displayed when users interact with an event or milestone.

Once-in-a-Lifetime, Special, and Single are not the Salesforce configuration designation tested here. The supported mechanism is explicitly the Unique setting.