Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (NPC) NP-Con-102 Free Practice Exam Questions (2026 Updated)

When a nonprofit uses a Full Copy Sandbox, the sandbox contains an exact replica of all the production data, including sensitive donor PII (Personally Identifiable Information). Giving a contractor access to this data is a significant security and compliance risk.

The Solution: Salesforce Data Mask:

Anonymization: Salesforce Data Mask is a powerful managed package that allows an admin to "scrub" or "mask" sensitive data in a sandbox.

Methods: It can replace real names with random names (Anonymization), replace characters with "X" (Deletion), or shuffle values within a column (Pseudonymization).

Developer Experience: The contractor can still see the structure of the data and write code against it, but the actual "John Doe at Main St" becomes "Sam Smith at 999 West Rd."

Security: This ensures that even if the developer's local machine or account is compromised, no real constituent data is exposed.

Why other options are incorrect:

Encryption (Options A & C): This protects data at rest but does not help if the developer has the permissions to view the decrypted data for testing purposes.

Profiles (Option D): This is insufficient because a developer often needs access to the fields themselves to write code; Data Mask allows them to see the field while hiding the sensitive content.

When performing complex integrations or troubleshooting why a field is missing in an older sandbox, a consultant needs a reliable reference for the NPSP metadata.

The NPSP Data Dictionary:

Historical Reference: The NPSP Data Dictionary is an official Salesforce resource (usually provided as a spreadsheet or a dedicated help article). It lists every object and field included in the managed package.

Version Tracking: Crucially, the Data Dictionary includes a column for "Introduced In" or "Package Version." This tells the consultant exactly which release of NPSP (e.g., 3.154) first included that specific field.

Object Mapping: It also provides the API names, descriptions, and help text for all NPSP-specific fields, making it the primary "source of truth" for mapping projects.

Why other options are incorrect:

Custom Field Definition (Option C): In the Salesforce Setup menu, the field detail page will show the "Installed Package" (Nonprofit Success Pack), but it does not tell you which version of that package introduced the field.

NPSP Package Details (Option A): This shows you the current version installed in the org, but not the historical release version for individual fields.

Schema Builder (Option D): This is a visual tool for seeing relationships between objects; it contains no versioning or historical metadata.

When delegating access to Gift Entry in NPSP, a consultant must follow the "Principle of Least Privilege." This means granting enough access to do the job without exposing the entire system.

Three Essential Permissions:

Object and Field Access (B): Users must be able to Create and Edit the records involved in the gift entry process. This includes the NPSP Data Import (the staging object), Accounts, Contacts, Opportunities, and GAU Allocations. Note that Delete (Option E) is usually not a "necessary level of access" for a standard entry clerk; they only need to enter and modify records.

Tab Visibility (C): A user cannot use a feature if they cannot find it. The Gift Entry tab must be set to "Default On" or "Visible" within the permission set so the users can access the interface.

Visualforce Page Access (D): NPSP Gift Entry is built using a custom interface. To run this interface, the user's profile or permission set must explicitly have access to the underlying Visualforce pages that power the tool, specifically those related to the Batch Object Importer (BOI). Without access to BOI_BatchOverride and BOI_DataImport, the user will see an "insufficient privileges" error when they try to open the Gift Entry tool.

Option A is incorrect because View All Data is a powerful administrative permission that bypasses all security and is never appropriate for a standard data entry role.

For organizations delivering personalized social services, the intake evaluation is the most critical touchpoint. To manage this efficiently, Salesforce Nonprofit Cloud utilizes Dynamic Assessments, a feature built upon the Discovery Framework and OmniStudio (specifically OmniScript).

Unlike a static form, a Dynamic Assessment allows a caseworker to navigate a "branching" path of questions. If a client answers "Yes" to a question about housing instability, the system can automatically trigger a sub-section of questions regarding shelter history. If they answer "No," those questions remain hidden, reducing "form fatigue" and ensuring the intake is as fast and relevant as possible.

Step-by-Step Implementation for the Consultant:

Define Assessment Questions: Using the Discovery Framework, the consultant creates a library of individual questions (e.g., "Do you have dependable transportation?"). These questions are modular and can be reused across different intake forms.

Build the OmniScript: The consultant uses the OmniScript Designer to arrange these questions. This is where the Conditional Logic is applied (e.g., "Set Element Visibility" based on prior answers).

