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

To identify organizations that have donated to the nonprofit in some year prior to the current year but have not contributed in the current year, the NPSP SYBUNT (Some Year But Unfortunately Not This year) report can be customized. Here’s how to do it:

Navigate to the NPSP SYBUNT Report:

Go to the Reports tab.

Find and open the NPSP SYBUNT report template.

Customize the Date Range:

Click on the “Filters” pane.

Adjust the date range filters to include donations from the desired prior years and exclude the current year.

Modify Report Criteria:

Ensure the report is filtering by Account to get the organization-level data.

Add additional filters if necessary to refine the report (e.g., specific campaign or donation types).

Run the Report:

Save and run the report to get a list of organizations that have donated in previous years but not in the current year.

By customizing the date range on the NPSP SYBUNT report for Accounts, you can easily identify and target these lapsed donors for re-engagement campaigns.

"Using NPSP Reports" from Salesforce Help: NPSP Reports

"SYBUNT and LYBUNT Reports in NPSP" from Salesforce.org: SYBUNT and LYBUNT

https://powerofus.force.com/s/article/NPSP-Which-Version-Am-I-Using

When a consultant is unsure when a particular field was added to NPSP, they can find the NPSP version number for the field in the NPSP Data Dictionary. Here’s why:

NPSP Data Dictionary:

The NPSP Data Dictionary provides comprehensive details about all fields, objects, and components within the NPSP package.

It includes information on when fields were introduced, their data types, descriptions, and related objects, making it the best resource for tracking the history of specific fields.

Salesforce NPSP Data Dictionary Documentation

Salesforce Nonprofit Success Pack Release Notes

https://sites.google.com/a/cloud4good.com/salesforce-glossary/home/npsp-user-manual/chapter-4-entering-data/npsp-data-importer-tool

When migrating data from a legacy donor management database, the NPSP Data Importer is the recommended tool for loading donor contact information, donation history, and payment information into Salesforce. Here’s why:

NPSP Data Importer:

The NPSP Data Importer is specifically designed for nonprofits using the Nonprofit Success Pack (NPSP).

It supports importing multiple related records (Contacts, Accounts, Opportunities, Payments) in a single file, making it ideal for comprehensive data migration.

The tool provides mapping capabilities to ensure that fields in the import file are correctly mapped to Salesforce fields.

It includes features to handle common nonprofit data structures such as household accounts, affiliations, and recurring donations.

Using NPSP Data Importer minimizes the risk of data discrepancies and ensures that all related records are correctly created and linked.

Salesforce documentation on NPSP Data Importer: NPSP Data Importer

When using Marketing Cloud Connect and enabling tracking, the type of data available for reporting using Salesforce reports includes Email Studio Send details. Here’s why:

Marketing Cloud Connect:

Marketing Cloud Connect integrates Marketing Cloud with Salesforce, enabling data synchronization and reporting.

This integration allows Salesforce to pull tracking data from various Marketing Cloud modules into Salesforce reports.

Email Studio Send Details:

Email Studio Send details include data such as email opens, clicks, bounces, and other email performance metrics.

This data is critical for understanding the engagement and effectiveness of email campaigns, and it is available for reporting within Salesforce.

Salesforce Marketing Cloud Connect Documentation

Salesforce Email Studio Reporting Guide

To ensure that the status for a Campaign Member on a fundraising campaign is automatically updated when a donation is received from that Contact, the Automatic Campaign Member Management feature in NPSP can be used. Here’s how to enable and configure it:

Navigate to NPSP Settings:

Go to Setup.

In the Quick Find box, type "NPSP Settings" and select it.

Enable Automatic Campaign Member Management:

In the NPSP Settings, navigate to "Donations".

Find the "Automatic Campaign Member Management" section.

Enable this feature by checking the corresponding box.

Configure the Settings:

Define the criteria for when and how Campaign Member statuses should be updated. For example, you can specify that the status should change to "Responded" when a donation is received.

Save Settings:

Save the changes to activate the automatic updates.

This setup ensures that Campaign Member statuses are updated automatically based on the criteria defined, reducing manual effort and improving accuracy.

"Automatic Campaign Member Management" from Salesforce Help: Automatic Campaign Member Management

"NPSP Settings Overview" from Salesforce.org: NPSP Settings

https://powerofus.force.com/s/article/NPSP-Configure-Gift-Entry

Gift Entry Templates in NPSP allow for the configuration of different batch data input settings for various types of donations. This feature ensures consistency and efficiency in processing different donation batches.

Steps:

Access the Gift Entry Templates in NPSP.

Create a new template for each type of donation batch that needs to be processed.

