Salesforce Updated Nonprofit-Cloud-Consultant Exam Questions and Answers by freyja

While Duplicate Rules and Matching Rules are essential for preventing new duplicates from being created, they do not help with a database that already contains existing duplicates (which is common after large direct mail imports).12

The Solution for "Auto13mating the Search":

On Unlimited Edition, Salesforce provides a feature called Duplicate Jobs.

Scanning the Database: Unlike rules that fire during a save, a Duplicate Job runs a scan across the entire existing database (or a specific segment) to find existing duplicate records based on your Matching Rules.

Reporting: Once the job completes, it generates a list of "Duplicate Record Sets." This allows the nonprofit's data integrity team to review and merge records in bulk.

Use Case: For a direct mail organization, running a Duplicate Job before a large mailing ensures they aren't wasting money by sending two identical letters to the same household.

Why other options are incorrect:

Duplicate/Matching Rules (Options A & C): These act as "gatekeepers" during data entry. They find duplicates only when a record is created or edited; they do not proactively "search" the existing database.

Scheduled Apex (Option D): This is a custom coding solution. A consultant should always recommend native, declarative features like Duplicate Jobs before suggesting custom code.

This is a "Solution Design" question where the organization's business model dictates the architecture. While NPSP is the default for most nonprofits, it is specifically designed for Individual and Household giving.

If an organization functions like a B2B (Business-to-Business) corporation and only receives funding from other corporations:

Simplification: They do not need the "Household" or "One-to-One" complexity of NPSP. These models are designed to "wrap" a contact in an account to support individual donations.

Standard Sales Cloud: The Standard Account Model (where a Contact belongs directly to an Account/Corporation) is exactly how Salesforce was originally designed to work for corporate sales.

Lead/Pipeline Management: By using Standard Salesforce (without NPSP), they get the cleanest experience for Lead conversion and Opportunity management, as all the NPSP-specific automation (like Household naming) would be unnecessary overhead for a purely corporate funding model.

Option A (Person Accounts) is also a specialty model, but it is intended for B2C (Business-to-Consumer) interactions. For a social enterprise dealing with corporations, Standard Accounts provide the best "out-of-the-box" fit.

The fundraising data model in the new Nonprofit Cloud (NPC) differs significantly from the older NPSP "Recurring Donations" object. NPC utilizes the Fundraising feature set, which is built on a high-performance architecture shared with other Industry Clouds.

To manage recurring giving, two primary objects are required:

Gift Commitment: This object represents the donor's "promise" or agreement to give a certain amount over time. It stores high-level information such as the total amount of the commitment, the donor (Person Account), and the status (e.g., Active, Paused, or Fulfilled).

Gift Commitment Schedule: This is the engine that drives the frequency of the gift. It defines when and how often the donation should be processed (e.g., Monthly on the 15th, or Weekly on Mondays). A single Gift Commitment can actually have multiple schedules if a donor has a complex giving plan.

The Workflow for a Consultant:

Create the Gift Commitment: When a donor signs up for a monthly giving program, the consultant (or the automated system) creates a Gift Commitment record.

Define the Schedule: A Gift Commitment Schedule record is then linked to that commitment, specifying the recurring transaction amount and the transaction period.

Automated Processing: Once these are active, the Nonprofit Cloud's Gift Processing engine uses the schedule to automatically generate Gift Transaction records (which are the equivalent of "received" donations) on the specified dates.

Option A is incorrect because "Opportunity" is part of the legacy NPSP model or standard Sales Cloud; while NPC can use Opportunities, the specific recurring logic in NPC is handled by Gift Commitments. Option C is incorrect because Gift Designation is used to track the fund or purpose the money is for (e.g., "Scholarship Fund"), which is applicable to both one-time and recurring gifts, but is not the object that establishes the recurring nature of the gift.