NP-Con-101 — Salesforce Certified Nonprofit Cloud Consultant (NPSP)

Full question text, answer options, and explanations for this practice set — a spoiler-free alternative is the interactive quiz above for scored, shuffled practice.

1. 1. What is the Nonprofit Success Pack (NPSP)?

   • A. A standalone Salesforce product for nonprofits, separate from Salesforce CRM
   • B. A free managed package installed on top of Salesforce that adds nonprofit-specific objects, features, and automation(correct)
   • C. A government grant program that provides Salesforce licenses at no cost to nonprofits
   • D. A Salesforce consulting methodology for nonprofit implementations

   Explanation: NPSP (Nonprofit Success Pack) is a free managed package from Salesforce.org installed on top of Salesforce Sales/Service Cloud. It adds nonprofit-specific features: Household accounts, Opportunity (donation) management, Recurring Gifts, Soft Credits, Relationships, TDTM automation, and more — purpose-built for constituent relationship management.

2. 2. What is the NPSP 'Household Account Model' and why is it preferred for nonprofit constituent management?

   • A. It merges all family members into a single Contact record for simplified management
   • B. It creates an Account record for each household (family), linked to individual Contact records, enabling both individual and household-level engagement, giving, and communications(correct)
   • C. It uses Person Accounts to represent each individual, eliminating the need for a separate Account
   • D. It tracks households as Opportunity records with contact roles for family members

   Explanation: The NPSP Household Account Model creates a 'Household Account' for each family unit (automatically named 'Smith Household') and links individual family members as Contacts. This enables tracking gifts at both the individual level (who actually gave) and the household level (total family giving), as well as generating household-addressed communications.

3. 3. What is 'TDTM' (Table-Driven Trigger Management) in NPSP?

   • A. A UI-based tool to create custom Apex triggers without coding
   • B. NPSP's automation framework that uses Trigger Handler records in a configuration table to manage when and how Apex automation runs(correct)
   • C. A trigger suppression setting used during data migrations to prevent NPSP automation from firing
   • D. A Salesforce Flow that replaces Apex triggers in NPSP automation

   Explanation: TDTM is NPSP's trigger management architecture. Instead of hardcoded triggers, NPSP uses a configuration table (Trigger Handler object) where each row defines: which object, which trigger event (before/after, insert/update/delete), which Apex class handles it, and whether it is active. This allows administrators to disable specific automations (e.g., during data migrations) without code changes.

4. 4. Where are NPSP global settings configured?

   • A. In Salesforce Setup → Custom Settings → Nonprofit Settings
   • B. In the NPSP Settings tab within the Nonprofit Success Pack app(correct)
   • C. In the Salesforce Admin Setup menu under 'Managed Packages'
   • D. By editing the NPSP Custom Metadata Types directly

   Explanation: NPSP global configuration is done through the 'NPSP Settings' tab in the Nonprofit Success Pack application. This provides an organized UI for configuring Households, Donations, Gift Entry, Relationships, System, and other NPSP-specific behaviors. The underlying data is stored in Salesforce Hierarchy Custom Settings.

5. 5. Which two NPSP settings are typically disabled during a bulk data migration to prevent performance issues and unwanted automation? (Choose 2)

   • A. TDTM Trigger Handlers — deactivating specific handlers to prevent rollup recalculation during import(correct)
   • B. Household Naming — disabling automatic household name/greeting generation during Contact import(correct)
   • C. Field-Level Security — disabling FLS temporarily to allow all fields to be populated
   • D. Sharing Rules — temporarily removing all sharing rules to allow admin access

   Explanation: During bulk data migration: (1) Certain TDTM Trigger Handlers (especially rollup handlers) should be deactivated to prevent repeated, inefficient rollup calculations during each record insert — recalculate once after migration completes; (2) Household Naming should be disabled to prevent the naming engine from running on every Contact insert, which causes severe performance degradation at scale. Re-enable both after migration.

