Explanation:
Financial Services Cloud is delivered via a managed package (core features: custom objects like Financial Account and Group/Household Accounts, predefined list views, profiles, etc.) and several unmanaged extension packages (customizable components that can be modified).

C. Field sets that configure how fields display in the client and household profiles: Provided in the core unmanaged extension package to control field visibility and order on Lightning record pages for Individual (client) and Group (household) records.

B. The Commercial Banking dashboard: Included in the unmanaged Commercial Banking extension package for out-of-the-box analytics tailored to commercial banking users.

A is incorrect because core custom objects (Financial Account, etc.) and householding are in the managed package.
D is incorrect because predefined list views (e.g., All Clients, All Households) are part of the managed package.

References:
Salesforce Financial Services Cloud Installation Guide (Winter '26): Managed package includes custom objects and list views; unmanaged extension provides field sets for profiles. Separate unmanaged commercial banking extension provides the commercial banking dashboard.
FSC Admin Help: Install multiple unmanaged extension packages for full sector-specific features like dashboards.

Explanation:

The core problem is a lack of structured, enforced process control. Bankers are bypassing required steps. The solution must mandate a sequence of tasks and prevent progression until tasks are complete. This is the exact purpose of Action Plans.

Why C is Correct:

Enforces Process: An Action Plan Template defines a non-negotiable sequence of tasks (e.g., "1. Collect Passport, 2. Verify Address, 3. Run AML Check"). When associated with a client record, it generates the required tasks in the predefined order.

Prevents Skipping: Tasks have statuses (Not Started, In Progress, Completed). The overall onboarding stage should be gated by the completion of the Action Plan. Managers can create validation rules or Flows that prevent stage progression (e.g., moving from "Application" to "Approved") if the Action Plan is not 100% complete.

Centralized Tracking: The Action Plan provides a single, auditable checklist attached to the client record. Managers and auditors can easily report on completion rates and identify which specific tasks are being missed.

Automates Assignment & Due Dates: Tasks are automatically assigned to the relevant user with calculated due dates, ensuring accountability.

Why the Other Options Are Incorrect:

A. Create an after-save trigger to generate reminder tasks.
❌ Incorrect (Inferior Solution). While this could create tasks, it reinvents the wheel and lacks the structure of Action Plans. It would be a custom-coded, one-off solution that is harder to maintain and update than a declarative Action Plan Template. More importantly, simple "reminder" tasks do not enforce order or gate process stages—bankers could still ignore them and move on.

B. Utilize Chatter notifications for reminders.
❌ Incorrect. Chatter notifications are passive reminders, not enforceable process controls. They can be easily dismissed or ignored. They do not create trackable, reportable tasks with due dates, and they cannot prevent a banker from advancing the client to the next stage.

D. Utilize Financial Services Cloud flag Templates to flag missing items.
❌ Incorrect. While FSC has Record Alerts (flags) to highlight important information, they are indicators, not process enforcement tools. A flag can signal a missing item, but it does not create a required task, enforce a sequence, or prevent progression. Bankers could still see the flag and choose to move forward, which is the existing problem.

Key References & Implementation:

Template Design: Create an "Onboarding - KYC & Internal Tasks" Action Plan Template with all required steps in order.

Automation: Use a Record-Triggered Flow to automatically associate this template when a new client record reaches a certain stage (e.g., Status = "Application Submitted").

Audit Trail: Use standard Action Plan and Task reports for the audit team.

Summary:
To solve the problem of missed tasks in a sequential onboarding process, the consultant must recommend implementing Action Plans and Action Plan Templates. This provides the necessary structure, enforcement, and auditability that reminders, flags, or custom triggers cannot achieve.

Explanation:

The Policy Administration component in Salesforce Financial Services Cloud (FSC) for Insurance is designed to handle core policy lifecycle processes on the Policy record page. It provides guided flows and actions specifically for managing day-to-day policy servicing and administration tasks.

The three insurance processes managed by this component are:

A. Payments – Allows agents to view payment history, capture premium payments, set up payment plans, or handle payment-related adjustments directly from the Policy record.
D. Underwriting – Supports initiating or managing underwriting referrals, reviewing requirements, and tracking underwriting decisions within the policy context.
E. Endorsements – Enables agents to process policy changes (endorsements) such as adding/removing coverage, updating beneficiaries, or modifying policy details via guided experiences.

Why not B? Approvals are typically managed through standard Salesforce approval processes or custom flows, not specifically within the Policy Administration component.

Why not C? Commissions are handled separately via the Commissions component or related objects (e.g., Commission object, payout processes), usually for producer/agent compensation tracking, not core policy administration.

References:
- Salesforce Help Documentation: "Policy Administration Component" – Lists actions for Payments, Underwriting, and Endorsements as key processes.
- Trailhead: "Insurance for Financial Services Cloud" modules – Highlights the Policy Administration component for managing policy changes (endorsements), payments, and underwriting tasks.
- FSC Insurance Agent Console Guides: Policy Administration includes tabs/actions for these three processes.

Explanation:

Cumulus Bank wants to move away from manual spreadsheets and improve efficiency in gathering client data for mortgage applications. Financial Services Cloud provides industry-specific tools for mortgage processes in the Retail Banking Console.

The two recommended features are:

A. The standard mortgage flow templates to build a mortgage flow in Financial Services Cloud:
FSC includes prebuilt Mortgage Flow Templates (e.g., for New Mortgage Application, Mortgage Renewal, Refinance) that provide guided, step-by-step screen flows for collecting client financial data, property details, co-applicants, documents, etc. These templates are designed specifically for mortgage origination and can be customized or used out-of-the-box to replace spreadsheet-based data collection with a structured, compliant digital process.

B. Flow Builder to automate these business processes:
Using Flow Builder (specifically Screen Flows launched from the console), the bank can build or extend the mortgage flows to automate data gathering, validations, calculations (e.g., debt-to-income ratios), branching logic, and integration with subsequent steps (e.g., pre-approval, document requests). This directly improves efficiency by guiding bankers through the process and reducing manual entry/errors.

Together, these features enable a modern, automated mortgage application intake process within FSC.

Why not the others?

C: Creating a custom "Mortgage Application" object might be part of a fully custom solution, but FSC already provides standard objects (e.g., Financial Accounts with Mortgage record types, Loan Application custom object in some extensions) and prebuilt flows—reinventing this is not recommended.

D: Data Import Wizard helps with one-time uploads but does nothing to improve the ongoing efficiency of the data collection process—it perpetuates spreadsheet dependency.

References:
Salesforce Trailhead: "Mortgage Processes in Financial Services Cloud" (covers using standard mortgage flow templates and Flow Builder for guided application intake).
FSC Help Documentation: Retail Banking Console includes prebuilt Mortgage Flow Templates for application data collection.
Accredited Professional exam resources: Common scenario recommending standard mortgage flow templates + Flow Builder to replace manual/spreadsheet processes.

Explanation:

The Actionable Relationship Center (ARC) in Financial Services Cloud is a Lightning component that requires specific permissions to be visible and usable, even if the component is already added to the page. When some users in the same role can see and use ARC while one cannot, the most likely cause is that the affected portfolio manager is missing the required FSC permission sets that grant access to ARC functionality.

Key permissions for ARC include:

Financial Services Cloud Standard or Financial Services Cloud Extension permission sets (or equivalents like FSC Foundations).
These permission sets provide object-level access (e.g., to Account-Account Relationship, Account-Contact Relationship), field access, and app/page/component visibility for ARC.

Without these, the ARC component will not render or be interactive for the user, even if the Lightning page and component are correctly configured and visible to others.

Why not the others?

B: Incorrect — If the portfolio manager can access the Lightning record page at all, and others in the same role see ARC on the same page, the issue is not page access (which is controlled by app/profile). ARC visibility is further gated by FSC-specific permissions.

C: Incorrect — Lack of access to specific Account records would prevent viewing/editing those records or relationships, but not the entire ARC component. The question implies the component itself is not visible/usable.

D: Incorrect — If colleagues in the same role can see and use ARC, the component has been added to the page layout/Lightning page. The issue is user-specific, pointing to permissions.

References:
Salesforce Help: "Actionable Relationship Center Permissions" (requires FSC permission sets for visibility and management).
Trailhead: "Set Up the Actionable Relationship Center" (emphasizes assigning FSC permission sets to users).
FSC Accredited Professional exam resources: Common troubleshooting question linking missing ARC visibility to missing FSC permission sets when page/component setup is consistent across roles.