Explanation:
The requirement involves bulk-creating over 100 new Contacts and a related Case record for each Contact from a single spreadsheet after field work. The fastest, no-cost, out-of-the-box solution is the Salesforce Data Import Wizard (Setup → Data Import Wizard), which natively supports importing Contacts and creating one related Case per Contact in a single import operation using one CSV file. This is explicitly designed for case management scenarios and works in both NPSP and Nonprofit Cloud environments.

Correct Option:

A – Use Data Import Wizard to insert Contacts and related Cases.
Data Import Wizard allows mapping spreadsheet columns to Contact fields and Case fields simultaneously.

It automatically creates a Case for each successfully imported Contact and links them via the standard Contact lookup on Case.

Supports 50,000+ records, duplicate checking, and field mapping—no app install or extra licensing required.

Incorrect Option:

B – Configure NPSP Data Importer to upsert Contacts with related Cases.
NPSP Data Importer is designed for donations (Opportunities + Payments), not for Cases.

It does not support creating or relating Case records.

C – Install Case Management to upsert Contacts and relate them to Cases.
Nonprofit Cloud Case Management does not include a bulk import tool for Contacts + Cases.

The Data Import Wizard works the same with or without Case Management installed.

D – Create a web-to-case form that case managers will use to record the contact details.
Web-to-Case is for external users submitting cases via a public website, not for internal staff bulk-entry from a spreadsheet after field work.

Reference:
Salesforce Help → Data Import Wizard → “Import Contacts and Cases”

Explanation:
This question focuses on troubleshooting inaccurate roll-up summaries on donor (Contact or Account) records within NPSP. While Customizable Rollups (CRLP) could be involved, the most common and fundamental issue is the data relationship itself. Donation totals rely on the link between the Opportunity (donation) and the donor, which is primarily defined by the Primary Contact field on the Opportunity.

Correct Option:

B. Verify Opportunity Primary Contact.
NPSP roll-up summaries (both standard and customizable) typically aggregate donations based on the Primary Contact lookup field on the Opportunity. If this field is blank, incorrect, or pointing to a different Contact, the donation amounts will not roll up to the intended donor's record. This is the first and most critical data integrity check.

Incorrect Options:

A. Check if the correct Operation is chosen.
The "Operation" (SUM, COUNT, etc.) is a configuration setting within a Customizable Rollup definition. If the operation were wrong, it would cause a systematic error for all donors meeting its filter criteria, not an isolated issue for "a handful of donors." The problem described is more likely data-specific.

C. Check if the correct target custom field is chosen.
This is a configuration check for a Customizable Rollup, similar to option A. An incorrect target field would cause the rollup to populate the wrong field for every donor affected by that rollup definition, not just a random handful. It does not address the core issue of which donor the Opportunity is linked to.

D. Verify Customizable Rollups is enabled.
If Customizable Rollups were entirely disabled, no roll-up fields would update for any donor, causing a widespread failure. The scenario describes only a few affected donors, indicating the feature is likely enabled but encountering a data issue for specific records.

Reference:
NPSP Documentation: "How Donations Are Rolled Up" and "Troubleshoot Rollups." These resources explain that the Primary Contact field on the Opportunity is the key relationship for most donation rollups. Verifying this field's accuracy is always a primary troubleshooting step for missing or incorrect totals.

Explanation:
The NPSP Household Mailing List button runs a pre-built report that is filtered by the Campaign ID. The error "data unavailable" for a non-admin user typically indicates a report folder or filter access issue, not an Apex class or object permission problem (since the admin can run it). The most common cause is that the report's filter on Campaign ID is locked, meaning users cannot change it, and the report tries to run with a blank or invalid Campaign ID for their context.

Correct Option:

B. Check if the Campaign ID filter in the Campaign Household Mailing List report is unlocked.
The standard NPSP "Campaign Household Mailing List" report has a filter for "Campaign ID". If this filter is locked, the report attempts to run with a stored Campaign ID value that the user may not have access to (due to Campaign sharing), resulting in "data unavailable." Unlocking the filter allows the report to prompt the user to enter a Campaign ID they can access when they click the button, resolving the issue.

Incorrect Options:

A. Check if the user has access to the Apex Class for Manage Households.
The button executes a report, not an Apex class. User permissions for Apex classes are irrelevant here. The error is about data access in the report, not code execution.

