Nonprofit-Cloud-Consultant Practice Questions

Nightly batch jobs in NPSP, particularly the Rollup Donors batch, process thousands or millions of records. Any increase in the "workload" per record will result in a measurable increase in total processing time.

Two Primary Performance Factors:

New Flows (A): Salesforce Flows (especially Record-Triggered Flows) are highly powerful but resource-intensive. If a new Flow was activated on the Opportunity or Account object, it will fire every time the NPSP batch job updates a record. If the batch job updates 100,000 Accounts, the Flow runs 100,000 times. If the Flow contains "In-Loop" queries or complex logic, it can drastically slow down the batch execution time or even cause it to hit governor limits.

New Customizable Rollups (C): Every time you add a new Customizable Rollup in NPSP Settings, you are adding another calculation that the batch job must perform for every record. If the new rollup has complex filters (e.g., "Total Gifts from 3 years ago excluding In-Kind and Grants"), the system must query more data and perform more evaluations per record, extending the batch window.

Why other options are less likely:

Standard Roll-up Summary (Option B): These are calculated by the Salesforce platform kernel and are generally more efficient than Apex-based rollups. While they add some overhead, they usually do not cause the "significant" slowdowns seen with custom logic or complex NPSP settings.

Role Hierarchy (Option D): While changes to the hierarchy trigger sharing recalculations, this typically affects record visibility and sharing performance rather than the execution speed of a data-processing batch job.

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.

Nonprofit Cloud Case Management (NCCM) is a managed package that extends the capabilities of Salesforce for human services. Like many high-end Salesforce industry solutions, it has specific technical and legal prerequisites that must be met before the installation can succeed.

Prerequisite 1: Provisioned Licenses (A):

NCCM is not a free, open-source tool like NPSP. It is a paid product that requires specific Permission Set Licenses (PSLs) to be provisioned in the org. A consultant must verify that the organization has purchased the necessary licenses through their Salesforce Account Executive. Without these licenses appearing in the "Company Information" section of Setup, the managed package will not function, and users will not be able to access the custom Case Management objects like Goals, Action Items, or Case Plans.

Prerequisite 2: My Domain (C):

NCCM relies heavily on modern Lightning components and OmniStudio features to power its interactive interfaces (such as the Case Plan Wizard). Salesforce requires My Domain to be enabled and deployed in any org that uses custom Lightning components. My Domain adds a unique prefix to the Salesforce URL (e.g., https://my-nonprofit.my.salesforce.com), which is necessary for the secure rendering of these components.

Why other options are incorrect:

Volunteers for Salesforce (Option B): This is a completely separate application for managing volunteer shifts and is not required for Case Management to function.

Install NPSP (Option D): While NCCM is often used alongside NPSP, the modern Nonprofit Cloud Case Management package can technically run on a standard Salesforce platform without NPSP, provided the necessary licenses are in place.