Nonprofit Cloud Consultant Mock Test
Salesforce Certified Agentforce Nonprofit Consultant — Free Practice Exam with Explanations
About This Nonprofit Cloud Consultant Practice Test
These 50 original practice questions were written for consultants preparing for the Salesforce Nonprofit Cloud Consultant credential — the exam Salesforce now publishes as the Salesforce Certified Agentforce Nonprofit Consultant (exam code NP-Con-102). They work through the parts of the job the exam actually tests: shaping an implementation for an organisation with a small operations team, choosing between the Nonprofit Cloud data model and a third-party or custom option, enabling the platform in the right order, and configuring Fundraising, Program Management, Case Management, Outcome Management and Grantmaking.
Every question includes a written explanation covering why the correct answer is right and why the distractors are not, so a wrong answer teaches you something rather than just costing a point. The question mix follows the published exam outline percentages, which means Feature Configuration and Solution Design together account for roughly two-thirds of the test.
One thing to settle before you start studying: this exam covers the integrated platform solution built on standard objects such as GiftTransaction, ProgramEnrollment and FundingAward. It does not cover the Nonprofit Success Pack managed package, which has its own separate credential. If your day job is NPSP, budget real time for the data model.
Note: these are original practice questions written by the A2Z Salesforce team. They are not real Salesforce exam questions, and no exam content is reproduced here.
Last updated:
Official Exam Format
- 60 Multiple Choice Questions
- Up to 5 unscored questions
- 65% Passing Score
- 105 Minutes
- Proctored / Online
- Prerequisite: Salesforce Certified Administrator
Domain Weighting
- Feature Configuration — 35%
- Solution Design — 32%
- Setup — 22%
- Implementation Strategy — 11%
Nonprofit Cloud Consultant Practice Questions
Show explanation & topic
Correct answer: C. A vision and value map exists to make the line from mission outcome to capability to measurable benefit explicit. Once that line is drawn, a feature request either supports a stated outcome or it does not, and the conversation stops being about personal preference.
Why the other options are wrong: Field-level design comes much later and is a different artefact. A value map does not replace requirements gathering; it frames it. And it is a planning tool, not a commercial contract — fixing budget is a separate exercise.
Exam domain: Nonprofit Implementation Strategy
Show explanation & topic
Correct answer: B. A single major bequest or a lost grant can swamp the effect of any system change. Measures the implementation genuinely influences — retention, recurring gift attrition, processing time per gift, acknowledgement turnaround — attribute results more honestly and are the ones the project team can act on.
Why the other options are wrong: Revenue reporting is standard reporting, not custom code, and there is no restriction on nonprofits reporting revenue. Deferring measurement to a later phase removes the baseline you need in order to show change at all.
Exam domain: Nonprofit Implementation Strategy
Show explanation & topic
Correct answer: D. With a single part-time admin, adoption capacity is the binding constraint, not build capacity. Phasing around change absorption — and getting the constituent model right first, since Fundraising, Programs and Outcomes all hang off it — is the standard recommendation.
Why the other options are wrong: A big-bang release concentrates all training, data migration and support load on one date, which is exactly what a thin operations team cannot handle. Outcome Management first is backwards, because indicators need programme and participant data to measure. Building everything and deciding later wastes budget on work that may be deferred indefinitely.
Exam domain: Nonprofit Implementation Strategy
Show explanation & topic
Correct answer: A. Infrequent users forget procedures between sessions. Guided paths that constrain what can be entered, plus job aids sized for a five-minute refresher, hold up far better than one-off training.
Why the other options are wrong: Handing out administrator access to occasional volunteers is a serious security and data-integrity risk. Requiring certification of volunteers is unrealistic. Re-keying paper forms reintroduces the manual effort the system was bought to remove and adds a second opportunity for error.
Exam domain: Nonprofit Implementation Strategy
Show explanation & topic
Correct answer: C. Grantmaking configuration turns on how applications are reviewed and decided — review stages, scoring, decisions, award requirements. The people who do that work are primary stakeholders, not consultees.
Why the other options are wrong: Budget authority is not the same as process knowledge. Surveying after design means any gap becomes rework. Proxying the process through IT reliably produces a description of the system people wish they had rather than the work they do.
Exam domain: Nonprofit Implementation Strategy
Show explanation & topic
Correct answer: B. Overlapping constituent roles and restricted funds are the two structural differences that drive most nonprofit design decisions, which is why Nonprofit Cloud ships relationship objects and a designation model rather than expecting you to bolt them on.
Why the other options are wrong: Nonprofits absolutely track revenue and gift pipelines. Nonprofit Cloud is built on standard objects, not a custom-object sprawl. And funders typically demand more quantitative reporting, not less.
Exam domain: Nonprofit Implementation Strategy
Show explanation & topic
Correct answer: C. The key architectural difference is that Nonprofit Cloud's fundraising, programme, grantmaking and outcome capabilities are standard objects on the core platform, while NPSP is a managed package layered on Contacts, household Accounts and Opportunities. For a greenfield customer that is the deciding factor.
Why the other options are wrong: It is Nonprofit Cloud that uses dedicated fundraising objects such as GiftTransaction; NPSP is the one that models donations as Opportunities. NPSP is not restricted to Essentials. And Nonprofit Cloud needs a deliberate enablement sequence — nothing meaningful is on by default.
Exam domain: Solution Design
Show explanation & topic
Correct answer: A. Person Accounts cannot be switched off once enabled, and Salesforce documents that they are not supported for use with the Nonprofit Success Pack. Both points belong in a written decision record before anyone clicks Enable.
Why the other options are wrong: The Marketing User flag is unrelated. There is no 10,000-Contact eligibility threshold of that kind. And enabling Person Accounts does not retroactively restructure existing business accounts — migration is a separate, planned exercise.
Exam domain: Solution Design
Show explanation & topic
Correct answer: D. Salesforce explicitly notes that Person Accounts are not required for Grantmaking and that grantmakers funding primarily organisations are likely to find the Contact plus business Account model more appropriate. Given that enabling Person Accounts is irreversible, not enabling them here is the conservative and correct call.
Why the other options are wrong: Person Accounts are strongly recommended for Fundraising and Program Management, not mandatory everywhere. A custom Constituent object throws away the standard data model and everything built on it. Leads are a sales-funnel construct with no place in a grantee record model.
Exam domain: Solution Design
Show explanation & topic
Correct answer: B. PartyRelationshipGroup represents a household or affiliated group, and the group membership objects connect individuals to it. That gives you a household for mailing and rollup purposes without collapsing four giving histories into one.
Why the other options are wrong: Public groups are a sharing construct for users, not constituents. Merging four donors into one record destroys individual giving history and is very difficult to unpick. A Campaign records participation in an appeal, not a living arrangement.
Exam domain: Solution Design
Show explanation & topic
Correct answer: C. Data Processing Engine is the Industries tool for large-scale, scheduled aggregation and write-back. Nonprofit Cloud's own scoring and rollup features are built on it, which is also why it is a prerequisite for several other capabilities.
Why the other options are wrong: A formula field cannot aggregate arbitrary related records at that scale. A record-triggered flow per transaction would recompute continuously and hit governor limits during batch gift loads. Validation rules only prevent saves; they never calculate and store values.
Exam domain: Solution Design
Show explanation & topic
Correct answer: D. Record rollup definitions are the Industries answer to exactly this shape of problem: aggregate across a lookup, apply filter conditions, and run the aggregation through Data Processing Engine on activation. Nonprofit Cloud ships household and data summary rollups built this way.
Why the other options are wrong: Classic roll-up summary fields require a master-detail relationship, which rules them out here. Cross-object formulas cannot aggregate a child collection. Apex is unnecessary when a declarative feature exists and would need its own tests and maintenance.
Exam domain: Solution Design
Show explanation & topic
Correct answer: A. Action plan templates exist to turn a repeatable checklist into tasks and document checklist items, with due dates calculated relative to a trigger date. The exam guide lists Action Plans among the Industries Common Features a consultant is expected to place correctly.
Why the other options are wrong: Discovery Framework builds dynamic assessments — questionnaires — not task checklists. An approval process handles one approval decision, not an eight-step sequence with documents. Data Processing Engine does bulk data aggregation, not task generation.
Exam domain: Solution Design
Show explanation & topic
Correct answer: B. Discovery Framework is the assessment engine used across Industries clouds, including Nonprofit Cloud intake. Questions are configured rather than coded, versions can be managed, and responses are stored in a structure built for analysis.
Why the other options are wrong: A field-per-question custom object means schema changes twice a year and orphaned fields forever. A free-text note cannot be compared or aggregated. A custom LWC form is a development project that solves a problem the platform already solves.
Exam domain: Solution Design
Show explanation & topic
Correct answer: C. OmniStudio is named in the exam outline as one of the Industries Common Features to place correctly, and guided multi-step interaction with branching is precisely what an OmniScript is for.
Why the other options are wrong: Visualforce is legacy and would be a development project. A report displays data; it cannot collect it. Conditional field-level security does not produce a branching, staged experience and is not designed to be reconfigured per intake scenario.
Exam domain: Solution Design
Show explanation & topic
Correct answer: A. A Gift Commitment represents the promise — a pledge, a recurring gift, an accepted grant proposal — and the Gift Commitment Schedule defines how it will be fulfilled. Each payment that actually arrives is a Gift Transaction.
Why the other options are wrong: Twelve commitments would report as twelve separate promises worth $720,000 in aggregate views. A single $60,000 transaction claims money you have not received. And Opportunities with payment schedules are the NPSP model, not Nonprofit Cloud's.
Exam domain: Solution Design
Show explanation & topic
Correct answer: D. Gift Designations represent funds designated for a specific purpose, and GiftTransactionDesignation is the junction that lets one gift be split across several designations with an amount each. Campaign remains the right place to track the appeal.
Why the other options are wrong: Forcing donors to give three gifts solves a data problem by inconveniencing donors. A single picklist cannot express a split. Parsing free text at reporting time is not an auditable basis for restricted fund accounting.
Exam domain: Solution Design
Show explanation & topic
Correct answer: B. Indicator Definition is the reusable, standard description of what is being measured; Indicator Assignment attaches it to a programme or outcome; Indicator Performance Period holds the time period with baseline and target, and Indicator Results record the values.
Why the other options are wrong: A Campaign field is not a shared, governed measure definition. Benefit Disbursement records what a participant received, not a performance measure. Funding Award Requirements are grantmaking deliverables, not the organisation's own impact framework.
Exam domain: Solution Design
Show explanation & topic
Correct answer: C. FundingOpportunity is the pool of money available for a purpose; IndividualApplication is the submitted application; FundingAward captures the approved award details and period; FundingDisbursement is each payment made or scheduled.
Why the other options are wrong: The Campaign-to-Opportunity chain is a sales model. The Program chain is service delivery to participants, which is the money going out as services rather than as grants. The Gift chain is money coming in from donors.
Exam domain: Solution Design
Show explanation & topic
Correct answer: A. JobPositionShift represents the work shift and JobPositionAssignment places a specific person on a specific shift on a specific day. Volunteer Management is not available in every edition, so edition and licensing must be verified before it is designed in.
Why the other options are wrong: Zero-value gift transactions would corrupt fundraising reporting. The availability claim in option C is simply false. And volunteers are constituents, not Salesforce users — provisioning user licences for them would be both costly and unnecessary.
Exam domain: Solution Design
Show explanation & topic
Correct answer: D. Knowing where the product stops and the ecosystem starts is part of solution design. The consultant's job is to select a fit-for-purpose partner solution and design the integration into Gift Transactions, designations and commitments.
Why the other options are wrong: Storing raw card numbers in Salesforce creates a serious compliance problem and is not what Payment Instrument is for. Declaring online giving impossible is wrong. Monthly manual reconciliation from bank statements loses donor attribution and delays acknowledgements.
Exam domain: Solution Design
Show explanation & topic
Correct answer: B. Salesforce documents mapping Nonprofit Cloud Fundraising objects into its data platform precisely so cross-system constituent data can be unified for segmentation and activation. That is the intended path for this requirement.
Why the other options are wrong: Nightly bulk copies into custom objects create a second source of truth and an ongoing deduplication burden. Manual spreadsheet merges do not scale and are immediately stale. Rebuilding two working platforms as custom applications is disproportionate to the requirement.
Exam domain: Solution Design
Show explanation & topic
Correct answer: A. The documented prerequisite path starts with the constituent model — Person Accounts and group memberships — then Data Processing Engine, then Actionable Segmentation, then Interaction Summaries and supporting features such as interest tags, record alerts and timeline.
Why the other options are wrong: Actionable Segmentation depends on Data Processing Engine, so it cannot come first. Interaction Summaries are not a universal precondition. And the order genuinely matters, because later features depend on earlier ones.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: C. Industries features, Nonprofit Cloud included, gate access behind permission set licenses. A permission set can only grant what the assigned licences allow, so a missing PSL produces exactly this symptom.
Why the other options are wrong: The Marketing User flag governs campaign management only. Object visibility does not depend on an overnight refresh. Granting System Administrator to solve a licensing gap is both wrong and a serious over-privilege.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: B. Enabling Person Accounts is a one-way door. The correct professional answer is to trial in a non-production environment and treat the production enablement as a documented architectural decision.
Why the other options are wrong: There is no disable switch, no record-count exemption, and no support-reversal window. Telling a customer otherwise sets up a painful surprise.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: D. Role hierarchy-based sharing for Interaction Summaries and Interactions is one of the documented Nonprofit Cloud setup steps, and it delivers exactly this pattern: private records that roll up the management chain.
Why the other options are wrong: Public Read/Write on Account exposes everything to everyone. Chatter posts are not a controlled record of donor interactions and follow different visibility rules. Separate orgs would make a unified constituent view impossible.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: A. Record alerts surface time-bound, high-visibility notices on a record; timeline presents related activity from multiple objects in one chronological view. Both are part of the documented Nonprofit Cloud setup path.
Why the other options are wrong: Validation rules only fire on save. Interest tags record affinities such as causes a donor cares about, not contact restrictions, and Actionable Segmentation builds lists rather than record views. A custom flag plus Chatter reinvents two standard features badly.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: C. The exam outline names address management alongside person accounts and relationship objects under stakeholder management, precisely because multiple addresses per constituent is a normal nonprofit requirement rather than an edge case.
Why the other options are wrong: A single address field cannot express seasonality. Hand-rolled field sets plus a month formula is fragile and duplicates a platform capability. Duplicating the constituent splits giving history and breaks deduplication.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: B. Relationship objects — Account Contact Relation for members in a household, plus Contact Contact Relation, Account Account Relation and Party Role Relation for other relationships — carry membership without overwriting the person's own record.
Why the other options are wrong: Repointing the Account field would destroy the individual constituent record in a Person Account model. Public groups are a sharing feature for users. A text list of names is unusable for reporting, segmentation or rollups.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: A. ContactContactRelation models a relationship between two people; AccountAccountRelation models a relationship between two accounts, such as a business account and a household account or a parent and subsidiary.
Why the other options are wrong: AccountContactRelation links a person to an organisation, which is neither case. PartyRelationshipGroup defines the group itself rather than a pairwise relationship. Opportunity Contact Role belongs to the sales data model.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: C. Nonprofit Cloud capabilities are documented as available in higher editions — Fundraising in Enterprise, Unlimited and Developer, Program Management in Enterprise and Unlimited, Volunteer Management narrower still. Edition is a gating question, not a detail to settle later.
Why the other options are wrong: Edition independence is false. Extra user licences do not change edition. And donated licence programmes provide a number of licences on eligible editions; they do not make every edition free or unnecessary to check.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: B. Person Accounts are not required for Grantmaking, so the plan works. But because they are strongly recommended for Fundraising and Program Management, and enabling them is irreversible, the decision and its future implications belong in the design record.
Why the other options are wrong: A is factually wrong. C ignores that a later Fundraising phase would face a constituent-model migration. D understates the impact: enabling Person Accounts later means converting existing contacts and revisiting integrations and reports.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: D. The documented prerequisite order puts Data Processing Engine before Actionable Segmentation for this reason. If DPE is missing or misconfigured, segmentation has nothing to run on.
Why the other options are wrong: There is no minimum record count for segmentation to function. Chatter is unrelated. The Marketing User flag governs campaign management, not segmentation.
Exam domain: Agentforce Nonprofit Setup
Show explanation & topic
Correct answer: C. Gift Entry exists for exactly this workload: a template controls which fields appear and what defaults apply, and a Gift Batch groups the entries so they can be checked and processed as a set.
Why the other options are wrong: A one-at-a-time screen flow is slower than the grid it would replace. Raw Data Loader inserts bypass the gift entry audit trail and the defaulting logic. A custom Visualforce page is a development project duplicating a shipped feature.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: B. Gift Entry records represent gifts created individually or in a batch before processing; afterwards they serve as an audit trail for the gift transactions that were created. That audit value is a good reason not to purge them casually.
Why the other options are wrong: They are not auto-deleted, they do not replace Gift Transaction as the transactional record, and they have nothing to do with campaign membership.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: D. Gift commitments support pausing and resuming a recurring gift, which preserves the donor's history and the reason for the change. Retention reporting depends on that continuity.
Why the other options are wrong: Deleting and recreating loses the commitment history and makes the donor look lapsed. A zero-value commitment is a workaround that corrupts projections. Marking transactions as refunded misstates the financial record, since no money was taken and nothing was returned.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: A. Soft credits exist to attribute influence to a person or organisation that is not the legal donor. The hard credit stays with the foundation, so revenue is counted once.
Why the other options are wrong: A duplicate transaction inflates income by $10,000. Changing the donor misstates who gave. Gift Tribute records honour or memorial dedications, which is a different concept entirely.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: C. Gift default designations cascade: campaign to commitment, commitment to the transactions generated from it. Configuring defaults at the right level is what stops staff having to designate every recurring payment by hand.
Why the other options are wrong: Inheritance does happen, it applies to the whole schedule rather than only the first payment, and it does not silently override a restricted designation with unrestricted.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: B. Nonprofit Cloud supports gift acknowledgements and tax receipts through document generation, which is why DocGenerationQueryResult appears among the Fundraising objects. Templates and data come from the records themselves.
Why the other options are wrong: An annual CSV mail-merge is manual, error-prone and leaves no record in Salesforce of what was sent. Hand-built Apex PDF generation duplicates a shipped feature. A self-service portal is a nice addition but does not discharge the obligation to issue receipts.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: A. Gift Tribute represents the details and status of an honour or memorial tribute attached to a gift, including whether the notification has been sent.
Why the other options are wrong: A soft credit would credit the deceased with influencing the gift, which is not the intent. Outreach source codes track appeals. Creating a designation per honouree would pollute the restricted-fund structure with hundreds of one-off entries.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: D. GiftRefund exists to represent a refund of a gift. Keeping the original transaction and the refund preserves the audit trail, which finance and auditors will expect.
Why the other options are wrong: Deleting or zeroing the transaction erases evidence that money was taken and returned. A negative transaction is a workaround that breaks reporting assumptions and bypasses the object designed for the purpose.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: B. Outreach source codes exist to track appeals and measure the effectiveness of a fundraising message, and outreach summary records aggregate the results of the outreach campaign. That is precisely a variant test.
Why the other options are wrong: Designations record where the money goes, not which message produced it. A text field on Contact records the last thing sent, not which appeal produced which gift. Gift commitments represent donor promises, not marketing variants.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: C. Benefit Assignment connects a participant and their programme enrolment to a benefit and tracks how much of it they should receive; Benefit Disbursement records when and how much was actually delivered.
Why the other options are wrong: Program Enrollment records joining the programme, and cohort membership groups participants; neither is a per-delivery record. Benefit and Benefit Type are definitions, not participant-specific records. The Gift chain is incoming donations.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: A. Benefit Schedule is the plan for delivering a benefit, Recurrence Schedule drives the repetition, and Benefit Session represents an instance of a planned delivery — which is what attendance is taken against.
Why the other options are wrong: Creating a Program per week destroys programme-level reporting. Eight date fields cannot record who attended which session. Campaigns are a marketing construct and give no benefit-delivery tracking.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: B. Program Cohort represents the participants of a cohort, and Program Cohort Member links programme enrollees to a given cohort — giving you intake-level reporting without fragmenting the programme.
Why the other options are wrong: A Program per intake multiplies configuration and breaks year-on-year programme reporting. A picklist is a workaround with no relationship to report through. Benefit record types describe what is delivered, not who joined when.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: D. A Care Plan is the instantiation of a care plan template for an individual, working toward specific goals. Goal definitions instantiate as goal assignments on the plan, which is what allows per-client tailoring from a standard starting point.
Why the other options are wrong: Goals in a description field cannot be tracked or reported. Action Plans generate task and document checklists and are a different feature from care planning. Impact Strategy is organisation-level outcome framing, not an individual service plan.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: A. Interactions and Interaction Summaries are part of the documented Nonprofit Cloud setup path precisely because structured meeting notes with attendees and controlled visibility are a core casework and major-gift requirement.
Why the other options are wrong: Chatter is collaboration, not a governed record, and follows different visibility rules. Personal calendar events do not capture discussion content or attendees in a reportable way. A single long text field on the enrolment cannot hold a series of dated meetings.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: C. Indicator Result holds the result of an indicator assignment for a time period. Indicator Performance Period supplies the period, calculation frequency and baseline against which that result is read.
Why the other options are wrong: Indicator Definition describes what is measured, not a measured value. Impact Strategy Assignment connects a strategy to an outcome. Outcome Activity is a junction between an outcome and an activity object.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: B. Grantmaking sites give applicants a self-service channel, ApplicationReview holds a review against an individual application, and ApplicationDecision records the final decision. Grantmaking sites are called out explicitly in the exam outline.
Why the other options are wrong: Email-to-Case loses structured application data and review history. A custom object plus a spreadsheet discards the shipped Grantmaking model and its reporting. Creating disbursements at submission promises money before a decision has been made.
Exam domain: Agentforce Nonprofit Feature Configuration
Show explanation & topic
Correct answer: D. FundingAward captures the approved award and its period, FundingDisbursement represents each payment made or scheduled, and FundingAwardRequirement represents a deliverable or milestone for an award or disbursement. Together they model a reporting-gated payment schedule.
Why the other options are wrong: A single disbursement misrepresents the payment schedule and the outstanding liability. Two awards make it look like two separate grants and break award-level reporting. A note in a description field is not a tracked, reportable obligation.
Exam domain: Agentforce Nonprofit Feature Configuration
Answered 0 of 50 questions. You can submit at any time.
How to Study for the Nonprofit Cloud Consultant Exam
Learn the object model as a set of chains, not a list
Nonprofit Cloud has a lot of standard objects, and memorising them alphabetically is wasted effort. Learn them as the chains the business actually runs: FundingOpportunity to IndividualApplication to FundingAward to FundingDisbursement; Program to ProgramEnrollment to BenefitAssignment to BenefitDisbursement; GiftCommitment to GiftCommitmentSchedule to GiftTransaction to GiftTransactionDesignation. Scenario questions almost always describe one link in a chain and ask which record carries the information.
Know what enabling something costs you
Setup questions like irreversible decisions. Person Accounts cannot be turned off once enabled and are unsupported alongside the Nonprofit Success Pack; Data Processing Engine has to be on before Actionable Segmentation will work; Volunteer Management is not available in every edition. For every prerequisite in the setup path, be able to say what breaks if you skip it and what you cannot undo afterwards.
Practise choosing between Industries Common Features
A large share of Solution Design questions is really one question repeated: given this requirement, is the answer an Action Plan, a Discovery Framework assessment, a Data Processing Engine definition, a record rollup definition, an OmniScript, or nothing at all because a standard object already does it? Build a one-line rule for each tool describing the shape of problem it solves, and test your rules against requirements you have met in real projects.
Get your hands on an org
Gift Entry grids, gift batches, gift commitment schedules and Grantmaking sites are much easier to reason about after you have clicked through them once. Salesforce offers Nonprofit Cloud trial and Trailhead Playground environments; configuring one recurring gift end to end will answer several exam questions on its own.