6. 6. How does NPSP automatically name a Household Account when a new Contact is created?

   • A. The administrator names the Household Account manually
   • B. NPSP generates the name using the Household Naming Settings format (e.g., 'Smith Household' or 'Bob and Jane Smith')(correct)
   • C. The Household Account takes the Contact's First Name and Last Name
   • D. NPSP uses the Contact's company name as the Household Account name

   Explanation: NPSP's Household Naming engine automatically generates Account names and formal/informal greetings based on configurable name formats (e.g., '{LastName} Household', 'The {Salutation} {LastName} Family', 'Bob and Jane Smith'). The format is configured in NPSP Settings → Household Naming. When household members change, names are automatically updated.

7. 7. What is the purpose of 'Affiliations' in NPSP?

   • A. To link two Contacts who are personal friends or acquaintances
   • B. To track a Contact's formal relationship to an Organization Account (e.g., employer, board member, volunteer at a company)(correct)
   • C. To record a donor's email opt-in preferences for campaign affiliations
   • D. To associate a Contact with multiple Household Accounts

   Explanation: NPSP Affiliations track a Contact's formal connections to Organization Accounts — their employer, professional memberships, board positions, or volunteer roles at companies. Each Affiliation has a Role (employee, board member, volunteer), Primary checkbox, and dates. This models the complex multi-organization relationships that nonprofits need to track for constituent management.

8. 8. A Contact should receive correspondence addressed to their workplace, not their home. How is this handled in NPSP?

   • A. Create a second Contact record for the same person with different address fields
   • B. Set the Contact's Primary Affiliation to the organization and use the 'Mailing Overwrite' feature to use the Organization's address
   • C. Manually enter the work address in all Mailing Address fields, replacing the home address
   • D. Configure an Address override on the Contact linking to the Organization Account address(correct)

   Explanation: NPSP's Address Management allows Contacts to have multiple addresses (home, work, seasonal, etc.). Setting an address as the Contact's 'Preferred' or using Address Overrides on the Contact allows the mailing address to point to their work address (via Affiliation to the Organization Account) instead of their Household address. This is managed through the NPSP Address object.

9. 9. Which two NPSP features help prevent duplicate Contact records in the database? (Choose 2)

   • A. Salesforce Duplicate Rules and Matching Rules configured for the Contact object(correct)
   • B. NPSP's built-in 'Fuzzy Match' duplicate detection algorithm that runs on all Contact saves
   • C. Data Import Wizard with 'Match by Name' or 'Match by Email' settings(correct)
   • D. Third-party deduplication tools from the AppExchange (e.g., DemandTools, Cloudingo)

   Explanation: Duplicate prevention in NPSP/Salesforce uses: (1) Salesforce Duplicate Rules with Matching Rules on Contact to alert or block when a potential duplicate is detected during manual entry; (2) NPSP Data Import Wizard's matching settings that can match incoming records to existing Contacts by name, email, or other fields, updating existing records instead of creating duplicates. NPSP has no built-in fuzzy match engine; third-party tools are supplements.

10. 10. What happens to a Contact's Household Account when the Contact is deceased and marked with a Deceased checkbox in NPSP?

    • A. The Contact is automatically deleted from Salesforce
    • B. NPSP can be configured to remove the Contact from the Household naming (omit from household name/greeting) and optionally move them to a separate deceased account
    • C. The Household Account is automatically renamed to reflect the remaining members
    • D. Both B and C are correct depending on NPSP settings(correct)

    Explanation: When a Contact is marked Deceased in NPSP: (1) The Household Naming engine can be configured to exclude deceased members from the household name and greetings; (2) NPSP can automatically rename the Household Account to reflect remaining members (e.g., 'Jane Smith Household' instead of 'Bob and Jane Smith Household'). Both behaviors occur based on NPSP Household naming configuration.