Map to Objects: Through DataRaptors or Integration Procedures, the consultant ensures that the data captured during the assessment is automatically pushed into the correct Salesforce objects, such as Person Accounts, Case Proceedings, or Life Events.

Action Plan Integration: Often, the completion of a Dynamic Assessment is linked to an Action Plan, which might automatically generate a "Welcome Kit" task or a "Referral" based on the needs identified during intake.

By using Dynamic Assessments, the nonprofit ensures a standardized, compliant, and data-driven intake process that captures a 360-degree view of the client's assets and barriers to success without requiring the caseworker to navigate through irrelevant fields.

Nightly batch jobs in NPSP, particularly the Rollup Donors batch, process thousands or millions of records. Any increase in the "workload" per record will result in a measurable increase in total processing time.

Two Primary Performance Factors:

New Flows (A): Salesforce Flows (especially Record-Triggered Flows) are highly powerful but resource-intensive. If a new Flow was activated on the Opportunity or Account object, it will fire every time the NPSP batch job updates a record. If the batch job updates 100,000 Accounts, the Flow runs 100,000 times. If the Flow contains "In-Loop" queries or complex logic, it can drastically slow down the batch execution time or even cause it to hit governor limits.

New Customizable Rollups (C): Every time you add a new Customizable Rollup in NPSP Settings, you are adding another calculation that the batch job must perform for every record. If the new rollup has complex filters (e.g., "Total Gifts from 3 years ago excluding In-Kind and Grants"), the system must query more data and perform more evaluations per record, extending the batch window.

Why other options are less likely:

Standard Roll-up Summary (Option B): These are calculated by the Salesforce platform kernel and are generally more efficient than Apex-based rollups. While they add some overhead, they usually do not cause the "significant" slowdowns seen with custom logic or complex NPSP settings.

Role Hierarchy (Option D): While changes to the hierarchy trigger sharing recalculations, this typically affects record visibility and sharing performance rather than the execution speed of a data-processing batch job.

NPSP is a Managed Package. In Salesforce, you cannot simply go into Setup and change the labels of fields that are part of a managed package because those fields are "locked" to protect the package's integrity and ability to receive updates.

The Solution: Translation Workbench:

Overriding Labels: To change "Organization" to "Organisation" (the UK spelling), the consultant must use the Translation Workbench. Even though both are English, Salesforce treats English (UK) and English (US) as different locales.

Override Feature: Within the Translation Workbench, there is an "Override" section specifically for managed packages. The consultant selects the Nonprofit Success Pack package, chooses the object (e.g., Account or GAU), and then enters the "New Label" for the specific field.

Global Impact: This change is reflected across the entire user interface, including reports, list views, and page layouts, without actually modifying the underlying code of the managed package.

Why other options are incorrect:

Reword in Setup (Option A): This works for custom fields you created, but it is blocked for fields starting with the npsp__ prefix.

Language Settings (Option B): Activating English (UK) will change standard Salesforce labels (like "Zip Code" to "Postcode"), but it does not automatically "UK-ize" the custom labels defined inside the NPSP managed package.

Support Case (Option C): Salesforce support does not perform UI label customization for individual customers.

In many nonprofits, "Interaction Summaries" (meeting notes) contain highly sensitive information. A caseworker's notes on a victim of domestic violence must be kept strictly confidential from a fundraiser who might be looking at the same constituent record for a donation appeal.

To solve this challenge, Nonprofit Cloud utilizes Compliant Data Sharing (CDS).

How CDS Secures Interaction Summaries:

Record-Level Restriction: By default, Interaction Summaries can be set to "Private" in the Organization-Wide Defaults (OWD).

Role-Based Access: Compliant Data Sharing allows the organization to grant access based on the user's specific role in relation to that record. For example, only the "Assigned Caseworker" and "Program Supervisor" roles are granted "Read" access to the summary.

Departmental Silos: Because fundraisers are not assigned a "Program" role in the CDS configuration for those specific records, they will not be able to see the Interaction Summaries, even if they have access to the Person Account record.

Auditability: CDS provides a clear audit trail of who was granted access to sensitive notes and why, which is critical for legal compliance in social services.

Why other options are incorrect:

