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

Salesforce Nonprofit Cloud for Fundraising is organized into several distinct Lightning Apps, each tailored to a specific fundraising persona or business process. For consultants, understanding which app supports which business function is essential for user enablement.

Donor Engagement: This app is the hub for mass-market fundraising. It is designed for team members who manage large-scale outreach, direct mail, digital campaigns, and high-volume donor acquisition. It includes features for Campaign Management, Source Codes, and segmenting large lists of donors for automated outreach. This app focuses on "one-to-many" relationships where the goal is efficiency and broad engagement.

Philanthropy & Partnerships: In contrast, this app is designed for "high-touch" or major gift fundraising. It focuses on "one-to-one" relationship management, tracking major donors, foundation partners, and corporate sponsors. It highlights tools like the Donor Profile, Wealth Screening data, and moves management stages.

Fundraising Strategy: This app (and its associated dashboards) is intended for leadership and data analysts. It provides high-level insights into fundraising performance, RFM (Recency, Frequency, Monetary) scoring trends, and overall revenue health, rather than day-to-day campaign execution.

By assigning the Donor Engagement app to the marketing and direct response teams, a consultant ensures they have immediate access to the Campaigns, Outreach Source Codes, and segments they need to run mass-market appeals effectively without being distracted by the specialized major gift tools found in the Philanthropy app.

When an organization uses a Private sharing model (Organ11ization-Wide Defaults), users can only see records they own or records owned by their subordinates in the role hierarchy. To open up visibility to a "subset" of records for a "selected" group of staff, the consultant must use a Sharing Rule.

Implementing the Solution:

Criteria-Based Logic: Since only a subset of Service Deliveries (e.g., those related to "Mental Health" or a specific "Program") needs to be shared, the consultant should use a Criteria-Based Sharing Rule.

Definition: The rule might state: "Share Service Delivery records where Program Name EQUALS 'Youth Outreach' with the 'Program Staff' Public Group."

Access Level: The consultant defines the level of access (Read Only or Read/Write).

Public Groups: The "selected staff" should be added to a Public Group. The sharing rule then targets this group.

Why other options are incorrect:

Public Read/Write (Option B): This would expose all records to all users, violating the nonprofit's strict security requirements.

Permission Sets / Profiles (Options C & D): These grant the functional ability to use the object (CRUD), but in a Private sharing model, they do not grant access to specific records owned by others. Sharing rules are the primary tool for record-level visibility in Salesforce.

User stories are the "building blocks" of an Agile implementation. A well-written user story follows the format: "As a [persona], I want to [action], so that [value/benefit]." To ensure a stalled project gets back on track, two critical components are alignment and prioritization.

Vision Alignment (B): Every story must have a purpose that contributes to the overall Implementation Vision. If a nonprofit’s vision is "Improving Donor Retention," but a user story is created for "Automating Facilities Management," the consultant must evaluate if that story is a distraction. Aligning stories to the vision ensures the consultant builds what the organization actually needs to succeed, rather than just what users want.

Priority (C): In any implementation, there is limited time and budget. Assigning a priority (often using the MoSCoW method: Must have, Should have, Could have, Won't have) is essential. It allows the consultant and the nonprofit to focus on mission-critical features first, ensuring that if the project runs out of resources, the most valuable parts of the system are already delivered.

Why other options are less critical:

Configuration Instructions (Option A): This is a mistake. User stories describe the requirement (the "What"), while technical documentation describes the solution (the "How"). Putting configuration steps in a user story makes it rigid and difficult for a developer to suggest better technical alternatives.

Epics (Option D): While epics are useful for grouping stories, they are a structural tool for project management rather than a "component" of the story's internal logic or value definition. Alignment and Priority are what drive project success.

In NPSP, the most efficient way to link a donation to a donor's campaign participation is through Automatic Campaign Member Management.31

How the Feature Works:32

The Link:33 When an Opportunity (donation) is created, it has a Primary Campaign Source field.

The Automation: If Automatic Campaign Member Management is enabled in NPSP Settings, the system automatically looks at the Primary Contact on the donation and checks if they are already a Campaign Member of that campaign.

Status Update: If they are already a member, the system can automatically update their Member Status (e.g., from "Sent" to "Responded").

Creation: If they are not yet a member, the system can automatically create a new Campaign Member record for that donor with a "Responded" status.

Why other options are incorrect:

Customizable Rollups (Option B): These summarize financial totals but do not handle the "Status" or "Response" logic on a campaign.

Customizable Campaign Influence (Option C): This is a Sales Cloud feature used to attribute "Influence" across multiple campaigns for a single deal. While relevant to high-level ROI, it is not the primary mechanism for simply recording that a donor "responded" to a specific direct mail appeal.

Sales Process (Option D): This defines the "Stages" an Opportunity goes through (Pledged, Won, etc.) and has no role in campaign response tracking.

In Nonprofit Cloud Case Management, a Care Plan is the central roadmap for a client's journey toward a specific outcome. While Care Plan Templates provide a standardized starting point, the philosophy of person-centered care requires that these plans be customizable to the unique circumstances of each participant.

A Care Plan is structurally composed of two primary "actionable" building blocks:

Goal Assignments: These represent the milestones the client is working toward (e.g., "Secure Stable Housing" or "Complete GED"). While a template might include five standard goals, a caseworker can manually add a sixth Goal Assignment that is unique to that client’s specific barriers.

Benefit Assignments: These are the services or resources provided to help the client achieve their goals (e.g., "Rental Assistance" or "Weekly Tutoring"). A caseworker can manually link additional Benefits to a Care Plan to ensure the participant has the specific support they need.

Step-by-Step Customization Workflow:

Template Application: The caseworker begins by applying a standard template, which populates the Care Plan with a set of pre-defined goal and benefit assignments.

Assessment Review: After a Dynamic Assessment, the caseworker identifies an unmet need.

Manual Entry: Within the Care Plan interface, the caseworker clicks "New" on the Goal Assignment related list to create a custom goal. They then do the same for Benefit Assignments to link the client to a specific service.

Linking: The caseworker can then link the manual Benefit Assignment to the manual Goal Assignment to show exactly how that service contributes to the client's progress.

Option B is incorrect because Programs and Program Enrollments are the broader containers that a client is part of. While a Care Plan exists within the context of an enrollment, you don't "add an enrollment" to a plan; rather, the plan is a subset of the enrollment. Option A refers to compliance and document tracking, which are managed via Action Plans, not the core clinical/social service logic of the Care Plan itself.

While Duplicate Rules and Matching Rules are essential for preventing new duplicates from being created, they do not help with a database that already contains existing duplicates (which is common after large direct mail imports).12

The Solution for "Auto13mating the Search":

On Unlimited Edition, Salesforce provides a feature called Duplicate Jobs.

Scanning the Database: Unlike rules that fire during a save, a Duplicate Job runs a scan across the entire existing database (or a specific segment) to find existing duplicate records based on your Matching Rules.

Reporting: Once the job completes, it generates a list of "Duplicate Record Sets." This allows the nonprofit's data integrity team to review and merge records in bulk.

Use Case: For a direct mail organization, running a Duplicate Job before a large mailing ensures they aren't wasting money by sending two identical letters to the same household.

Why other options are incorrect:

Duplicate/Matching Rules (Options A & C): These act as "gatekeepers" during data entry. They find duplicates only when a record is created or edited; they do not proactively "search" the existing database.

Scheduled Apex (Option D): This is a custom coding solution. A consultant should always recommend native, declarative features like Duplicate Jobs before suggesting custom code.