Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (NPC) NP-Con-102 Free Practice Exam Questions (2025 Updated)

To ensure effective user acceptance testing and training before going live with its Nonprofit Cloud implementation, a nonprofit can use the following sandbox configuration options:

Partial Data Sandbox:

This sandbox type includes a subset of the production data, which is useful for testing with realistic data without the need for a full copy of the production environment. It provides a balance between data availability and cost.

To search for nonprofit user groups in a particular region or state, an admin should use the Trailblazer Community:

Access Trailblazer Community:

Go to the Trailblazer Community website: trailblazer.salesforce.com.

Search for User Groups:

Use the search functionality to look for user groups. You can enter keywords related to your region, state, or specific interests such as "nonprofit user groups."

You can also filter search results by location to find groups relevant to your area.

Join Relevant Groups:

Review the list of user groups and join the ones that are most relevant to your needs.

Engaging with these groups allows you to connect with other nonprofit Salesforce users, share best practices, and stay informed about local events and meetups.

The Trailblazer Community is a valuable resource for finding and connecting with regional nonprofit user groups.

When migrating historic donation records into a nonprofit's Salesforce org where many of these donations were paid in multiple installments, it is important to ensure that the Payments are correctly matched to the Opportunities. The correct approach involves using the "Do Not Automatically Create Payment" field:

Check the Do Not Automatically Create Payment Field:

When importing historic donations, check the "Do Not Automatically Create Payment" field on the Opportunities.

This prevents Salesforce from automatically creating Payments for these Opportunities, which allows you to manually enter the correct Payments that match the historic installment records.

Manually Create Payments:

After importing the Opportunities with the "Do Not Automatically Create Payment" field checked, manually create Payment records that correspond to each installment.

Ensure each Payment is correctly associated with the corresponding Opportunity.

Validation:

Validate the imported data to ensure all Payments are correctly matched with the Opportunities.

This method ensures that the historic donation records with multiple installments are accurately represented in Salesforce.

check the entity relationship diagram

When evaluating whether to use Program Management Module (PMM) or Nonprofit Cloud Case Management, it is important to consider the specific requirements of the nonprofit. While PMM can track programs, services, and the impact of those services, Nonprofit Cloud Case Management offers additional functionality tailored to human services nonprofits. Case Management includes custom objects specifically designed to track client goals and action items, making it more suitable for organizations needing detailed goal tracking.

Steps:

Assess the specific requirements for tracking client goals and action items.

Compare the features of PMM and Case Management.

Highlight that Case Management has a custom object for tracking goals and action items.

Discuss the benefits and potential limitations of implementing Case Management, including the need for Experience Cloud licenses if applicable.

Before installing the Volunteers for Salesforce package, a consultant should:

Check that the nonprofit has the most recent NPSP release:

Ensure that the organization is running the latest version of the Nonprofit Success Pack (NPSP). This is crucial because newer releases might contain important updates and fixes that can impact the installation and functionality of Volunteers for Salesforce.

To troubleshoot the error message "Npsp,TDTMCContact

of AfterUpdate caused by : System,SObjectException

field gender_c Contact (npsp)," the admin should:

Check for Invalid Values:

The error indicates that there might be invalid values in the gender field on Contact records.

Review the values in the gender field across the Contact records to ensure they conform to the expected values (e.g., Male, Female, Non-binary).

Steps to Verify and Correct Values:

Use Salesforce reports or data export tools to extract Contact records with gender values.

Check for any discrepancies or invalid entries.

Correct the invalid values by updating the records with appropriate values.

Review Field Mappings and Settings:

Ensure that any field mappings related to the gender field in Relationship settings or Reciprocal Relationships are correctly configured.

By ensuring the gender field values are valid, the admin can resolve the error and ensure smooth execution of the after-update trigger.

To ensure the campaign for monthly project updates to donors who have given 10 or more times stays current, the consultant should:

Create a Contact Report:

Create a report on the Contact object and include a filter to display only those contacts whose total number of gifts meets the criteria (10 or more).

This filter ensures that only the relevant donors are included in the report.

Run the Report Monthly:

Schedule or manually run the report each month to get the updated list of donors.

Use the "Add to Campaign" button to add the contacts from the report to the newsletter campaign, ensuring the campaign list stays current with donors who meet the criteria.

Salesforce Reporting Guide

Salesforce Campaign Management Guide

For a nonprofit organization providing case management and requiring automatic scoring of clients based on various factors like age, income, and health conditions, along with automating the creation and assignment of follow-up tasks, the best combination of functions is Engagement Plans and Levels.

Engagement Plans: These are used to automate the creation of tasks and follow-up activities based on predefined templates. This feature ensures that specific tasks are generated and assigned to relevant staff members as soon as certain criteria are met.