Permission Sets (Option A): These grant the ability to use the Interaction Summary object (CRUD), but they do not control which specific records a user can see. If OWD is set to Public, Permission Sets won't hide specific department notes.

Session Security (Option B): This deals with 2-factor authentication and login requirements, not record-level data visibility between departments. Compliant Data Sharing is the standard Industry Cloud tool for this level of granular privacy.

In Salesforce, sensitive data like Social Security Numbers or Tax IDs is often protected using Classic Encryption or Shield Platform Encryption. When a field is encrypted, it appears as masked (e.g., XXXX-XX-1234) to most users, even if they have "Read" access to the Contact object.

To allow a specific subset of users (such as the HR Director or a high-level Compliance Officer) to see the actual, unmasked data, the View Encrypted Data system permission must be utilized.

Step-by-Step Implementation:

Create a Permission Set: The consultant should create a specific Permission Set named "PII Access" or similar.

Enable System Permission: Under the System Permissions section of the Permission Set, the consultant must locate and check the box for View Encrypted Data.

Assign to Users: This Permission Set is then assigned only to the specific users who require access to the sensitive identification numbers.

Security Principle: This follows the "Principle of Least Privilege." Users with this permission can see the data in plain text in reports, list views, and record pages, while all other users see the masked version.

Why other options are incorrect:

View All Data (Option A): This is a very broad and dangerous permission that grants access to almost all data in the org, but even "View All Data" does not automatically unmask encrypted fields unless View Encrypted Data is also present.

Manage Encryption Keys (Option B): This is a highly technical administrative permission for managing the security certificates and keys; it does not grant the ability to view field data.

View All Contacts (Option D): This provides object-level visibility but respects field-level security and masking.

Advanced Mapping in the Nonprofit Success Pack (NPSP) is a powerful tool that allows admins to customize how data from the NPSP Data Import staging object is pushed into target records. However, it operates within a specific architectural framework.

Key Architectural Considerations:

Object Relationships: Advanced Mapping is designed to handle the core "Nonprofit Triangle" of data: Accounts, Contacts, and Opportunities. For any additional or custom object to be eligible as a target in Advanced Mapping, it must have a direct lookup or master-detail relationship to one of these three primary objects. This is because the NPSP Data Importer logic relies on these "anchor" records to establish context and maintain data integrity.

Mapping Groups: The tool organizes mappings into Object Groups. When you create a new group for a custom object (e.g., "Volunteer Hours"), the system validates that the custom object is related to a Contact or Account so it knows which record to link the new data to.

Field Type Support: Contrary to Option A and C, Advanced Mapping supports a wide variety of field types, including Checkboxes, Picklists, and Lookups. The restriction isn't on the field type, but on the object's position in the data hierarchy.

Custom Object Support: While the question asks about "NPSP objects" (Option D), Advanced Mapping can map to custom objects created by the organization, provided they follow the relationship rules mentioned above.

Understanding these relationship requirements is essential for a consultant during the data migration or integration design phase. It ensures that the staging file can successfully populate multiple related records in a single execution without custom Apex code.

This requirement involves two parts: a one-time transaction and an automated long-term "influence" tracking. In NPSP, this is best accomplished by using the Relationship object's advanced soft-credit capabilities.

Step-by-Step Implementation:

Define the Automated Soft Credit: The consultant should create a Relationship record between the Board Member and the Donor.

Set the Related Opportunity Contact Role: On this Relationship record, there is a field called Related Opportunity Contact Role. The consultant should select Soft Credit (or a custom role like "Solicitor").

The Automation Logic: By setting this field on the relationship, NPSP's trigger framework is instructed that every time a donation is created where the donor is the "Primary Contact," the person on the other end of the relationship should automatically be added to that donation as an Opportunity Contact Role with the specified soft 3credit role.45

Result: When the fundraiser creates the current donation, the board member is automatically soft-credited. For every future donation the do6nor makes, the system will continue to grant that soft credit automatically, satisfying th7e requirement to track all future gifts without manual intervention.

Why other options are incorrect:

Option A and D: These suggest adding the soft credit manually to the current donation. While this works for the current gift, it does not address the "any future donations" requirement, which would require the fundraiser to remember to do it every single time.

