Free Salesforce Nonprofit-Cloud-Consultant Practice Exam with Questions & Answers | Set: 7

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.

References:

Salesforce Account Model Documentation

Salesforce Trailhead: Managing Leads and Opportunities

To ensure that donors receive credit for new donations, the automatic Opportunity Contact Role hard credit value should be configured in NPSP Settings. Here’s how to do it:

Navigate to NPSP Settings:

Go to the App Launcher and search for "NPSP Settings".

Access Donations Settings:

Under NPSP Settings, select "Donations".

Click on "Opportunity Contact Roles".

Configure Default Contact Role:

Set the default Contact Role for Opportunities to ensure that the primary donor is automatically assigned the correct role.

This role typically is "Primary Donor" or "Donor".

Verify and Save:

Ensure that the configuration is correct and save the changes.

This setup ensures that when new donations are imported or entered, the primary donor receives the appropriate hard credit automatically, maintaining accurate donor credit records.

References:

Salesforce NPSP Documentation: Opportunity Contact Roles

Salesforce Trailhead: Manage Donations in NPSP

To track nested campaigns effectively, Salesforce Campaign Hierarchies can be utilized. Here are the steps to set this up:

Create Parent Campaign:

Create the top-level parent Campaign called "Friends of the Organization".

Create Sub-Campaigns:

Create sub-campaigns under the parent campaign for each hierarchical level: FY19, Capital Campaign, Annual Fund, Digital Donations, and Mobile.

Link each sub-campaign to its parent campaign using the Parent Campaign lookup field.

Configure Campaign Hierarchy Settings:

Ensure the Campaign Hierarchy settings are configured to allow for the desired depth of nested campaigns.

Track Campaign Performance:

Use Campaign Hierarchy reports to track the performance of each campaign within the hierarchy.

Analyze metrics such as total donations, engagement, and conversion rates at each level.

By creating a structured Campaign Hierarchy, the nonprofit can effectively track and manage complex campaign structures, gaining insights into performance at each level of the hierarchy.

References:

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

"Managing Campaigns in NPSP" from Salesforce.org: Campaign Management

A Salesforce-recommended governance structure for nonprofit organizations ensures the implementation runs smoothly and effectively. It typically includes the following elements:

Release Management: This ensures that changes are systematically planned, tested, and deployed. It involves managing how new features and updates are rolled out to avoid disruption and ensure smooth transitions.

Rules of Engagement: These define how different stakeholders will interact with the system and with each other. It includes protocols and guidelines for communication, decision-making, and responsibilities.

Center of Excellence (CoE): This is a dedicated team or a hub of experts that provides leadership, best practices, research, support, and training. A CoE helps ensure that the organization is leveraging Salesforce effectively and efficiently.

References:

Salesforce Nonprofit Cloud Implementation Guide

Salesforce Trailhead: Governance Framework

In the Nonprofit Success Pack (NPSP), donations can be credited in two ways: hard credits and soft credits. Hard credits reflect direct donations, while soft credits are used to acknowledge indirect contributions, such as when a donor's employer matches a donation.

Hard Credits:

Hard credits represent the actual donor who made the donation.

In this scenario, the employer who matches the donation will receive a hard credit for the matched amount.

Soft Credits:

Soft credits are used to recognize individuals or entities who influenced or facilitated the donation but are not the direct donors.

The donor will receive a soft credit for the amount matched by their employer.

Scenario Application:

The donor made a donation of $500. This is a hard credit for the donor.

The employer matches this donation with another $500. The employer receives a hard credit for this matched amount.

The donor is acknowledged for facilitating the matched gift, thus receiving a soft credit of $500.

Implementation in NPSP:

To implement this, configure the Opportunity Contact Role to automatically assign soft credits to related contacts, such as employers matching donations.

Use the NPSP Settings to ensure that soft credit roles are correctly assigned and tracked.

References:

CertGod Nonprofit Cloud Consultant study guide: "The donor has a soft credit of $500 and the employer has a hard credit of $500"​​.

To ensure that all child Opportunities contain the unique reference number from the Recurring Donation object and to prevent modifications after creation, follow these steps:

Create a Custom Text Field on the Opportunity Object:

Navigate to Setup.

In the Object Manager, select Opportunity.

Click on Fields & Relationships.

Create a new Text field (e.g., "Recurring Donation Reference Number").

Use NPSP Recurring Donation Custom Field Mappings:

