Important Salesforce Certified Nonprofit Cloud Consultant (NP-Con-102) Exam Questions

Answer: A

Explanation:

To ensure that a deceased donor no longer appears on any mailing lists, the nonprofit organization should 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 and open the donor's contact record.

Select the Deceased Field:

Locate the 'Deceased' checkbox on the contact record.

Check the box to mark the contact as deceased.

Verify Exclusion from Mailing Lists:

Ensure that automated workflows and processes exclude contacts marked as deceased from email and mailing lists.

Review and update any relevant segments or mailing lists to remove the deceased donor.

This action preserves the donor's history in Salesforce while ensuring they are no longer included in future communications.

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

Answer: B

Explanation:

When encountering governor limit errors on a particular job in NPSP, the consultant should decrease the batch size for that job. Here's why:

Batch Size:

Salesforce has strict governor limits to ensure efficient resource usage. When a batch job hits these limits, it often indicates that the batch size is too large.

Decreasing the batch size reduces the number of records processed in each batch execution, thereby minimizing the chances of hitting governor limits.

This approach helps in completing the job successfully without exceeding platform limits.

Salesforce Batch Apex Documentation

Salesforce Governor Limits Guide

These solutions provide precise and effective steps to address common issues and configuration needs within the Salesforce Nonprofit Cloud environment.

Answer: C

Explanation:

https://powerofus.force.com/s/article/NPSP-Merging-Contacts

When using the NPSP Contact Merge functionality, any empty Household Accounts that do not have associated Contacts or Opportunities are automatically deleted. This is likely the cause of the reduction in the number of household accounts noticed by the system administrator.

Steps to Verify:

Check Merge Settings:

Review the settings and configuration of the NPSP Contact Merge process to understand its behavior regarding empty Household Accounts.

Review Audit Logs:

Check the Salesforce audit logs to see the details of the merge operations and confirm that empty Household Accounts were deleted.

Restore if Necessary:

If the deletion of empty Household Accounts was unintended, use data recovery options to restore any necessary records.

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Merge Duplicate Records in Nonprofit Success Pack

Answer: B, C

Explanation:

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

Answer: A

Explanation:

To configure NPSP to send Apex error messages to a specific system admin, you should follow these steps:

Navigate to NPSP Settings:

Go to the App Launcher in Salesforce.

Type 'NPSP Settings' in the search bar and select it.

Access System Tools:

In the NPSP Settings, locate the 'System Tools' section in the left-hand sidebar.

Configure Error Notifications:

Under System Tools, select 'Error Notifications.'

Here, you will find options to configure who receives error notifications.

Set the Specific Admin:

Find the field where you can specify the user to receive error notifications.

Enter the username or search for the specific admin user you want to receive these notifications.

Save the settings.

By following these steps, you ensure that all Apex error messages are sent only to the specified system admin, effectively managing error notifications within NPSP.

Nonprofit Success Pack (NPSP) Documentation: System Tools > Error Notifications section.

Salesforce documentation on user management and notification settings.