11. 11. In NPSP, what is the 'Preferred Email' and 'Preferred Phone' functionality?

    • A. Fields that store the email and phone that marketing campaigns should use
    • B. Custom fields that, when selected, automatically copy the chosen email type or phone type to the standard Email and Phone fields for system-wide compatibility(correct)
    • C. Fields that indicate whether the contact prefers email or phone outreach
    • D. Integration settings for email delivery preferences in Marketing Cloud

    Explanation: NPSP's Preferred Email and Preferred Phone features allow nonprofits to store multiple email/phone values (home, work, alternate) on Contact records. When a user selects a Preferred Email picklist value (e.g., 'Work'), NPSP automatically copies that email value to the standard Email field, ensuring tools that only look at the standard field use the correct contact method.

12. 12. In NPSP, which Salesforce standard object is used to record donations?

    • A. The NPSP Donation custom object
    • B. The Salesforce Opportunity object(correct)
    • C. The Payment object from NPSP
    • D. The Salesforce Activity (Task) object

    Explanation: NPSP uses the standard Salesforce Opportunity object to record donations. NPSP adds Opportunity record types (e.g., 'Donation', 'Grant', 'Major Gift', 'In-Kind') and custom fields for gift processing. This leverages the existing Salesforce CRM infrastructure and reporting capabilities for the core donations object.