Steps to Set Up Engagement Plans:

Navigate to the "Engagement Plans" tab in NPSP.

Create a new Engagement Plan Template, defining the tasks and follow-ups that should be created.

Specify the conditions under which this Engagement Plan should be triggered (e.g., a new client intake).

Assign the Engagement Plan to the appropriate client records.

Levels: These are used to categorize clients (or any other records) based on numeric values or other criteria. In this case, Levels can be used to automatically assign a score to each client based on their age, income, and health conditions.

Steps to Set Up Levels:

Navigate to NPSP Settings > Levels.

Create a new Level, specifying the criteria for each level (e.g., age range, income bracket, number of health conditions).

Define the actions that should be triggered when a client reaches a specific level.

By using Engagement Plans and Levels, the nonprofit can automate both the scoring of clients and the creation of follow-up tasks, ensuring a streamlined case management process.

To add donors to a Campaign from an Opportunities report, the report must include Contact records. The correct approach is to create a report type that includes Contacts, such as the Opportunities with Contact Roles report type.

Creating the Report:

Navigate to the Reports tab and click "New Report."

Select the "Opportunities with Contact Roles" report type. This report type includes both Opportunity and Contact records.

Configuring the Report:

Add the necessary filters to include the desired Opportunities and their related Contacts.

Customize the report to display relevant fields, such as Contact Name and Opportunity Amount.

Adding to Campaign:

Once the report is configured and run, select the Contacts you want to add to the Campaign.

Use the "Add to Campaign" button available in the report to add these Contacts as Campaign Members.

Benefits of This Approach:

Ensures that the Campaign Members are correctly linked to the Opportunity records.

Streamlines the process of managing Campaigns and associated donor information.

Additional Steps:

Ensure that the "Add to Campaign" button is enabled for the report type in Setup if it is not already visible.

To create a custom Apex class in the TDTM (Table Driven Trigger Management) framework, follow these steps:

Create the Apex Class:

In Salesforce, go to Setup.

Navigate to "Apex Classes" under "Custom Code".

Click "New" and create your custom Apex class.

Ensure the class implements the TDTM framework correctly.

Create the Test Class:

Create a corresponding test class to ensure your Apex class functions as expected.

This is essential for maintaining code coverage and passing Salesforce deployment requirements.

Create a Trigger Handler Record:

Go to the TDTM Trigger Handlers tab.

Create a new Trigger Handler record and link it to your custom Apex class.

Define the order of execution and the object the trigger applies to.

These steps ensure that your custom Apex class is correctly integrated into the TDTM framework, maintaining organized and manageable trigger logic.

Salesforce NPSP Documentation: TDTM Overview

Salesforce Trailhead: Apex Basics & Database

When using NPSP (Nonprofit Success Pack) with the default account model and a new Contact is created without specifying an Account Name, NPSP automatically creates an Account with a household name.

Default Account Model in NPSP:

NPSP typically uses the Household Account Model by default.

This model groups individuals into households, making it easier to manage and report on donor families.

Automatic Account Creation:

If a Contact is created without an Account Name, NPSP automatically generates a Household Account.

The name of the Household Account is usually derived from the Contact’s last name, formatted as "The [LastName] Household."

Process:

Step 1: A user creates a new Contact record, leaving the Account Name field blank.

Step 2: Upon saving the Contact, NPSP checks for an existing Household Account.

Step 3: If no Household Account exists, NPSP creates a new Household Account using the Contact’s last name.

Benefits:

Organization: Ensures that all Contacts are associated with an Account, maintaining data integrity.

Reporting: Facilitates household-level reporting and analytics.

To allow prospective volunteers to fill out their volunteer application online:

Set up the Volunteers for Salesforce Volunteer Signup Form: This form can be embedded on the nonprofit's website, allowing prospective volunteers to submit their information directly into Salesforce.

This approach leverages the existing Volunteers for Salesforce functionality, making it easy to capture and manage volunteer applications.

To ensure full compliance with Salesforce best practices for data security, the consultant should use Salesforce Health Check. Here’s why:

Salesforce Health Check:

This tool provides a comprehensive security assessment of your Salesforce org by measuring its settings against the Salesforce recommended baseline.

It evaluates critical security settings such as password policies, session settings, and other security configurations.

Health Check provides a score and recommendations to improve the overall security posture of the org, making it a crucial tool for maintaining data security compliance.

Salesforce Health Check Documentation

Salesforce Security Best Practices Guide

To predict the likelihood of a contact becoming a recurring donor, the consultant should implement Einstein for Nonprofits. Here's how:

Enable Einstein for Nonprofits:

Ensure that Einstein Analytics and Discovery are enabled in the Salesforce org.

Navigate to the Einstein for Nonprofits setup and configure the necessary settings.

Configure Prediction Models:

Use Einstein Prediction Builder to create a custom prediction model.

Define the criteria and data points that indicate a high likelihood of recurring donations, such as past donation behavior, engagement levels, and demographic information.

Train and Deploy the Model:

Train the prediction model using historical data.

Deploy the model to start predicting which contacts are likely to become recurring donors.

Utilize Predictions in Fundraising Strategies:

Fundraisers can use the predictions to prioritize outreach and engagement efforts.

Customize communication and engagement plans for high-potential recurring donors.

Einstein for Nonprofits leverages AI and machine learning to provide insights and predictive analytics, helping nonprofits make data-driven decisions to enhance donor engagement and fundraising efforts.

Salesforce Einstein for Nonprofits: Einstein for Nonprofits.

Salesforce Einstein Prediction Builder Guide: Prediction Builder.

For a large nonprofit organization functioning like a for-profit corporation and needing to manage Leads and track its Opportunity pipeline:

Salesforce Account Model without NPSP: This model is suitable as it aligns with for-profit business processes, focusing on managing business accounts, leads, and opportunities. The Household Account Model in NPSP is more suited for organizations managing individual donors, which is not applicable here.

Using the standard Salesforce Account Model allows the organization to leverage Salesforce’s CRM capabilities tailored for B2B interactions.

https://powerofus.force.com/s/article/PMM-Overview

https://trailhead.salesforce.com/en/content/learn/modules/program-management-with-nonprofit-cloud/manage-nonprofit-programs-with-salesforce?trail_id=manage-programs-with-nonprofit-cloud

To meet the reporting requirements of a new grant that expects services to be segmented according to location, the nonprofit should use the Program Cohort object. The Program Cohort object allows tracking and reporting of services provided in specific locations, making it possible to generate detailed reports that meet funder requirements.

Steps:

Configure the Program Management Module to include the necessary fields for tracking service locations within the Program Cohort object.

Ensure that all relevant data is accurately entered into the Program Cohort records, including location details.

Create custom reports and dashboards that segment services based on the location data stored in the Program Cohort object.

Regularly review and update the data to ensure accurate and up-to-date reporting for the funder.

When a nonprofit organization creates a custom Opportunity name for all organization donations, the consultant should discuss the following considerations:

Using the "Refresh Name" Action (B):

The organization should use the "Refresh Name" action to change existing Opportunities to the new naming convention. This action ensures that the custom naming convention is applied correctly.

Navigate to the Opportunity record.

Click on the "Refresh Name" button to update the Opportunity name according to the new naming convention.

Using the "Refresh All Opportunity Names" Button in Bulk Data Processes (C):

For bulk updates, the organization should use the "Refresh All Opportunity Names" button available in Bulk Data Processes.

Go to NPSP Settings.

Under Bulk Data Processes, find the "Refresh All Opportunity Names" button.

Click on it to update all existing Opportunities to the new naming convention in bulk.

These methods ensure that the custom naming convention is applied consistently across all existing Opportunity records, maintaining data integrity and consistency within the Salesforce org​​.

A common cause of the NPSP (Nonprofit Success Pack) upgrade failing when run in Production, despite no issues in the sandbox, is not having adequate test code coverage. This is essential for successful deployments in Salesforce environments.

Test Code Coverage:

Salesforce requires a minimum of 75% test code coverage for deploying Apex code to a production environment.

This means that automated tests must cover at least 75% of the codebase, ensuring that most functionalities are validated and reducing the risk of errors during deployment.

Sandbox vs. Production Differences:

Sandbox environments often have less data and different configurations compared to production, which might not fully mimic real-world scenarios.

In production, there could be additional triggers, validation rules, or workflows that are not present or not active in the sandbox.

Mitigating Upgrade Failures:

Ensure that all custom code, including Apex triggers, classes, and batch processes, has adequate test coverage.

Review and test all dependent packages and configurations in a full sandbox environment that closely replicates the production setup.

Additional Considerations:

Conduct a comprehensive review of all customizations and integrations.

Run the NPSP Health Check Tool and Salesforce Optimizer in sandbox before the actual upgrade to identify potential issues.

To present active volunteer sites on a map that should be visible without logging in, the nonprofit can use Tableau Public. Here’s why:

Tableau Public:

Tableau Public is a free platform that allows users to create and share interactive data visualizations online.

It supports publishing maps and other visualizations that can be accessed publicly without requiring login credentials.

This tool is ideal for sharing information like volunteer site locations with a broad audience.

Tableau Public Documentation

Salesforce and Tableau Integration Guide