Configure the fields and layout for each template to match the specific data requirements of each donation type.

Save and publish the templates.

Use the templates when processing donation batches to ensure consistent data entry and processing.

For a volunteer manager to search for volunteers with specific skills and availability using Volunteers for Salesforce, the following steps can be advised:

Use the Find Volunteers Tab:

Click on the "Find Volunteers" tab in Salesforce.

Filter Criteria:

Fill in the Volunteer Status, Volunteer Availability, and Volunteer Skills tabs with the required values:

Volunteer Status: Select the appropriate status (e.g., Active, Available).

Volunteer Availability: Specify the dates and times the volunteer is available.

Volunteer Skills: Include landscaping or other required skills.

Hit Search:

Click on the "Search" button to retrieve the list of volunteers matching the criteria.

Review and Contact Volunteers:

Review the list of volunteers who meet the criteria.

Use the contact information provided to reach out to the suitable volunteers for the specific task.

This method leverages the built-in search functionalities in Volunteers for Salesforce, providing an efficient way to find and manage volunteers based on specific needs.

Volunteers for Salesforce Documentation: Finding and Managing Volunteers

Salesforce Trailhead: Volunteers for Salesforce

Changes to Engagement Plan Templates in Salesforce only affect newly created Engagement Plans. Here’s why:

Template Changes Application:

When an Engagement Plan Template is modified, the changes are not retroactively applied to existing Engagement Plans. Only new plans created after the modification will reflect the changes.

Create New Engagement Plans:

For the development manager to see the changes, new Engagement Plans need to be created using the updated template. Existing plans will retain the configuration they had at the time of creation.

Communicate Changes:

Inform relevant stakeholders about this behavior to manage expectations and plan accordingly. Consider cloning existing Engagement Plans if updates are necessary, applying the new template configurations.

Review Documentation:

Refer to Salesforce documentation on Engagement Plans for detailed information on how templates and plan instances work.

When migrating a large volume of contacts, organizations, and address records into NPSP, it is essential to consider the following:

Complexity with the Address Object:

Using the Address object to track addresses can introduce complexity, especially if multiple addresses per contact or organization need to be managed. This complexity arises from the need to ensure all address records are correctly linked and maintained.

Impact on Data Storage:

Migrating all historical address information can significantly impact system data storage. Salesforce has storage limits, and large volumes of data can quickly consume available storage. It is important to plan for data storage needs and consider archiving or summarizing historical data to manage storage usage effectively.

Steps for Migration:

Data Preparation:

Clean and standardize the data before migration to ensure consistency.

Identify and remove duplicates to avoid data redundancy.

Data Mapping:

Map the fields from the legacy system to the corresponding fields in NPSP, including custom fields if necessary.

Data Import Tools:

Use Salesforce Data Loader or the NPSP Data Importer for the migration process.

Import data in batches, starting with Accounts, followed by Contacts, and then address information.

Testing and Validation:

Test the migration in a sandbox environment to identify and resolve any issues.

Validate the imported data to ensure accuracy and completeness.

"Data Import Strategies for Nonprofits" from Salesforce Help: Data Import Strategies

"Address Management in NPSP" from Salesforce.org: Address Management

When a nonprofit organization is informed of a deceased donor and wants to ensure that the donor no longer appears on any mailing lists, the appropriate action is to select the "Deceased" field on the donor's contact record. Here’s how to do it:

Navigate to the Contact Record:

Go to the Contacts tab in Salesforce.

Search for the donor’s contact record and open it.

Select the Deceased Field:

Locate the "Deceased" checkbox on the contact record.

Check the box to mark the contact as deceased.

Additional Actions:

Ensure that any automated processes or workflows related to email and mailing lists exclude contacts marked as deceased.

Update any relevant lists or segments to remove the deceased donor from future communications.

Implications of Marking a Contact as Deceased:

The contact will no longer be included in email or direct mail campaigns.

The contact record is retained in Salesforce for historical and reporting purposes, preserving donation history and other relevant information.

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

To exclude gala attendees from the report that identifies individual donors who have yet to make a gift toward the Annual Fund Campaign this year, a cross filter should be added to the report. Cross filters allow you to filter records based on related objects, such as excluding contacts who are campaign members of the gala event.

Steps:

Go to Reports and create a new report or edit an existing report on donors.

Add a cross filter to the report by clicking on the "Filters" pane and selecting "Add Cross Filter."

Set the cross filter to exclude Contacts who are Campaign Members of the specific gala campaign.

Save and run the report to ensure it correctly excludes gala attendees.

To configure the view of Contact records to avoid visually identifying a subset of clients, the consultant should set the component visibility for the Client Photo Component:

Navigate to Lightning App Builder:

In Salesforce Setup, go to "Lightning App Builder."

Select the Lightning Record Page for Contacts that you wish to modify.

Configure Component Visibility:

Locate the Client Photo Component on the page.

Click on the component to open its properties.

Set Component Visibility Rules:

In the properties panel, set visibility rules for the Client Photo Component.

Define criteria to control when the component is visible. For instance, you can use field values or user profiles to determine visibility.

Save and activate the changes.

Test and Deploy:

Test the Lightning Record Page to ensure the visibility rules work as expected.

Deploy the updated page to users.

By setting the component visibility for the Client Photo Component, you can ensure that the subset of clients is not visually identified, meeting the nonprofit's requirements.

Before converting from Legacy Recurring Donations to Enhanced Recurring Donations, nonprofits should consider several factors to ensure a smooth transition. Enhanced Recurring Donations offer improved functionality but may introduce compatibility issues with existing integrations. Additionally, once the switch is made, reverting to Legacy Recurring Donations is not supported, which means careful planning and testing are essential.

Steps:

Review all existing integrations to ensure compatibility with Enhanced Recurring Donations.

Conduct thorough testing in a sandbox environment to identify any potential issues.

Inform stakeholders that reverting to Legacy Recurring Donations is not supported once the switch is made.

Plan for a phased rollout and provide training to users on the new features and processes.

When troubleshooting the issue of Recurring Donation Opportunities having close dates at the end of the month instead of the 15th, the consultant should check if the "Always use last day of the month" field is selected. This field setting overrides other close date settings and defaults the close date to the last day of the month.

Log in to Salesforce: Access the Salesforce org where NPSP is installed.

Navigate to NPSP Settings: Go to the App Launcher, search for "NPSP Settings", and select it.

Find Recurring Donations Settings:

In NPSP Settings, expand the "Donations" section.

Click on "Recurring Donations".

Check the "Always use last day of the month" Field:

Locate the "Always use last day of the month" setting.

Verify whether this checkbox is selected.

If selected, uncheck this option if you want the close date to follow the Day of the Month picklist value.

Save the Settings: Save any changes made and verify that new Recurring Donations reflect the correct close date.

By ensuring this field is not selected, the system will correctly use the 15th of the month as specified in the Day of the Month picklist.

When migrating a large volume of donation and payment data into an NPSP org, the consultant should discuss the following considerations with the nonprofit organization:

Data Storage Limits:

Salesforce has data storage limits based on the type and edition of the Salesforce instance.

It is important to calculate the volume of data being imported and ensure it does not exceed the available storage.

If necessary, consider purchasing additional data storage or archiving old records to free up space.

Data Skew:

Data skew occurs when a large number of child records are associated with a single parent record.

This can impact performance and cause issues with sharing rules and data visibility.

Plan the data import to distribute records evenly and avoid creating data skew, particularly with high-volume objects like Contacts and Accounts.

By addressing these considerations, the nonprofit can ensure a smooth and efficient data migration process while maintaining optimal system performance and compliance with Salesforce limits.

Salesforce Documentation: Data Storage Allocations

Salesforce NPSP Documentation: Data Import Best Practices

For suggesting new features in NPSP, the recommended resource is:

Power of Us Hub: This is a community platform specifically for Salesforce.org customers. It includes forums, idea exchanges, and collaboration spaces where nonprofit users can suggest and discuss new features for NPSP.

The Power of Us Hub is the central place for engaging with the Salesforce nonprofit community and influencing future product development.

When the consultant encounters API call limit errors after switching the integration from a sandbox to a production environment, the likely explanation is:

Different API Call Limits for Sandbox and Production Environments:

Salesforce environments have different API call limits based on the type of environment and the organization's Salesforce edition. Sandbox environments often have higher API call limits for testing purposes, while production environments have stricter limits to ensure performance and reliability.

If the Check/Reference Number field is not visible in the report builder, the consultant should check if there is a custom field named "Check/Reference Number" on the Payments object. Here’s how to proceed:

Verify Custom Fields on Payments Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Look for a custom field named "Check/Reference Number".

Ensure Field is Included in Report Type:

Go to the Report Builder.

Verify that the report type being used includes the Payments object.

If the report type does not include Payments, create or use a report type that does.

Add Field to Report Layout:

In the Report Builder, ensure the "Check/Reference Number" field is added to the report layout.

Drag and drop the field into the columns of your report.

By ensuring that the custom field is present on the Payments object and included in the report type, the development associate can successfully add the Check/Reference Number to their report.

Salesforce Documentation: Custom Fields

Salesforce Trailhead: Create Reports with the Report Builder