Free Salesforce Certified Agentforce Nonprofit Consultant NP-Con-102 Exam Questions

In the Nonprofit Success Pack (NPSP), Salesforce implements strict data integrity guardrails to prevent the accidental loss of financial history. One of the most critical protections involves the deletion of Account records that have associated 'financial' records.

According to NPSP documentation and standard database behavior:

Opportunity Protection: An Account cannot be deleted if it has any associated Opportunity (Donation) records that are in a 'Closed/Won' stage. This is a hard-coded safety feature in NPSP's trigger framework.

The Error Message: When a user attempts to delete the Household Account, the system will halt the operation and display an error message such as: 'This Account has Opportunities. You must delete all Opportunities before you can delete this Account.'

Audit Integrity: This ensures that the organization's total revenue figures remain accurate. If a household gave $1,000 last year, deleting that account would 'orphan' or delete those gifts, leading to a reconciliation nightmare in the general ledger.

Regarding other objects:

Affiliations and Relationships (Option C): These are child records of the Contact, not the Account. If you were deleting a Contact, these might be impacted, but they do not typically prevent the deletion of the parent Account directly; the primary blocker is the financial transaction.

Option A and B: These are incorrect because they imply the operation would either complete silently or be ignored without feedback. Salesforce always provides a clear error when a trigger validation (like NPSP's Opportunity check) fails.

To successfully delete such an account, the admin would first have to delete (or re-parent) the Closed/Won Opportunities.

Advanced Mapping is the powerful engine behind NPSP Gift Entry and the NPSP Data Importer. It allows consultants to map fields from a staging record to multiple objects (Account, Contact, Opportunity, etc.) simultaneously.

However, Advanced Mapping is architecturally dependent on the newer NPSP framework components. Specifically, Salesforce documentation states that Customizable Rollups must be enabled and deployed before Advanced Mapping can be activated.

Step-by-Step Dependency Logic:

Modernization: Customizable Rollups replaced the legacy 'Legacy Rollups' and provide a more flexible way to calculate donor totals.

Infrastructure: Both Customizable Rollups and Advanced Mapping utilize a shared set of underlying NPSP code resources. Enabling Customizable Rollups updates the database schema and triggers the necessary background processes that Advanced Mapping requires to function.

Enabling Advanced Mapping: Once Customizable Rollups are active, the consultant can go to NPSP Settings > Bulk Data Processes > Advanced Mapping and toggle the feature on. The system will then perform a 'deployment' of the mapping logic.

My Domain (Option C) is a general Salesforce requirement for Lightning components but is not the specific functional prerequisite for this NPSP feature. Custom Triggers (Option A) and Delegated Administration (Option B) are unrelated to the internal NPSP mapping engine dependencies.

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.

When donor totals (e.g., 'Total Gifts This Year') are incorrect, the consultant must investigate the l30ogic that aggregates those numbers. In NPSP, this involves a combination of configuration settings and system health tools.

Three Critical Areas to Troubleshoot:

Customizable Rollups (B): This is the engine that calculates the totals. The consultant should check if the Filter Groups are correctly defined. For example, if a rollup is set to only count 'Individual' gifts but the missing gifts are marked as 'Major Gifts,' the filter logic is the culprit.

Opportunity Stages (C): NPSP rollups only include donations that are in a 'Closed/Won' state. If the organization created a custom stage (e.g., 'Received - Awaiting Acknowledgment') but didn't mark that stage as 'Won' in the Stage picklist settings, those gifts will be ignored by the rollup engine.

NPSP Health Check (D): This is the first place a consultant should look for system-wide issues. The Health Check will identify if the nightly rollup batch job is failing, if there are orphaned records, or if there are 'Data Integrity' issues (like an Opportunity without an Account) that prevent the rollups from processing successfully.

Why other options are incorrect:

Salesforce Optimizer (Option A): This is a general org health tool (checking limits, unused fields, etc.) and does not have the nonprofit-specific logic needed to troubleshoot NPSP rollups.

Campaign Hierarchy (Option E): While hierarchies help with campaign reporting, they do not impact the 'hard credit' rollups on Account and Contact records.

The organization's requirements---fixed budget, fixed scope, and deliverables defined upfront---are the classic characteristics of the Waterfall methodology.

In a Waterfall implementation for Nonprofit Cloud:

Linear Progression: The project follows a strict sequence: Requirements -> Design -> Build -> Test -> Deploy. You do not move to the next phase until the previous one is 'signed off.'

Upfront Requirements: As mentioned in the prompt, the organization believes they already know exactly what they need. A consultant spends a long 'Discovery' phase at the beginning documenting every single field, report, and automation.

Predictability: This model provides the nonprofit's board with a clear 'end date' and a total cost, which is often attractive for organizations with rigid fiscal year budgets.

Why this is different from other methods:

Agile (Option B): Agile assumes the scope will change as the users learn more about the system. It prioritizes flexibility over a fixed upfront scope.

Kanban (Option C): Kanban is a 'just-in-time' delivery system focused on visualizing work and managing flow. It is typically used for ongoing support or 'business-as-usual' tasks rather than a structured implementation with a fixed SOW and predefined deliverables.

For a consultant, while the organization wants Waterfall, it is important to warn them that translating 'spreadsheets and notepads' into a sophisticated cloud system often reveals new requirements that Waterfall's rigid structure may struggle to accommodate without costly 'Change Orders.'

Managing the 'Grant Seeking' lifecycle in NPSP involves tracking multi-year relationships with funders. To provide the 'easy access' to history that the nonprofit requires, NPSP provides specific, standard fields on the Opportunity object designed for this exact scenario.

The NPSP Standard Solution:

Previous Grant/Gift Opportunity: This is a standard NPSP lookup field on the Opportunity. When a consultant creates a renewal grant, they should populate this field with the Original Grant record. This creates a direct 'link' or 'chain' between the two records, allowing a user to click from the current grant back to the previous one instantly.

Is Grant Renewal: This is a checkbox field. Checking this box allows the nonprofit to run reports specifically on 'Renewed Revenue' vs. 'New Revenue,' which is a key metric for many development directors.

Data Integrity: Using a lookup field (Option C) is superior to naming conventions (Option B) because naming is prone to typos and does not provide a clickable link. It is also superior to Campaigns (Option A) because a campaign shows a 'pool' of gifts but doesn't specifically define the chronological 'Renewal' relationship between two specific grants.

By utilizing these standard NPSP fields, the consultant ensures that the nonprofit can see the 'Evolution of a Grant' over time, making it easy to reference past project descriptions, budgets, and reporting requirements from the previous funding cycle.

In the context of the new Nonprofit Cloud (NPC) and its Fundraising capabilities, Salesforce has introduced a more granular data model to support wealth screening and donor prospecting. The correct object for tracking specific financial indicators like real estate and business ownership is the Contact Profile.

In earlier versions of Salesforce for nonprofits (like NPSP), this data might have required custom fields on the Account or Contact. However, in the modern Nonprofit Cloud architecture, the Contact Profile object is specifically designed to store sensitive, person-centric data that aids in major gift strategies. This object contains standard, out-of-the-box currency fields such as:

RealEstateValue: To track the estimated value of property owned by the constituent.

BusinessOwnershipValue: To record the value of private businesses the contact owns.

AssetLiquidationValue: For tracking liquid assets.

StockValue: For public equity holdings.

Step-by-Step Configuration for Wealth Prospecting:

Enable Fundraising: The consultant must first ensure that Fundraising is enabled in the Setup menu, as the Contact Profile fields for fundraising are available in more recent API versions (v59.0 and later).

Set Up Donor Profiles: The consultant should configure the Donor Profile---an account page layout within the Fundraising app.11 This page uses the Contact Profile record to display a 'Donor Summary' card.

Data Integration: Often, wealth data is imported from external screening services (like WealthEngine or iWave). The consultant maps these external data points directly to the standard fields on the Contact Profile object.

ARC Integration: To provide a 360-degree view, the Contact Profile data can be surfaced alongside the Actionable Relationship Center (ARC), allowing major gift officers to see a donor's net worth alongside their professional and personal affiliations.

By utilizing the standard Contact Profile object, nonprofits ensure their data remains compatible with built-in analytics and future Salesforce updates.

Accounting Subledger (ASL) is designed to bridge the gap between Fundraising (Salesforce) and Finance (General Ledger). It uses a 'Stage to State' mapping to determine when a fundraising record is ready to be processed as an accounting transaction.

In the Starter Edition of ASL, the system looks for specific 'States' to trigger record creation:

Committed: This state indicates that a donor has made a formal promise to give (a Pledge), but the cash has not necessarily been received yet. In accounting terms, this creates an Accounts Receivable entry.

Finalized: This state usually indicates that the cash has been received and the transaction is closed.

The Solution for Pledges:

To meet the requirement of exporting pledges 'when they are booked,' the consultant must map the organization's 'Pledged' Opportunity stage to the Committed Accounting State.

Step-by-Step Configuration:

Navigate to Accounting Subledger Settings.

Go to Stage to State Mapping.

Locate the Pledged stage (or whatever custom stage the nonprofit uses for booked pledges).

Map this stage to Committed.

Save the settings and run the subledger job.

Once this mapping is in place, as soon as an Opportunity is moved to the 'Pledged' stage, ASL will generate Ledger Entries that reflect the revenue as 'Committed.' These entries can then be exported to the external financial system to record the expected income on the organization's books.

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.

When implementing the new Nonprofit Cloud (NPC), the shift toward Person Accounts as the default model for individual constituents is a significant change from the traditional Nonprofit Success Pack (NPSP) model. A consultant must understand how this architecture impacts system logic and data integrity.

The Is Person Account (API name: IsPersonAccount) field is a standard Boolean field on the Account object that automatically evaluates to true when an account record is a Person Account. This field is critical for consultants for several reasons:

Filtering Automation: Because Person Accounts live on the Account object alongside Business Accounts (like Foundation or Corporate partners), a single Flow or Apex Trigger on the Account object will fire for both. To ensure that 'Company-specific' logic doesn't execute for an individual donor, a consultant uses the IsPersonAccount field as a decision element or entry criteria in Salesforce Flows.

Validation Rules: Validation rules intended for businesses (e.g., 'Tax ID is required for all Corporate Accounts') would fail for individual donors if not properly scoped. By adding AND(NOT(IsPersonAccount), ...) to the formula, the consultant ensures the rule only applies to Business Accounts.

Reporting and List Views: This field is the primary way to segment data. While Person Accounts mimic Contacts, they are technically Accounts, so this flag is the only way to quickly differentiate individuals from organizations in global queries.

Regarding the other options: Option A is incorrect because while many packages support Person Accounts, it is not a universal guarantee, and a consultant must always verify compatibility during the design phase. Option B is a common misconception; while some fields are prefixed in certain API contexts, standard contact fields on the Person Account record page often retain their standard labels, and custom fields created on the Contact object specifically for Person Accounts are suffixed with __pc, not prefixed with 'Person' for the API name.

For a nonprofit engaged in Grant Seeking, the Deliverables object in NPSP is the specific tool designed to manage the high-stakes requirements of institutional funding.34

Why Deliverables (D) are the best fit:56

Grant-Specific 7Metadata: Unlike standard Tasks, Deliverables include fields specific to the gr8ant process, such as 'Grantee Requirements,' 'Due Date,' and 'Requirement Description.'

Next Deadline Visibility: NPSP has built-in automation that identifies the 'earliest' incomplete Deliverable and surfaces its date on the parent Opportunity record in the 'Next Deliverable Date' field. This allows the fundraising team to see their upcoming deadlines at a glance without digging into related lists.

Audit and Compliance: Deliverables allow the organization to track not just that a 'Task' was finished, but that a specific legal or financial report was submitted. You can track 'Submitted' and 'Confirmed' dates, which are vital for maintaining good standing with a funder.

While Engagement Plans (Option A) and Tasks (Option B) can be used for general 'Moves Management,' they lack the specialized fields and the automated 'Next Deadline' rollup logic that makes Deliverables the gold standard for grant management in NPSP.

The organization should use Process Templates and Program Plans in Nonprofit Cloud. Process Templates provide standardized, repeatable sequences of steps and activities for refugee families entering the program, with the ability to define dependencies between steps. Program Plans organize these processes and track participant progress through the program. Together, these features minimize repetitious manual work by automating the assignment of standard tasks while allowing flexibility for individual family circumstances and sequential dependencies between services.

In the Nonprofit Success Pack (NPSP), error handling is centralized to ensure that critical failures in background processes (like nightly rollups or asynchronous triggers) do not go unnoticed. By default, NPSP may be configured to send notifications to all System Administrators, which can lead to 'notification fatigue' or sensitive technical data being sent to users who do not manage the system's backend.

To route these errors to a single, specific individual, a consultant must use the NPSP Settings interface.

Step-by-Step Configuration:

Navigate to NPSP Settings: Use the App Launcher to find the NPSP Settings tab.

Access Error Handling: In the sidebar, go to System Tools and then click on Error Notifications.

Edit Settings: Click the Edit button at the top of the page.

Change Recipient Type: Look for the field labeled Error Notifications To. By default, this might be set to 'All System Administrators.' Change this value to User.

Select the Admin: A new lookup field will appear. Search for and select the specific System Administrator who should be the point of contact for technical issues.

Save: Click Save.

Once this is configured, any Apex errors triggered by the NPSP framework (TDTM, Batch jobs, etc.) will generate an email sent exclusively to that selected user. This is a best practice for governance as it ensures a clear line of accountability for troubleshooting.

Why other options are incorrect:

Option A: Standard Salesforce 'Apex Warning Emails' in Setup are different from NPSP-specific framework errors.

Option B: There is no 'disable' checkbox for individual users in the NPSP settings; the system uses a single designated recipient (User, Chatter Group, or Profile).

Option D: Changing profiles just to manage email notifications is an extreme and unnecessary security change that would disrupt the permissions of other administrators.