NP-Con-102 Certification Exam Guide + Practice Questions Updated 2026

Explanation:
For Major Gift Officers (MGOs), efficiency is driven by the ability to prioritize and segment their donor portfolio. In the modern Nonprofit Cloud, the feature designed specifically for this high-volume, high-priority organization is Actionable Segmentation and the resulting Actionable Lists.
An Actionable List is more than just a standard list view or report; it is a dynamic work queue that allows fundraisers to group prospects based on specific data points, such as Prospect Status, Wealth Tier, or Last Gift Date.
How a Consultant Implements Actionable Lists:
Define the Dataset: The consultant first identifies the criteria using Actionable Segmentation. For major gift prospects, this might involve filtering Person Accounts who have a "Qualified" prospect status and a high net worth indicator on their Contact Profile.
Create the List: Once the segment is defined, it is published as an Actionable List.
Assign and Engage: MGOs can then access this list from their Donor Engagement or Philanthropy & Partnerships app. The list provides an optimized view where the officer can see key details and immediately trigger actions, such as making a phone call, sending an email, or assigning an Action Plan
.
Real-Time Status Tracking: As the officer engages with a prospect, they can update the status directly within the list view. This allows the organization to track the "Movement" of a prospect through the solicitation pipeline in real time.
While Contact Profiles (Option C) provide the underlying data (wealth and personal attributes), and Action Plans (Option B) provide the tasks once the prospect is engaged, the Actionable List is the foundational "organizing" feature that allows the officer to manage their entire portfolio effectively. It ensures that the "most promising relationships" are always at the top of the officer's daily priority list.

Explanation:
Tracking the "Grant Seeking" process in NPSP requires a specific mapping of business requirements to the NPSP data model. Unlike "outbound" grantmaking, "inbound" grant seeking uses the Opportunity object as the primary record for each grant proposal.
Mapping the Lifecycle:
Applications & Reporting Deadlines (Deliverables): In NPSP, the Deliverable object is specifically designed to track milestones associated with a grant Opportunity. An "Application Submission" is a deliverable (the first milestone), and "Mid-Year Report" or "Final Report" are subsequent deliverables with specific due dates. This allows the development director to see a calendar of all upcoming grant requirements.
Payments (Opportunities with Payments): While the Opportunity tracks the total amount awarded, the Payment object in NPSP tracks the actual cash coming in. Since grants are often paid in multiple installments (multi-year grants), using the related Payments list is the standard way to reconcile the total award against what has actually been deposited in the bank.
Actions (Activities): Standard Salesforce Activities (Tasks and Events) are used to track the day-to-day engagement steps, such as "Draft Narrative," "Call Program Officer," or "Review Budget." These are the "internal" actions assigned to staff members.
Why other options are incorrect:
Option A: Recurring Donations are for open-ended, sustaining gifts (like monthly donors), not for specific fixed-amount grant awards with a set payment schedule.
Option C: Using Activities for reporting deadlines is a poor practice because activities are easily deleted or closed without the formal tracking and field-level detail (like "Grantee Requirements") that the Deliverable object provides.

Explanation:
In Nonprofit Cloud, access to core functionality is governed by specific industry-aligned permission sets. If Case Managers are unable to see Program and Benefit records, it is typically a matter of missing object-level and feature-level permissions.
The Advanced Program Management permission set is a critical requirement for users who need to interact with the full program lifecycle.
Permissions included in Advanced Program Management:
Object Access: It grants Read, Create, Edit, and Delete access (depending on the specific assignment) to the Program, Benefit, Benefit Type, and Benefit Schedule objects.
Functional Access: It allows users to manage Program Enrollments and track Benefit Disbursements.
Visibility: Without this permission set (or a Permission Set Group containing it), the objects remain hidden from the user's navigation bar and global search, even if the records are marked as "Active."
Step-by-Step Resolution:
● The Admin should navigate to Setup > Users.
● Select the Case Manager users.
● Click Permission Set Assignments > Edit Assignments.
● Add Advanced Program Management to the assigned list.
Note: If the organization wants to limit Case Managers to "Read-Only," they would use this permission set in conjunction with a Muting Permission Set within a Permission Set Group.
Why other options are incorrect:
Outcome Management (Option A): This grants access to impact tracking (Outcomes, Indicator Definitions) but does not provide the primary access to the Program and Benefit service delivery objects.
Status Marking (Option C): While a record should be active for operational use, "Active" status on a record does not override Salesforce security. If the user doesn't have object-level permissions via a permission set, they cannot see the record regardless of its status.

Explanation:
In Nonprofit Cloud for Grantmaking, the "Reviewer" persona (often a board member or external expert) needs a specialized interface to look at submitted data without accidentally changing it.
Salesforce provides a specific Lightning component in the Grantmaking Experience Cloud template called Form Review.
How the Form Review Component Works:
Read-Only Presentation: This component is designed to render the data captured via the Discovery Framework (the application questions) in a clean, read-only format. It ensures the board member sees the applicant's responses exactly as they were submitted.
Integration with Assessments: The Form Review component works in tandem with the Dynamic Assessment records. It "pulls" the answers from the assessment and displays them in a structured layout on the portal page.
Use Case: When a board member logs into the portal to evaluate a grant, they click on an application. The page they land on includes the Form Review component, allowing them to scroll through the project description, budget summaries, and impact goals.
Why other options are incorrect:
Form Overview (Option C): This component is typically used by the applicant to see a "Table of Contents" or a status summary of their own application (e.g., "Section 1: Complete, Section 2: In Progress").
Batch Assign Reviews (Option B): This is an administrative tool used by the internal Grant Manager to distribute applications to different reviewers; it is not the component used by the reviewer to actually see the application details.
By using the Form Review component, a consultant provides a professional and secure evaluation experience for the board, ensuring they have all the context needed to make funding decisions.