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.

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.

Discovery Framework combines a specialized assessment-question data model with OmniStudio to support sophisticated questionnaire-driven onboarding and needs-analysis processes. It is not fundamentally built on Salesforce Flow.

Salesforce supports both independent and hierarchical questions. A question can reference another assessment question as its parent, creating parent-child dependencies and allowing follow-up questions to be organized in a structured hierarchy.

The framework uses OmniStudio to create advanced digital forms. Discovery Framework combines its data model with OmniStudio to manage questionnaire-driven information collection and create digital forms that collect and validate customer information. These forms can include conditional behavior, integrations, and sophisticated guided logic.

Discovery Framework also supports question lifecycle management through versions. Assessment-question versioning enables administrators to replace or retire prior question content while preserving the historical structures required by previously completed assessments.

Discovery Framework forms are deployable beyond internal Lightning experiences. Activated forms can be exposed through supported digital channels, including Experience Cloud or Communities and other Salesforce experiences. Therefore, the supported considerations are hierarchical questions, sophisticated OmniStudio forms with advanced logic and integrations, and assessment-question lifecycle or archiving capabilities.

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.

A Screen Flow is the appropriate declarative solution because the process requires an internal agent to enter information into a guided form and then submit that information to an external service.

Screen Flow provides Screen elements that can capture temporary user-entered values such as the customer ' s full name and the last four digits of the Social Security number. Those values do not have to be stored in Salesforce simply because they are collected during the flow interview. They can remain flow variables used only for the authentication transaction.

Flow Builder can then invoke an external authentication service through an HTTP Callout, External Service action, Apex action, or another supported integration mechanism. The flow can send the supplied identity information, receive the authentication response, evaluate the result, and display an appropriate outcome to the customer service agent.

Screen Flows can also be launched from record-page quick actions, embedded directly on Lightning pages, or exposed through supported service-console experiences.

A custom Lightning web component or Canvas application would introduce unnecessary development for a requirement already supported declaratively. OmniScript is also capable of sophisticated guided interactions, but the requirement as stated maps directly to Salesforce ' s Screen Flow and external-callout capabilities.

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.

A Custom Relationship Group is the appropriate construct when several people or organizations participate in a meaningful business grouping that is not accurately represented as a permanent household or a single legal business entity.

Agentforce Financial Services groups are designed to represent a customer ' s broader financial circle and can aggregate information across participating members. The group model can be extended through custom group record types when the standard Household model does not match the business requirement.

In this scenario, the farmers continue to operate independently but collaborate seasonally or for a limited period. Representing the collaboration as one Business Account would incorrectly imply that they constitute a single organization. A standard Household is also inappropriate because the collaboration is commercial rather than a family unit. Contact-Contact Relationship can model a direct relationship between two people but does not provide the group-level construct required for several cooperating farms and farmers.

A customized relationship group can therefore represent the temporary collaborative business operation while keeping each farmer and farm independently modeled and related to the group. This preserves each party ' s identity and financial relationships while allowing advisors to understand and service the collaborative arrangement as a meaningful business grouping.

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.

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.

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.