Salesforce Nonprofit Cloud Consultant Exam Questions

When setting up Volunteers for Salesforce in an international context, it's important to ensure that volunteer jobs and shifts reflect the local time zones accurately. Here's how to configure this:

Navigate to Volunteers for Salesforce Settings:

Go to Setup.

Type 'Volunteers for Salesforce' in the Quick Find box and select it.

Configure Volunteer Jobs:

Create Volunteer Jobs for each country.

For each job, set the 'Website Time Zone' field to the local time zone where the job will take place.

Adjust Volunteer Shift Times:

When creating volunteer shifts, ensure the start and end times are set according to the local time zone.

Update Website Information:

Inform volunteers about the time zone settings on the volunteer signup pages if necessary.

'Volunteers for Salesforce Setup Guide' from Salesforce Help: Volunteers for Salesforce

'Managing Volunteer Shifts and Jobs' from Salesforce.org: Volunteer Management

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 allow case managers to create and edit service delivery records in the Program Management Module (PMM), you should assign the appropriate permissions through Permission Sets. Permission Sets provide a way to grant specific permissions to users without changing their profiles, making it easier to manage access to certain functionalities.

Steps:

Create a Permission Set:

Navigate to Setup -> Permission Sets.

Click 'New' to create a new permission set.

Grant Permissions:

In the new permission set, go to Object Settings.

Find and select 'Service Deliveries.'

Grant 'Create' and 'Edit' permissions.

Assign the Permission Set:

Assign the newly created permission set to the case managers who need access to create and edit service delivery records.

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Permission Sets

Both Marketing Cloud and Pardot offer the capability to segment data and functionality using business units. This is particularly useful for large nonprofits with multiple chapters operating under a single brand but needing customized roles, processes, and messaging.

Marketing Cloud:

Business Units: Allows organizations to separate data, user permissions, and content based on different parts of the organization, such as chapters or departments. Each business unit can have its own data and customizations, enabling localized marketing while maintaining centralized control.

Pardot:

Business Units: Pardot Business Units enable marketing teams to partition data and customize marketing efforts for different segments within the organization. This ensures that each chapter can tailor its marketing automation processes to its specific needs while maintaining brand consistency.

Salesforce Marketing Cloud Documentation

Salesforce Pardot Documentation

Salesforce Trailhead: Get Started with Marketing Cloud Business Units

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.

Salesforce Account Model Documentation

Salesforce Trailhead: Managing Leads and Opportunities

https://trailhead.salesforce.com/en/content/learn/modules/search_solution_basics/search_solution_basics_optimizing

To improve search performance when migrating a large volume of donation data into the Nonprofit Success Pack (NPSP) for a nonprofit, the consultant should consider implementing Skinny Tables and Custom Index. Here is a detailed explanation:

Skinny Tables:

Skinny tables are a performance optimization technique in Salesforce used to improve the performance of read-only operations.

They are highly effective in environments with large volumes of data, such as the scenario described with 20 years of donation data and over 200,000 donations each year.

A skinny table contains frequently accessed fields and can significantly reduce query time.

Skinny tables are maintained by Salesforce and do not require changes to the custom object schema or existing queries.

They are particularly useful for scenarios involving complex reports and list views.

Custom Index:

Custom indexes enhance the performance of search queries in Salesforce.

Creating custom indexes on fields that are frequently used in search filters and conditions can drastically improve search performance.

Salesforce allows up to 25 custom indexes per object, which can be leveraged to optimize searches on key fields such as donor names, donation dates, and amounts.

Custom indexes should be applied to fields involved in frequently used WHERE clauses in SOQL queries.

Salesforce documentation on Skinny Tables: Skinny Tables

Salesforce documentation on Custom Index: Custom Index