Option C: Partial Soft Credits are used for splitting gifts among multiple people (e.g., $50 to person A, $50 to person B). It is more complex than needed here and does not have the automated "future" triggering logic found in the Relationship-based soft credit model.

In the context of a Nonprofit Cloud implementation, the Agile methodology is often preferred over traditional methods because it accounts for the evolving needs of mission-driven organizations. Unlike a rigid framework, Agile focuses on delivering value in small, manageable increments called "Sprints."

Two of the most significant benefits of this approach are:

Iterative Planning: Rather than trying to document every single requirement for a complex feature like "Outcome Management" at the very start, Agile allows for continuous planning. The consultant and the nonprofit stakeholders prioritize a "Backlog" of work. At the start of each sprint, the team plans only the work for that cycle. This allows the organization to pivot if, for example, a new grant requirement is announced mid-project that changes how they need to track benefits.

Hands-on Stakeholder Involvement: Agile requires constant collaboration. Stakeholders (such as Program Managers or Gift Officers) are involved in "Sprint Reviews" where they see live demonstrations of the work completed. This "fail-fast" or "learn-early" model ensures that if a consultant builds a Gift Entry flow that doesn't quite match the staff's physical workflow, it is caught and corrected within weeks rather than months.

Why other options are incorrect:

Option A: Defining all risks early and producing a "single deliverable" is a hallmark of the Waterfall method. In Agile, risks are identified continuously, and deliverables are produced incrementally.

Option C: A "linear sequence" and "carefully controlled change" describes a rigid Waterfall environment. In contrast, Agile is non-linear and embraces change as a way to improve the final product's relevance to the nonprofit's mission.

For a consultant, it is vital to distinguish between the Program Management Module (PMM) and Nonprofit Cloud Case Management (NCCM). While they work together, they serve different functional depths.

PMM (Standard Service Tracking): PMM is designed for "Service Delivery." It tracks which clients are in which programs and when they received a service (e.g., "John attended the Food Bank on Tuesday"). It is excellent for high-volume, low-touch interactions.

NCCM (Deep Clinical/Social Work): Nonprofit Cloud Case Management is designed for "high-touch" human services. It introduces a much more granular data model. Specifically, it includes custom objects like Goals and Action Items that are part of a Case Plan. These allow a caseworker to define a specific journey for a client (e.g., Goal: "Secure Employment," Action Item: "Draft Resume").

The Core Distinction:

The consultant should explain that while PMM tracks what was delivered, Case Management provides the specialized objects needed to track the client's long-term progress through Goal tracking.

Option A: PMM does not have specialized calendar objects; it uses standard Salesforce Activities.

Option C: This is incorrect. Case Plans and Action Items are features of Case Management, not the standard PMM.

Option D: Case Management does not require Experience Cloud, though they are often used together for participant portals.

By highlighting the Goal and Action Item objects, the consultant helps the nonprofit understand that Case Management is the correct choice for their "care-centric" requirements.

When dealing with Large Data Volumes (LDV)—specifically in the range of "tens of millions of records"—standard import tools and standard APIs are insufficient due to governor limits and processing speeds. For a time-sensitive weekend migration, the Bulk API is the only architecturally sound recommendation.

Why Bulk API is Required:

Parallel Processing: Unlike the SOAP API (Option B), which processes records synchronously (one by one or in small serial batches), the Bulk API is designed for asynchronous processing. It breaks the data into large chunks (up to 10,000 records per batch) and processes them in parallel on the Salesforce application servers.

Minimized API Calls: Tens of millions of records would quickly exhaust an organization's daily SOAP API limits. The Bulk API is optimized to handle massive datasets with significantly fewer API calls.

Weekend Constraint: The "weekend" requirement implies a need for high throughput. The Bulk API is the fastest method available for moving data into Salesforce, making it possible to complete a multi-million record migration within a 48-hour window.

Why other options fail:

NPSP Data Import (Option C): While powerful for processing complex logic (like creating Accounts and Contacts at once), it is built on top of standard Apex processing and is significantly slower than the Bulk API for pure volume.

Data Import Wizard (Option D): This tool is limited to 50,000 records per session, making it impossible to use for a migration of this scale.

A consultant would typically use a tool like Data Loader (configured for Bulk mode) or a dedicated ETL tool (like Informatica or Mulesoft) that utilizes the Bulk API to achieve the necessary performance.