Explanation:
The nonprofit has three key requirements that point directly to Experience Cloud (formerly Community Cloud):

Manage Incoming Donations: This is handled by NPSP (Nonprofit Success Pack), which is the foundation of the recommended solution.

Provide a Portal for Constituents and Staff Members: Experience Cloud is the specific Salesforce platform designed to create secure, branded external portals or communities for different user groups (constituents/donors, volunteers, staff).

Create a New Web Experience for Constituents: Experience Cloud's drag-and-drop builder allows the nonprofit to quickly create a customized, modern web experience for its constituents, where they can log in to manage their profile, view their giving history, or register for events.

Correct Option: B

B. NPSP with Experience Cloud
NPSP: Manages the core donor and donation data (Requirement 1).

Experience Cloud: Provides the necessary platform to build external portals for constituents and internal portals for staff access (Requirement 2) and the tools for creating a new web experience (Requirement 3). This combination directly addresses all three requirements.

Why the Other Options Are Incorrect:

A. NPSP with Accounting Subledger
Rationale: Accounting Subledger is a tool for transferring financial data to external accounting software. It has nothing to do with creating web portals or managing external user access.

C. NPSP with Account Engagement
Rationale: Account Engagement (Pardot) is a marketing automation tool used for email campaigns, nurturing, and lead scoring. It is excellent for communication but does not create secure user portals or communities.

D. NPSP with Program Management Module
Rationale: The Program Management Module (PMM) is used to track client services and program participation. It is an internal tool for program staff and does not create external constituent portals or web experiences.

Reference
Salesforce.org Outbound Funds Module Documentation (Focus on tracking awards, grants, and applications made to external parties).

Explanation:
Integrating an external email platform (like Marketing Cloud, Mailchimp, etc.) involves syncing subscriber data and engagement activities to Salesforce. This creates records (e.g., Campaign Members, custom objects for opens/clicks) that consume data storage. The consultant must plan for data volume and retention policies to manage storage costs and system performance, and understand the required data model in NPSP for tracking subscribers.

Correct Options:

B. Email subscribers' activities can be retained for a certain length of time.
Email engagement data (opens, clicks) can generate a high volume of records. The consultant should define a data retention policy (e.g., keep activity records for 12 months) to limit storage consumption and avoid hitting data limits. This is a critical storage consideration.

D. Subscribers must be synced as Leads and Campaign Members in NPSP.
In the NPSP model, external subscribers are typically synced as Leads (if they are not yet Contacts) or Contacts, and their email campaign participation is tracked as Campaign Members. This creates Lead, Contact, and Campaign Member records, all of which consume storage. Understanding this required data model is essential for storage planning.

Incorrect Options:

A. Campaign Member records use less storage space than custom object records.
This is a misleading generalization. The storage footprint depends on the number of fields and data types, not the object type. A Campaign Member with many custom fields could use more storage than a lean custom object. This is not a reliable consideration.

C. Unsubscribed Leads should be deleted from Salesforce immediately.
Deleting records immediately is generally not advised for compliance and historical reporting. Unsubscribed Leads should be marked as unsubscribed and potentially archived or suppressed, not deleted. Immediate deletion is not a standard storage management practice.

Reference:
Salesforce Data Storage Management best practices and email integration guides. Key considerations include:

Data retention policies for high-volume activity data (Option B).

Understanding the data model impact (Leads, Contacts, Campaign Members) of syncing subscribers (Option D).
These help forecast storage needs and avoid limit issues.

Explanation:
The requirement involves a single donation (one payment) being financially split between two different scholarship funds. This is a fund accounting need, where the donation's revenue must be allocated to multiple internal accounting designations (funds). In NPSP, this is handled through General Accounting Unit (GAU) Allocations, which allow a single Opportunity (donation) to be split among multiple GAUs (funds) with specified percentages or amounts.

Correct Option:

A. GAU Allocations
GAU Allocations are the NPSP feature designed to split a single donation's financial credit among multiple funds, departments, or accounting units. The consultant would set up two GAUs for the scholarship funds and allocate the donation's amount between them (e.g., 50%/50%), ensuring proper financial tracking and reporting for each fund.

Incorrect Options:

B. Automated Soft Credits
Soft Credits are for giving philanthropic credit to additional individuals/organizations (e.g., honoring a board member), not for splitting financial revenue between internal funds. They do not affect the accounting designation of the gift.

C. Partial Soft Credit
Partial Soft Credit is a subtype of soft credit used when multiple individuals share credit for a donation (e.g., a husband and wife each get 50% credit). It is still about donor attribution, not financial allocation to internal funds.

D. Campaign Hierarchy
Campaign Hierarchy is for organizing marketing campaigns (parent/child relationships). It does not handle the financial splitting of a donation between funds.

Reference:
NPSP Documentation: "General Accounting Units (GAUs) and Allocations." This feature is specifically for allocating a single donation's revenue to multiple accounting designations, which is essential for tracking restricted gifts like scholarships split between funds.

Explanation:
The nonprofit wants to control which financial records (specifically, which Ledger Entries) are created and available for export to the external finance system. The Accounting Subledger (ASL) needs a definitive way to know when a donation's financial data is considered final and ready for the general ledger.

Correct Option: D

D. Configure Stage to State Mapping.
ASL Dependency: The Stage to State Mapping is the core configuration tool within the Accounting Subledger. This tool explicitly defines which Opportunity Stages (e.g., "Closed Won") correspond to which Ledger Entry States (e.g., "Ready to Process" or "Closed").

Controlling Export: The consultant should configure the mapping so that Ledger Entries are only created in the "Ready to Process" state (making them available for export) when the associated Opportunity reaches a final, verified Stage (like "Closed Won"). This ensures that frequently updated or incomplete records (like those in "Pledge" or "Prospecting" stages) do not create incomplete or confusing ledger entries for the finance team.

Why the Other Options Are Incorrect:

A. Configure report to filter by stage.
Rationale: Configuring a report only controls what the finance team sees, not what Ledger Entries are created. The nonprofit wants to limit the records created and available for export, which is a system automation problem, not a reporting problem.

B. Configure a Sales Process.
Rationale: A Sales Process defines the Opportunity Stages available to users. While a necessary step in the overall setup, the Sales Process itself does not tell Accounting Subledger when to create or finalize a Ledger Entry. That instruction comes from the Stage to State Mapping (D).

C. Configure Path on Opportunity.
Rationale: Path is a user interface element that provides visual guidance on the Opportunity. It has no underlying automation or connection to the Accounting Subledger logic and cannot control the creation or state of Ledger Entries.

Reference:
Accounting Subledger Documentation - Stage to State Mapping (Focus on controlling the creation and state of Ledger Entries).

Explanation:
The requirement is to add real-time chat support where clients can interact directly with staff members. This is a live, synchronous communication channel (chat) that needs to be integrated into the nonprofit's digital properties (website, portal). The solution must support agent-facing chat where staff can respond in real-time, not just automated bots or form submissions.

Correct Option:

A. Digital Engagement
Digital Engagement (part of Salesforce's Service Cloud) is the feature that enables live chat, SMS, and messaging channels directly within Salesforce. It allows nonprofits to embed a chat widget on their website, route chats to available staff agents, and manage conversations within the Service Cloud console, meeting the real-time chat requirement.

Incorrect Options:

B. Web-to-Case
Web-to-Case creates Case records from a web form submission. It is asynchronous (not real-time) and does not provide a live chat interface. It's for submitting support requests, not for instant messaging.

C. Experience Cloud
Experience Cloud is for building branded portals or communities where authenticated users can access content and self-service tools. While you can embed a live chat widget (like Digital Engagement) within an Experience Cloud site, Experience Cloud itself is not the chat solution; it's the platform that could host it. The core chat functionality requires Digital Engagement.

D. Einstein Bots
Einstein Bots provide AI-powered automated chat bots to handle common inquiries without a live agent. While bots can be part of a chat strategy, the requirement specifies a "chat interface with a staff member" (human agent), so a pure bot solution is insufficient. Digital Engagement includes the ability to integrate bots and route to live agents.

Reference:
Salesforce Service Cloud: "Digital Engagement" (formerly Live Agent). This feature is designed specifically for embedding live chat, enabling real-time conversations between customers (clients) and service agents (staff) directly within Salesforce.