Navigate to NPSP Settings.

Under "Donations", select "Recurring Donations".

Go to "Field Mappings".

Map the custom text field on the Recurring Donation object to the custom text field on the Opportunity object.

Ensure Field-Level Security:

Set the field-level security for the custom fields to ensure that they are only editable by the required profiles and read-only for others.

By following these steps, the unique reference number will be automatically populated and synchronized from the Recurring Donation object to all child Opportunities, and it will remain consistent for reconciliation purposes.

References:

Salesforce NPSP Documentation: Custom Field Mapping

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Settings

Under the Household Account model in Salesforce NPSP, a Contact's Account represents where they live, essentially their Household. The Primary Affiliation, on the other hand, indicates where they work or are affiliated professionally.

Household Account:

This is used to group individuals living at the same address into a single account.

All contacts associated with a Household share the same Account record, representing their home address and family unit.

Primary Affiliation:

This is a special relationship field in NPSP that links a Contact to an Organization or company where they work or have a significant relationship.

It allows nonprofits to track where their constituents are employed or connected professionally, separate from their residential information.

References:

CertGod Nonprofit Cloud Consultant Guide

Creating a Campaign hierarchy is the most effective way to track funding for projects and monitor year-over-year goals in Salesforce. Campaign hierarchies allow for organizing campaigns in a structured manner, making it easy to roll up data and track progress across different levels. Here’s how to set this up:

Create Parent Campaigns for Years:

For each year, create a parent campaign. For example, "2023 Projects" and "2024 Projects".

Create Sub-Campaigns for Projects:

Under each yearly parent campaign, create sub-campaigns for each project. For instance, "2023 Projects" can have sub-campaigns like "Project A", "Project B", etc.

Link Sub-Campaigns to Parent Campaigns:

Use the Parent Campaign lookup field to link each project campaign to its respective year campaign. This establishes the hierarchy.

Track Goals and Progress:

Use Campaign fields to set goals and track actual amounts. Fields like "Campaign Member Status", "Amount Raised", and custom fields can be used to track the funding and progress.

Use roll-up summary fields to aggregate data from sub-campaigns to parent campaigns.

Reporting and Dashboards:

Create reports and dashboards to monitor the progress of each project and year-over-year comparisons. Use the Campaign Hierarchy feature in reports to show aggregated data.

By setting up a Campaign hierarchy, the foundation can easily track the funding, manage goals, and compare progress year-over-year.

References:

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

"Managing Campaigns in NPSP" from Salesforce.org: Managing Campaigns

Lightning Flow in Salesforce is a powerful declarative tool that allows users to automate business processes and create guided visual experiences. This tool is specifically designed for process automation and can help nonprofits streamline routine activities without requiring any coding knowledge. Here are the steps to use Lightning Flow for automating processes:

Access Lightning Flow Builder:

Navigate to Setup.

In the Quick Find box, type "Flows" and select "Flows" under Process Automation.

Create a New Flow:

Click "New Flow".

Choose the type of flow you want to create. For automating routine activities, "Screen Flow" or "Scheduled-Triggered Flow" might be appropriate.

Design the Flow:

Use the drag-and-drop interface to add elements like screens, decisions, assignments, and loops.

Configure each element to define the process logic.

Set Entry Conditions and Actions:

Define the trigger for the flow (e.g., record creation, updates, scheduled times).

Specify the actions to be taken (e.g., create/update records, send emails, call Apex classes).

Test the Flow:

Before activating the flow, use the Debug mode to test and ensure it works as expected.

Activate the Flow:

Once tested, activate the flow so it starts running based on the defined conditions.

References:

"Get Started with Automation Tools" from Salesforce Help: Salesforce Automation

"Salesforce Flow for Nonprofits" from Salesforce.org: Salesforce.org Guide

To avoid manually entering information twice and ensure it appears on both the Opportunity record and the Payment record, follow these steps:

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to "Donations" and select "Payment Mappings".

Create mappings to ensure that relevant fields from the Opportunity record are automatically populated in the Payment record.

Create Custom Fields on the Payment Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Create custom fields that correspond to the Opportunity fields you want to map.

Ensure the field types match those on the Opportunity object to facilitate accurate data transfer.

These steps automate the data transfer between Opportunities and Payments, reducing manual entry and ensuring consistency across records.

References:

Salesforce NPSP Documentation: Payment Mappings

Salesforce Trailhead: Custom Fields