Explanation
The following considerations should be included when configuring the report with branch management reportable objects:
Bankers with Branches with Opportunities, Accounts, Leads, and Contacts report types are available for creating reports with Branch Unit Related Records. These are standard report types that allow users to create reports that show data from Banker, Branch Unit, Opportunity, Account, Lead, Contact, and Branch Unit Related Record objects.
The reportable objects include Banker, Branch Unit, Branch Unit Related Records, and Branch Unit Customer. These are custom objects that are part of the branch management feature in Financial Services Cloud. Banker is an object that represents a banker or an employee who works at a branch unit.
Branch Unit is an object that represents a physical location where bankers provide services to customers.
Branch Unit Related Record is an object that represents a record that is related to a branch unit, such as an opportunity, an account, a lead, or a contact. Branch Unit Customer is an object that represents a customer who has a relationship with a branch unit.
When Branch Unit is the primary object, the administrator can select Branch Unit Customers or Branch Unit Related Records as related objects. This means that the administrator can create reports that show data from Branch Unit and its related objects by using lookup fields or junction objects.

Explanation
To enable Multiple Relationship Groups, which is a feature that allows users to add individuals to more than one group or household, the Admin needs to use Custom Settings. Custom Settings are similar to custom objects and enable application developers to create custom sets of data, as well as create and associate custom data for an organization, profile, or specific user. The Admin can use Custom Settings to enable Multiple Relationship Groups by following these steps:
From Setup, enter Custom Settings in the Quick Find box, then select Custom Settings.
Click Manage next to Group Member Record Type Mapper.
Click Edit next to Default Organization Level Value.
In Multiple Relationship Groups Enabled, select True.
Click Save.

Explanation
To configure customized nodes for display in ARC, developers should reference the Lightning Web Component in the Display properties of the custom ARC relationship graph. A Lightning Web Component is a custom framework for creating reusable web components that run natively in browsers and leverage modern web standards. A custom ARC relationship graph is a metadata type in Financial Services Cloud that defines how account-account relationships are displayed in ARC, such as node shape, color, size, label, or icon. You can use Lightning Web Components and custom ARC relationship graphs to create customized nodes for ARC that show additional information or functionality for each account. Verified References: : Salesforce Help Article [9] : Salesforce Help Article [10]

Explanation
A Primary Group is a construct in Financial Services Cloud that allows you to define the main group for a client. You can use Primary Group to roll up financial data from all the financial accounts that are related to the client or the group. This way, you can get an accurate summary of the client's financial data regardless of how often they change households. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 69.

Explanation
To document the current state business process for implementing Salesforce Financial Services Cloud, the consultant should create an end-to-end visual map of the process using personas, systems, inputs, and outcomes. A visual map is a tool that can help illustrate the flow of a business process from start to finish, showing the steps, decisions, and dependencies involved in each stage. A visual map can also include personas, systems, inputs, and outcomes to provide more context and detail for each step of the process.
Personas are fictional characters that represent the different roles or users that participate in or interact with the process. Systems are the tools or applications that are used to perform or support the process. Inputs are the data or information that are required or provided for each step of the process. Outcomes are the results or outputs that are achieved or delivered by each step of the process. Verified References: : Salesforce Help Article 3 : Salesforce Help Article [4]