Nonprofit Cloud Consultant Nonprofit-Cloud-Consultant Exam Questions and Answers PDF

For a small volume of contacts (150) and a simple one-off requirement like an event cancellation, standard Salesforce functionality is the most cost-effective and efficient choice. Send List Email is a native Lightning Experience feature that meets all the organization’s criteria without the complexity of a third-party marketing tool.

How Send List Email Meets the Requirements:

Direct Send: Users can select up to 2,000 contacts from a list view or a campaign and click Send List Email. This uses Salesforce's internal mail servers (or the organization's connected Office 365/Gmail account).

Send History: Every list email sent is automatically recorded in the Activity History (specifically the "HTML Email Status" or "Emails" related list) on the Contact record. This satisfies the requirement to "view the send history."

Manage Bounces: Salesforce has a native "Email Bounce Management" feature. If an email address is invalid, a warning icon appears next to the email address on the Contact record, and the staff can see the "Bounce Reason."

Resending: Because the send history is logged as an activity, staff can easily identify who didn't receive the message and trigger a follow-up email manually or by creating a filtered list of "bounced" contacts.

Why other options are incorrect:

Elevate (Option A): This is a payment processing platform for fundraising and has no native bulk email capabilities for event management.

Email-to-Case (Option B): This is a support tool for receiving incoming emails and turning them into tickets; it is not for proactive event outreach.

Account Engagement (Option D): Formerly known as Pardot, this is a robust marketing automation platform. While it could do this, it is considered "overkill" for a one-off 150-person email and requires a separate, significant license and technical setup.

One of the most common configuration hurdles in Nonprofit Cloud is understanding the "Two-Key" access model. Unlike standard Sales or Service Cloud, where a Profile can grant access to almost any object, Industry Clouds (like NPC) require a Permission Set License (PSL) to be assigned before the objects even become "visible" or "available" in the system's schema for that user.

The "Two-Key" Access Model:

The First Key (Permission Set License): The PSL "unlocks" the feature set at the organization level for a specific user. For Fundraising, the user must be assigned the Nonprofit Cloud Fundraising PSL. Without this, the Fundraising objects (like Gift Transaction) literally do not exist from that user's perspective, even if they are a System Administrator.

The Second Key (Permission Set): Once the license is assigned, the user then needs a Permission Set (e.g., "Fundraising Access") to grant the actual CRUD (Create, Read, Update, Delete) permissions.

Step-by-Step Resolution for a Consultant:

Navigate to Setup > Users.

Open the user record for the System Administrator.

Scroll to the Permission Set License Assignments related list and click Edit Assignments.

Locate and check the box for Nonprofit Cloud Fundraising (and any other relevant industry licenses like Nonprofit Cloud Grantmaking).

Once the PSL is saved, the Admin will then be able to assign themselves the necessary Permission Sets to see and manage the Fundraising objects.

Option A is incorrect because Sharing Rules control which records you see, not whether the object itself is visible. Option B is incorrect because tabs are easily accessible via the App Launcher; if the objects are missing from the "All Objects" list, it is a licensing and permissioning issue, not a tab configuration issue.

In NPSP, the relationship between a child (student) and a parent is tracked using the Relationship object. This is a5 person-to-person junction record.

Building the Report:

The Starting Point: To see the student's information (Phone/Email) alongside their parent's information, the consultant needs a report that spans the Relationship record.

Custom Report Type: A report type of Contacts with or without Relationships allows the user to list the primary contact (the Student) and pull in the "Related Contact" (the Parent) from the relationship record.

Cross-Object Fields: In the report builder, the consultant can use the "Add fields related via lookup" feature to pull the parent's cell phone and email address from the Related Contact record.

Why other options are incorrect:

Option C and D: These refer to Program Management Module (PMM) objects. While they show who is in the program, they don't natively "connect" one person's contact info to another person's contact info without a Relationship record.

Option A: "Service Participants" is a specific PMM term, but it doesn't provide the bridge to the parent/guardian data found in the NPSP Relationship model.

When donor totals (e.g., "Total Gifts This Year") are incorrect, the consultant must investigate the l30ogic that aggregates those numbers. In NPSP, this involves a combination of configuration settings and system health tools.

Three Critical Areas to Troubleshoot:

Customizable Rollups (B): This is the engine that calculates the totals. The consultant should check if the Filter Groups are correctly defined. For example, if a rollup is set to only count "Individual" gifts but the missing gifts are marked as "Major Gifts," the filter logic is the culprit.

Opportunity Stages (C): NPSP rollups only include donations that are in a "Closed/Won" state. If the organization created a custom stage (e.g., "Received - Awaiting Acknowledgment") but didn't mark that stage as "Won" in the Stage picklist settings, those gifts will be ignored by the rollup engine.

NPSP Health Check (D): This is the first place a consultant should look for system-wide issues. The Health Check will identify if the nightly rollup batch job is failing, if there are orphaned records, or if there are "Data Integrity" issues (like an Opportunity without an Account) that prevent the rollups from processing successfully.

Why other options are incorrect:

Salesforce Optimizer (Option A): This is a general org health tool (checking limits, unused fields, etc.) and does not have the nonprofit-specific logic needed to troubleshoot NPSP rollups.

Campaign Hierarchy (Option E): While hierarchies help with campaign reporting, they do not impact the "hard credit" rollups on Account and Contact records.