C. Check if the user has the View Reports in Public Folders system permission.
While this permission is necessary to see reports in public folders, the user is able to click the button and get an error, suggesting they have at least some access to the report. The error is specific to the data in the report, not the report's visibility. The admin would also check if the report is in a public folder, but the locked filter (Option B) is the more precise and common cause.

D. Check if the user has access to Households via Role hierarchy.
The report is based on Campaign Members and Contacts/Households. If the user lacks access to the Campaign records (due to sharing rules), they cannot see the Campaign Member data, which could cause this error. However, the primary diagnostic step is to first verify the Campaign ID filter is unlocked, as a locked filter with an ID they can't access is the most direct cause. Role hierarchy may affect Campaign access, but the filter setting is the immediate configuration to check.

Reference:
NPSP Documentation: "Troubleshoot the Household Mailing List Report." The guide specifically addresses this error, advising to unlock the Campaign ID filter on the underlying report to allow users to input a Campaign ID they have permission to view. This is a standard fix for this permission-based error.

Explanation:
The nonprofit wants to automate the search for duplicate contact records, specifically within the context of a direct mail fundraising channel. This indicates a need for proactive, ongoing duplicate detection, not just blocking duplicates at the point of entry. In Salesforce, Matching Rules define the criteria for identifying potential duplicates, and they are used by Duplicate Rules to either report on or block duplicates. To automate the search (i.e., regularly scan and report), you need Matching Rules combined with Duplicate Rules set to "Allow" and potentially scheduled jobs.

Correct Option:

A. Matching Rules
Matching Rules are the foundation. They define the field comparisons and logic (e.g., "First Name, Last Name, and Postal Code match") used to identify duplicate records. Without a Matching Rule, you cannot have a Duplicate Rule. The consultant must first create or confirm the appropriate Matching Rule for contact deduplication.

Incorrect Options:

B. Duplicate Rules
Duplicate Rules control the action when a match is found (e.g., "Block" or "Allow" the save, and "Report"). While essential for the overall solution, the question asks for what to implement to "automate the search." The search logic itself is defined by the Matching Rule. Duplicate Rules use Matching Rules to perform the search.

C. Scheduled Apex Jobs
While you could write Scheduled Apex to scan for duplicates, this is a custom, programmatic solution and is unnecessary. Salesforce provides declarative Duplicate and Matching Rules that can be configured to run on record creation/edit and can also be used in batch processes or reports to find existing duplicates.

D. Duplicate Jobs
There is no standard Salesforce feature called "Duplicate Jobs." You can run reports based on Duplicate Rules or use Data.com Duplicate Management to find duplicates, but this is not a specific, named "Job" object.

Reference:
Salesforce Help: "Duplicate Management" and "Matching Rules." To automate duplicate search, you configure:

Matching Rules (define the search criteria).

Duplicate Rules (set to "Allow" to not block saves, and use in duplicate reports).
For ongoing detection in direct mail, the consultant would ensure the correct Matching Rule exists and is used in a Duplicate Rule that allows saves but logs them for review (e.g., via the "Duplicate Record Sets" object).

Explanation:

In NPSP, the Matching Gifts feature allows nonprofits to track and manage when an employer or company matches a donor’s contribution.
If a donor doesn’t indicate their gift is eligible for matching but the nonprofit later learns it is, staff can use Find Matched Gifts on the Opportunity.
The Find More Gifts button helps locate related gifts and connect them properly, ensuring reporting and donor crediting is accurate.
This avoids manual workarounds and leverages NPSP’s built-in functionality.

Why not the others?
B. Create a Lightning quick action declaratively → ❌ Not relevant.
This is a UI customization option, but the requirement is about gift management, not interface shortcuts.
C. Create a Contact lookup field on the Opportunity object → ❌ Unnecessary.
Opportunities already relate to Contacts and Accounts, and Matching Gifts don’t require extra custom lookups.
D. Select Manage Soft Credits and change the Role for the donor → ❌
This is for assigning credit for influence (e.g., when someone solicits a gift), not for recording employer matches.

Reference:
NPSP Matching Gifts Documentation
Salesforce Trailhead: Manage Matching Gifts in NPSP

⚡ Exam Tip:
When you see a question about matching gifts, always think about the built-in Matching Gifts functionality in NPSP rather than soft credits or customizations.