In NPSP, soft credits are fundamentally based on the Opportunity Contact Role (OCR) object. Even if
"Partial Soft Credits" are used for splitting a gift, the primary mechanism for attributing a "Solicitor" to a donation is assigning them a specific role on the Opportunity.
Reporting Logic:
* The Junction: The Opportunity Contact Role acts as the bridge between the Opportunity (the donation) and the Contact (the solicitor).
* Standard Report Type: The standard report type Opportunities with Contact Roles allows the user to see the donor (the Account) and all related contacts who have a role on that gift.
* Filtering: The Admin can filter this report by the "Role" field (e.g., Role EQUALS Solicitor). This surfaces exactly who the solicitor was for every donor's transaction.
Why other options are incorrect:
* Option D: Partial Soft Credits is a more complex object used when multiple people get different dollar amounts of credit for a single gift. For a standard report showing "who the solicitor is," the Contact Role is the simpler and more standard starting point.
* Option A: Relationships track person-to-person ties (like "Spouse" or "Coworker"), not who influenced a specific financial transaction.
* Option B: This focuses on the Household structure rather than the individual donation influence history.

Data storage is a significant cost and performance consideration for nonprofits. External email platforms (like Mailchimp, Constant Contact, or Marketing Cloud) can generate millions of "Activity" records that quickly consume a Salesforce org's data storage limits.
Two Key Considerations:
* Record Type Efficiency (B): In the Salesforce storage model, Campaign Member records are highly efficient. They take up significantly less space than a record in a custom object (like a "Email Result" object). If the integration uses Campaign Members to track status, the org can store more data before hitting its limits.
* Retention Policies (C): Because individual "Open" and "Click" data becomes less relevant over time, the consultant must consider a Data Retention Policy. For example, the organization might decide to keep granular engagement data for 6 months to drive near-term marketing, but then archive or delete that data to free up space for new records.
Why other options are less relevant:
* Option A: Syncing as Leads is a functional choice, but not a "storage consideration" in itself.
* Option D: Deleting unsubscribed leads is a bad practice; you should keep the record and mark it as
"Email Opt Out" to ensure you don't accidentally re-import and email them in the future, which would violate anti-spam laws.

The organization's requirements-fixed budget, fixed scope, and deliverables defined upfront-are the classic characteristics of the Waterfall methodology.
In a Waterfall implementation for Nonprofit Cloud:
* Linear Progression: The project follows a strict sequence: Requirements -> Design -> Build -> Test -> Deploy. You do not move to the next phase until the previous one is "signed off."
* Upfront Requirements: As mentioned in the prompt, the organization believes they already know exactly what they need. A consultant spends a long "Discovery" phase at the beginning documenting every single field, report, and automation.
* Predictability: This model provides the nonprofit's board with a clear "end date" and a total cost, which is often attractive for organizations with rigid fiscal year budgets.
Why this is different from other methods:
* Agile (Option B): Agile assumes the scope will change as the users learn more about the system. It prioritizes flexibility over a fixed upfront scope.
* Kanban (Option C): Kanban is a "just-in-time" delivery system focused on visualizing work and managing flow. It is typically used for ongoing support or "business-as-usual" tasks rather than a structured implementation with a fixed SOW and predefined deliverables.
For a consultant, while the organization wants Waterfall, it is important to warn them that translating
"spreadsheets and notepads" into a sophisticated cloud system often reveals new requirements that Waterfall's rigid structure may struggle to accommodate without costly "Change Orders."

When a nonprofit requires a "portal" or a "web experience" for external users (constituents) to interact directly with Salesforce data, Experience Cloud (formerly Community Cloud) is the required solution.
How this solution meets the requirements:
* Incoming Donations (NPSP): NPSP provides the foundational data model for managing individual donors, household accounts, and the donation (Opportunity) pipeline.
* Constituent Portal (Experience Cloud): By implementing an Experience Cloud site (such as the Customer Service or Build Your Own template), the nonprofit can allow donors to:
* Log in to view their giving history.
* Download tax receipts.
* Update their contact information or communication preferences.
* Staff Management: While staff members typically use the internal Salesforce Lightning interface, Experience Cloud can also be configured for staff who need a simplified web interface for specific tasks.
* New Web Experience: Experience Cloud is a highly customizable CMS (Content Management System). It allows the nonprofit to build a branded, mobile-responsive web experience that looks and feels like their main website while being natively connected to their Salesforce data.
Why other options are incorrect:
* Program Management Module (Option A): This tracks service delivery, not web portals.
* Accounting Subledger (Option B): This is a back-office tool for finance reconciliation.
* Account Engagement (Option C): This is a marketing automation tool (Pardot) for sending emails and tracking engagement, but it does not provide a logged-in "portal" experience for constituents.

NPSP is a Managed Package. In Salesforce, you cannot simply go into Setup and change the labels of fields that are part of a managed package because those fields are "locked" to protect the package's integrity and ability to receive updates.
The Solution: Translation Workbench:
* Overriding Labels: To change "Organization" to "Organisation" (the UK spelling), the consultant must use the Translation Workbench. Even though both are English, Salesforce treats English (UK) and English (US) as different locales.
* Override Feature: Within the Translation Workbench, there is an "Override" section specifically for managed packages. The consultant selects the Nonprofit Success Pack package, chooses the object (e.
g., Account or GAU), and then enters the "New Label" for the specific field.
* Global Impact: This change is reflected across the entire user interface, including reports, list views, and page layouts, without actually modifying the underlying code of the managed package.
Why other options are incorrect:
* Reword in Setup (Option A): This works for custom fields you created, but it is blocked for fields starting with the npsp__ prefix.
* Language Settings (Option B): Activating English (UK) will change standard Salesforce labels (like
"Zip Code" to "Postcode"), but it does not automatically "UK-ize" the custom labels defined inside the NPSP managed package.
* Support Case (Option C): Salesforce support does not perform UI label customization for individual customers.