NP-Con-102 Salesforce Certified Agentforce Nonprofit Consultant Exam Topics and Questions

This topic sets the context for everything that follows. You need to show you understand how nonprofits operate, what drives their technology decisions, and how to deliver a project that actually lands. The weight is modest, but the material underpins the rest of the exam.

How Nonprofit Implementation Strategy is tested

Eleven percent means three or four items, and they will test whether you can translate a nonprofit's mission into a workable implementation plan. Expect scenarios where a stakeholder describes a problem in their own language and you must identify the correct discovery step, the right artifact to produce, or the phase of the project lifecycle where a given activity belongs. The trap is choosing answers that sound professional but skip the nonprofit context. A generic project management response will cost you marks if it ignores the organisation's funding model, volunteer workforce, or reporting obligations to donors and grantmakers. Read each scenario for the nonprofit-specific constraint, then pick the answer that acknowledges it.

Where the first topic asked you to plan the project, this one asks you to design the solution. At thirty-two percent, it is the heaviest topic on the exam. You will spend more time here than anywhere else, and the questions dig into the choices you make when a requirement could be met in several ways.

– Choosing the right toolset

The first sub-topic tests your ability to evaluate whether a requirement should be met with Agentforce Nonprofit out of the box, a platform feature like Flow or a custom object, or a third-party app from the AppExchange. The exam expects you to know when the native data model is enough and when it needs extension. You also need to recognise the boundary between configuration and customisation, and when a managed package is the better bet because it brings domain logic you would otherwise have to build. The wrong answer is usually the one that over-engineers a simple requirement or tries to stretch a feature past its design.

– Mapping process to data model

The second sub-topic is about alignment. A nonprofit describes how they work today, and you must map that process onto the Agentforce Nonprofit data model without forcing a fit that will break later. This means understanding which standard objects handle which business entities, how relationships are represented, and where the model expects certain workflows to live. The exam will present a process and ask which object or set of objects supports it correctly. Candidates lose marks when they pick an object because its name sounds right, but its relationships or lifecycle do not match the requirement. Read the process carefully, then trace it through the schema.

– Industries Common Features

The third sub-topic covers the shared toolset that sits above the platform but below the vertical solution: OmniStudio for guided experiences, Data Processing Engine for batch calculations, Action Plans for templated task sequences, and Dynamic Assessments for structured data collection. You need to know when each one is appropriate and when it is overkill. A question might describe a requirement for intake or case progression and ask which feature fits. The trap is choosing the most powerful tool when a simpler one would do, or ignoring these features entirely and defaulting to Flow or Apex when they were built to solve exactly this class of problem.

How Solution Design is tested

Thirty-two percent translates to nine or ten items, and they will be scenario-heavy. You will read a paragraph describing a nonprofit's requirement, then choose the design that meets it without creating technical debt. The scenarios are written to make two or three answers look plausible, so you need to evaluate trade-offs: declarative versus programmatic, standard versus custom, native versus third-party. The exam rewards answers that respect the data model, use the right Industries feature when one exists, and avoid unnecessary complexity. Candidates lose marks by picking solutions that work but do not scale, or by choosing a custom build when a standard feature was designed for exactly that use case. Every question in this topic is a design decision under constraint. Read for the constraint first, then eliminate answers that ignore it.

Once the design is settled, you have to configure the org. This topic is about the foundational setup steps that make Agentforce Nonprofit work: turning on features, assigning the right permissions, and configuring the objects that represent people and their connections. At twenty-two percent, it sits between the strategy layer and the feature layer, and it tests whether you can execute the design you chose in the previous topic.

– Permissions and licensing

The first sub-topic covers enablement and access. Agentforce Nonprofit features do not work until they are switched on, and users cannot see them without the correct permission sets and permission set licenses. You need to know which features require which permissions, and the difference between a permission set that grants access to a feature and a permission set license that unlocks a whole tier of functionality. The exam will describe a user role or a feature request and ask what must be assigned or enabled. The trap is assuming that installing the package is enough, or assigning a permission set without the underlying license. Read the question for what the user needs to do, then work backwards to the permission and license that allow it.

– Stakeholder Management

The second sub-topic is about configuring the objects that represent people and their relationships. Stakeholder Management in Agentforce Nonprofit uses person accounts to model individuals, relationship objects to capture connections between them, and address management to handle multiple locations per contact or household. You need to know when to enable person accounts, how to configure reciprocal relationships, and how the address model differs from the standard Contact mailing address. The exam will ask you to choose the correct setup for a requirement involving households, affiliations, or multiple addresses. Candidates lose marks when they try to use standard Contacts for scenarios that need person accounts, or when they configure relationships without understanding that the system maintains both sides automatically.

How Agentforce Nonprofit Setup is tested

Twenty-two percent means six or seven items, and they focus on the mechanics of getting the system ready. Expect questions that describe a feature or user need and ask what must be enabled or assigned to make it work. You will also see scenarios involving person accounts, relationships, or addresses, and you must choose the correct configuration. The exam tests whether you know the dependency chain: which permission set licenses unlock which permission sets, which features require which setup steps, and which objects must be enabled before others can be configured. The trap is choosing an answer that sounds right but skips a prerequisite step, or configuring something in a way that will cause problems later when the org scales. Read each scenario for the full requirement, not just the immediate ask.

The final topic is the heaviest on the exam at thirty-five percent. It focuses on configuring Fundraising Management, the feature set that handles donations, pledges, campaign attribution, recognition, and acknowledgements. This is where the exam tests your ability to configure the system to match how a nonprofit actually raises and tracks money. The sub-topic list is short but each element is dense, and the exam expects you to know not just what each feature does but how they interact. Gift Entry is the interface through which donations are recorded, whether one-off or recurring. Gift Commitments model pledges, allowing the system to track what a donor has promised against what they have paid. Outreach Source Codes link gifts to campaigns or appeals, so the organisation can measure which fundraising efforts work. Soft Credits let you attribute a gift to someone who facilitated it but did not write the cheque, which matters for relationship management and recognition. Gift Acknowledgements automate the thank-you process, generating letters or emails based on rules you configure. Each of these pieces has its own configuration surface, and the exam will ask you to choose the right settings for a given fundraising workflow. You need to know which fields control what, how the features depend on one another, and where the common configuration mistakes happen. A question might describe a pledge payment schedule and ask how to configure the commitment, or present a scenario involving joint donors and ask where to apply the soft credit. The answers look similar, so you need to know the mechanics in detail.

How Agentforce Nonprofit Feature Configuration is tested

Thirty-five percent means ten or eleven items, and they will dig into the configuration details of Fundraising Management. Expect scenarios that describe a fundraising process and ask you to configure Gift Entry, set up a Gift Commitment, apply an Outreach Source Code, assign a Soft Credit, or generate an acknowledgement. The exam rewards answers that reflect how these features are meant to be used together, not in isolation. The trap is choosing a configuration that works for the immediate requirement but breaks a downstream process, or misunderstanding the relationship between a gift and a commitment, or placing a soft credit on the wrong object. Candidates also lose marks by ignoring the acknowledgement rules and assuming the system will send the right message automatically. Every question in this topic is a test of whether you know the feature well enough to configure it under real-world constraints. Read the scenario for the full workflow, not just the step being asked about, because the correct answer often depends on what happens before or after.