13. 13. What is a 'Recurring Donation' in NPSP and how does it work?

    • A. A single large gift paid in multiple installments with fixed amounts and dates
    • B. A giving commitment that automatically creates Opportunity records on a defined schedule (monthly, quarterly, annually) for an open-ended or fixed number of periods(correct)
    • C. A donor's recurring credit card charge processed natively by NPSP
    • D. A Campaign that runs the same fundraising appeal every year

    Explanation: NPSP Recurring Donations are commitments that auto-generate Opportunity records on a configured schedule. Each installment period creates a new Opportunity that can be linked to payment processing for collection. NPSP Enhanced Recurring Donations (NPSP's updated version) added a Recurring Donation record with improved status management, pause/resume capabilities, and flexible scheduling.

14. 14. What is NPSP's 'Gift Entry' feature and how does it improve the donation processing workflow?

    • A. A Salesforce standard feature for entering gifts directly into the ledger
    • B. A batch gift entry interface that allows data entry staff to enter multiple donations in a single session, matching to existing donors and creating Opportunities efficiently(correct)
    • C. A feature exclusive to Nonprofit Cloud (NPC) that is not available in NPSP
    • D. An Einstein AI tool that extracts gift amounts from scanned check images

    Explanation: NPSP's Gift Entry feature (available in Enhanced Recurring Donations/NPSP 3.0+) provides an optimized batch data entry interface for processing high volumes of gifts — processing checks after a fundraising event or mail campaign. It allows matching incoming gifts to existing donors, creating or updating Recurring Donations, and batch processing multiple records without navigating individual Opportunity pages.

15. 15. In NPSP, what does the 'Payment' object (npe01__OppPayment__c) track?

    • A. Credit card transaction IDs from the payment processor
    • B. The specific payment method and date for each payment installment against an Opportunity(correct)
    • C. The nonprofit's payment obligations to vendors
    • D. Recurring Donation payment schedules

    Explanation: The NPSP Payment object (npe01__OppPayment__c) stores the specific payment details for an Opportunity: payment method (check, credit card, wire), check number, payment date, and amount. An Opportunity can have multiple Payments (e.g., a pledge paid in installments). When all Payments are marked Paid, NPSP automatically marks the Opportunity as Closed Won.

16. 16. Which two scenarios trigger NPSP to automatically create a Payment record for an Opportunity? (Choose 2)

    • A. When an Opportunity is created with a Close Date in the future (NPSP auto-creates one open Payment)(correct)
    • B. When an Opportunity is marked Closed Won (NPSP auto-creates a Paid Payment if none exist)
    • C. When a Campaign Member clicks a donation link in an email
    • D. When a Recurring Donation installment Opportunity is created by the Recurring Donation engine(correct)

    Explanation: NPSP automatically creates Payment records: (1) When any Opportunity is created, NPSP creates one matching open Payment record (configurable in NPSP Settings → Donations); (2) When the Recurring Donation engine creates installment Opportunities, it creates associated Payment records. Closed Won auto-creation is configurable. Campaign Member clicks are outside NPSP's scope.

17. 17. What is an 'In-Kind Gift' in NPSP and how should it be recorded?

    • A. A gift of publicly traded stock, entered as a cash equivalent
    • B. A non-cash donation of goods or services, recorded as an Opportunity with the 'In-Kind' record type and a value in the Amount field(correct)
    • C. A gift that the donor wants to remain anonymous (in-kind = anonymous)
    • D. A matching gift contributed by the donor's employer

    Explanation: In-Kind Gifts are non-cash donations (donated computers, food, professional services). In NPSP, they are recorded as Opportunities with an 'In-Kind' record type, with the fair market value entered as the Amount. Tracking them allows nonprofits to report total giving (cash + in-kind), which is important for grant reports and organizational impact. Payment records for in-kind gifts are typically marked 'Written Off' or closed without a payment method.

18. 18. What is a 'Soft Credit' in NPSP?

    • A. A partial credit given to donors when a gift is refunded
    • B. Credit given to a Contact who influenced a donation but is not the primary donor — used to track who helped secure a gift(correct)
    • C. A credit that reduces the donor's next gift by a specified amount
    • D. A gift-in-kind with no monetary value that is 'softly' tracked

    Explanation: Soft Credits in NPSP give credit to Contacts who influenced a donation — solicitors, event hosts, board members who made introductions, or employers who offer matching gifts. The Opportunity Contact Role with the 'Soft Credit' role type triggers NPSP to add the gift amount to that Contact's soft credit rollup fields, enabling the organization to recognize the influence network around each gift.

19. 19. Which NPSP feature automatically creates Soft Credits for Household members when one member makes a gift?

    • A. NPSP Household Rollup — rollups automatically include all household members
    • B. Household Soft Credits — configured to give Household members a soft credit for each other's gifts(correct)
    • C. TDTM trigger on Opportunity Contact Roles that creates Soft Credits for spouses
    • D. This is not supported; Soft Credits must be manually created for each household member

    Explanation: NPSP's Household Soft Credits feature can be enabled to automatically give Soft Credits to household members (typically spouses/partners) for each other's gifts. This means if Jane gives $500, Bob (her household member) also receives a $500 soft credit. This is critical for major gift strategies where both partners in a household should be cultivated and credited for household-level giving.

20. 20. What is the 'Relationships' feature in NPSP used for?

    • A. Tracking constituent relationships to the nonprofit (donor, volunteer, board member)
    • B. Modeling interpersonal relationships between Contacts (spouse, parent, colleague, friend, business partner)(correct)
    • C. Defining reporting relationships between staff members in the org chart
    • D. Linking donor Contacts to the corporations where they work

    Explanation: NPSP Relationships model the interpersonal connections between Contacts — spouse, parent, child, colleague, mentor, friend, board colleague, etc. Each Relationship record is bidirectional (creating a 'Husband of' also creates a reciprocal 'Wife of') and tracks the relationship type, start/end dates, and status. This relationship intelligence is vital for major gift strategies and constituent research.

21. 21. Which two NPSP rollup fields on the Contact/Account show giving history used for donor analytics? (Choose 2)

    • A. Total Gifts (npo02__TotalOppAmount__c) — sum of all Closed Won Opportunity amounts(correct)
    • B. Last Gift Date (npo02__LastCloseDate__c) — date of the most recent Closed Won Opportunity(correct)
    • C. Lifetime Gifts Count (npo02__NumberOfOpps__c) — count of all Closed Won Opportunities
    • D. Average Gift Size (npo02__AverageGift__c) — mathematical average of all gifts

    Explanation: NPSP provides a rich set of rollup fields on Contact/Household Account including Total Gifts (sum of all Closed Won gift amounts), Last Gift Date (most recent Closed Won gift), and many more. These are calculated by NPSP's rollup engine and updated whenever a related Opportunity is created, updated, or closed. Total Gifts and Last Gift Date are two of the most commonly used for donor analytics and segmentation.

22. 22. How does NPSP use the standard Salesforce Campaign object for nonprofits?

    • A. Campaigns are only used for email marketing and are not linked to gift tracking in NPSP
    • B. Campaigns track fundraising appeals, events, and outreach efforts, linking gifts (Opportunities) to campaigns for source tracking and ROI analysis(correct)
    • C. NPSP replaces Campaigns with a custom 'Appeal' object
    • D. Campaigns are disabled in NPSP to prevent duplication with NPSP's Donation tracking

    Explanation: NPSP uses the standard Salesforce Campaign for fundraising appeals (direct mail, events, online campaigns, grant proposals). Opportunities are linked to Campaigns via the Primary Campaign Source field, enabling revenue attribution reporting: how much each campaign raised, cost vs. income, donor response rate, and campaign ROI — essential for fundraising strategy.

23. 23. What is NPSP's 'Customizable Rollups' feature?

    • A. A drag-and-drop interface for creating custom rollup reports
    • B. An NPSP feature that allows administrators to define custom rollup field configurations beyond the standard NPSP rollup fields, without requiring custom Apex code(correct)
    • C. A Tableau CRM extension that provides rollup visualizations for NPSP data
    • D. A feature that rolls up Campaign data to parent Campaigns automatically

    Explanation: NPSP Customizable Rollups (CMR) allows administrators to create additional rollup field configurations beyond NPSP's standard rollup fields — for example, 'Total gifts in the last 5 years', 'Total restricted gifts', or 'Average gift by channel'. These are configured via the NPSP Settings UI without Apex code, using filter groups to define which Opportunities/Payments to include.

24. 24. Which two NPSP reports or report types are most useful for annual fund reporting? (Choose 2)

    • A. NPSP Donors and Donations report type — showing all Contacts with associated Opportunities(correct)
    • B. NPSP Household Giving report — showing total giving by Household Account(correct)
    • C. The standard Salesforce 'Opportunities with Contact Roles' report type
    • D. NPSP Recurring Donations by Status report — showing all active monthly donors

    Explanation: For annual fund reporting: (1) NPSP provides custom report types like 'Donors and Donations' that join Contact-level data with Opportunity history, enabling constituent-level gift analysis; (2) Household Giving reports aggregate giving by household for capacity analysis, LYBUNT/SYBUNT identification, and recognition-level tracking. Both are foundational for year-end donor analysis.

25. 25. What does 'LYBUNT' stand for in nonprofit fundraising parlance and how is it used in Salesforce NPSP reporting?

    • A. Last Year's Budget Utilization by Nonprofit Tracker — a financial planning metric
    • B. Last Year But Unfortunately Not This (year) — donors who gave in the previous fiscal year but not the current year; used in retention and recapture campaign targeting(correct)
    • C. Lifetime Year By Unit Number Total — a cumulative giving metric
    • D. Largest Year Balance Unrestricted Nonprofit Total — a fund balance calculation

    Explanation: LYBUNT ('Last Year But Unfortunately Not This') identifies donors who gave in the previous fiscal year but have not yet given in the current year. In NPSP, LYBUNT reports filter on NPSP rollup fields: 'Last Gift Date was in [prior fiscal year]' AND 'Last Gift Date was NOT in [current fiscal year]'. These donors are high-priority re-engagement targets since they already have a giving relationship with the organization.