Mar-2026 Download Free Latest Exam NP-Con-102 Certified Sample Questions [Q43-Q67]

Mar-2026 Download Free Latest Exam NP-Con-102 Certified Sample Questions

Prepare for your exam certification with our NP-Con-102 Certified Salesforce

NEW QUESTION # 43
A nonprofit is migrating from a legacy donor management database. The database has donor contact information, donation history, and payment information. How should the consultant load the data from the database using a single file to create the related records?

• A. Workbench
• B. Data Loader
• C. Data Import Wizard
• D. NPSP Data Importer

Answer: D

Explanation:
When migrating data into the Nonprofit Success Pack (NPSP), the most efficient and robust tool is the NPSP Data Importer. This tool was specifically built to handle the "multi-object" nature of nonprofit data in a single pass.
Why NPSP Data Importer is the Correct Choice:
* Single File Processing: Standard Salesforce tools like Data Loader or the Data Import Wizard usually require separate files and separate "upserts" for each object. You would have to import Accounts, then export the IDs, then import Contacts, then export those IDs, then import Opportunities.
* Complex Logic in One Row: The NPSP Data Importer allows you to put the Contact Name, the Household address, and the Donation Amount on the same row of a CSV file.
* Automatic Relationship Management: When you process the file, the Importer automatically:
* Creates or finds the Contact.
* Automatically creates the Household Account.
* Creates the Opportunity (Donation) and links it to the Account.
* Creates the Payment record (if payment info is included).
* Handles GAU Allocations and Campaign Memberships.
* Dry Run Capability: It includes a "Dry Run" feature that validates the data and checks for duplicates before any actual records are created, which is vital for a clean migration.
While Workbench and Data Loader are powerful technical tools, they lack the specific NPSP business logic that makes the NPSP Data Importer the fastest and safest way to move a legacy database into Salesforce using a single flat file.

NEW QUESTION # 44
A nonprofit wants to convert from Legacy Recurring Donations to Enhanced Recurring Donations. What are two considerations the nonprofit should take into account before making the switch? (Choose 2)

• A. Enhanced Recurring Donations introduces a new custom object.
• B. Reverting to Legacy Recurring Donations is unsupported.
• C. Data Loader is required to revert to Legacy Recurring Donations.
• D. All existing integrations should be reviewed for compatibility.

Answer: B,D

Explanation:
The move from Legacy Recurring Donations to Enhanced Recurring Donations (ERD) is a significant architectural upgrade in NPSP. While ERD offers better performance and more flexible scheduling, it changes how data is processed and stored.
Key Considerations:
* Integration Compatibility (A): Enhanced Recurring Donations changes the underlying logic of how installments (Opportunities) are created and managed. If the nonprofit uses third-party apps (like an external payment gateway or a custom web form) that rely on the legacy npe03__Recurring_Donation__c fields or the old "Monthly" vs. "Custom" picklist values, those integrations may break. A consultant must perform a thorough audit of all APIs and managed packages before the conversion.
* No Revert Path (D): This is a "one-way door." Salesforce documentation explicitly states that reverting to Legacy Recurring Donations is unsupported once the upgrade process has been completed. The conversion process modifies the database schema and migrates records in a way that cannot be easily undone. Therefore, testing in a full sandbox is a non-negotiable prerequisite.
Clarifying Other Points:
* New Custom Object (Option B): This is incorrect. Enhanced Recurring Donations actually uses the same custom object as the legacy version (npe03__Recurring_Donation__c), but it utilizes new fields, new page layouts, and a completely different set of Apex triggers and batch jobs.
* Data Loader (Option C): Since the process is unsupported, Data Loader is not a viable or recommended way to "revert" the complex architectural changes.

NEW QUESTION # 45
A case manager wants to assign a group of services to a client. What should the consultant ensure is configured prior to the case manager using the Case Plan Wizard?

• A. A Program with Action Item Templates
• B. A Program with Goals and Action Item Templates
• C. A new Case Plan
• D. A Program with Goals

Answer: B

Explanation:
The Case Plan Wizard in Nonprofit Cloud Case Management is a tool that allows caseworkers to quickly build a customized care plan for a participant. To make this "wizard" efficient and automated, the underlying
"templates" must be set up beforehand.
Required Pre-configuration:
To "assign a group of services" effectively through the wizard, the consultant must ensure that the Program record is populated with:
* Goals: These are the objectives the client wants to reach. In the wizard, the caseworker can select from these pre-defined goals rather than typing them from scratch.
* Action Item Templates: These are the specific tasks or "steps" required to reach a goal. By creating Action Item Templates and linking them to a Goal within a Program, the consultant enables the
"grouping" logic. When a caseworker selects a Goal in the wizard, the associated Action Items automatically appear as suggested tasks.
Workflow for the Consultant:
* Navigate to the Program record.
* Use the Goals related list to create standard goals for that program.
* Use the Action Item Templates related list to define the repeatable steps for those goals.
* Ensure the Case Plan Wizard component is added to the Contact or Case record page.
Why other options are insufficient:
* Option A and B: If you only have Goals or only have Action Items, the wizard loses its primary value of providing a "ready-made" plan for the caseworker.
* Option D: A "New Case Plan" is the result of using the wizard, not a prerequisite for the wizard's configuration.

NEW QUESTION # 46
A nonprofit organization has identified that some donations should be directed to one or more program areas in the financial accounting software. This information is identified when an Opportunity is being solicited. In the Nonprofit Cloud Fundraising Data Model, which object should be used to record the donor's intent during solicitation?

• A. Gift Default Designation
• B. Gift Designation
• C. Gift Transaction Designation

Answer: C

Explanation:
In the Nonprofit Cloud (NPC) Fundraising model, tracking donor intent-where the money is "designated" to go-is a core requirement for financial transparency. It is important to distinguish between the "Fund" and the "Allocation."
* Gift Designation (The Fund): This object represents the master fund or program area (e.g., "Clean Water Initiative"). It is a static record that holds rollup data for that specific fund.
* Gift Transaction Designation (The Allocation): This is the junction object that records the donor's specific intent for a particular gift. When a consultant identifies that a donation needs to be split across multiple programs, they create multiple Gift Transaction Designation records linked to a single Gift Transaction. This object stores the specific amount or percentage of that transaction that should be credited to a particular program.
Workflow During Solicitation:
During the solicitation of an Opportunity, the consultant or gift officer captures the donor's intent. Even if the money has not yet arrived, the data model for NPC Fundraising (v59 and higher) anticipates that this intent will eventually live on the Gift Transaction Designation record. When an Opportunity is "Won" and converted into a Gift Transaction, the system uses the metadata captured during solicitation to populate these designation records.
Why other options are incorrect:
* Gift Default Designation (Option C): These are used at the Campaign or Org-wide level to define where unrestricted or "unmarked" gifts should go by default. They are templates for inheritance rather than the record that tracks a specific donor's intent for a specific solicitation.
* Gift Designation (Option B): As mentioned, this is the master definition of the fund, not the record of a specific allocation instance.

NEW QUESTION # 47
In the NPSP Data Import Template, the Account fields should contain which two types of information?
Choose 2 answers

• A. Contact's address-related data
• B. Business-related data
• C. Household-related data
• D. Contact's employer-related data

Answer: B,C

Explanation:
The NPSP Data Import Template is a "flat file" structure designed to populate multiple objects in the NPSP data model simultaneously. Because NPSP uses a "Household-centric" model but also supports corporate and foundation giving, the Account fields in the template serve a dual purpose depending on the record being imported.
* Business-related data (A): If the nonprofit is importing donations from a corporation, foundation, or local business, the "Account" fields in the template (such as Account Name, Account Phone, etc.) are used to create or match an Organization Account. This allows the consultant to track the entity's history and give them "Hard Credit" for their donations.
* Household-related data (B): If the nonprofit is importing individual donors, the Account fields are used to define the Household Account. For example, if the template specifies "The Smith Household" in an Account field, NPSP logic will use that data to name the household record it creates for the associated contacts.
* Address Logic (C): While addresses are part of an account, in the NPSP Data Importer, address data is typically handled by specific Address fields that NPSP then intelligently routes to the Household or the Contact record.
* Employer Logic (D): Tracking an employer is usually handled via Affiliations. While the employer is an Account, the template has specific "Home" vs. "Work" logic to handle these relationships separately from the primary account being created.
In summary, the Account columns in the CSV template are the landing spot for any data related to the
"Institutional" or "Household" entity that owns the donation or contains the contact.

NEW QUESTION # 48
A human services nonprofit needs to track client goals and action items related to those goals. The nonprofit is unsure whether Program Management Module alone will meet its requirements. The nonprofit is considering whether to implement Nonprofit Cloud Case Management. What should the consultant discuss with the nonprofit?

• A. Case Management has a custom object for tracking goals.
• B. Case Management requires Experience Cloud licenses.
• C. Program Management Module has custom objects for calendars and activities.
• D. Program Management Module can track Case Plans and Action Items.

Answer: A

Explanation:
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.

NEW QUESTION # 49
A nonprofit on Unlimited Edition uses direct mail extensively as a fundraising channel. The nonprofit wants to automate the search for duplicate contact records. What should the consultant recommend implementing?

• A. Scheduled Apex Jobs
• B. Duplicate Jobs
• C. Duplicate Rules
• D. Matching Rules

Answer: B

Explanation:
While Duplicate Rules and Matching Rules are essential for preventing new duplicates from being created, they do not help with a database that already contains existing duplicates (which is common after large direct mail imports).12 The Solution for "Auto13mating the Search":
On Unlimited Edition, Salesforce provides a feature called Duplicate Jobs.
* Scanning the Database: Unlike rules that fire during a save, a Duplicate Job runs a scan across the entire existing database (or a specific segment) to find existing duplicate records based on your Matching Rules.
* Reporting: Once the job completes, it generates a list of "Duplicate Record Sets." This allows the nonprofit's data integrity team to review and merge records in bulk.
* Use Case: For a direct mail organization, running a Duplicate Job before a large mailing ensures they aren't wasting money by sending two identical letters to the same household.
Why other options are incorrect:
* Duplicate/Matching Rules (Options A & C): These act as "gatekeepers" during data entry. They find duplicates only when a record is created or edited; they do not proactively "search" the existing database.
* Scheduled Apex (Option D): This is a custom coding solution. A consultant should always recommend native, declarative features like Duplicate Jobs before suggesting custom code.

NEW QUESTION # 50
A Household Account has Contacts with Affiliations, Relationships, and Closed/Won donations associated with it. What is the outcome when a system admin attempts to delete this Household Account record?

• A. Since Closed/Won donations are associated with the Account record, an error message displays.
• B. The Household Account record and its standard related records are deleted.
• C. The Household Account record and its standard related records remain.
• D. Since Affiliations and Relationships are associated with the Contacts in this Account, an error message displays.

Answer: A

Explanation:
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.

NEW QUESTION # 51
A Nonprofit Cloud Administrator enables Automatic Person Account Mailing Address Synchronization.
Which object's related list should be added to Person Account record pages to see additional addresses?

• A. Location
• B. Contact Point Address
• C. Address

Answer: B

Explanation:
The Nonprofit Cloud has adopted the standard Salesforce Information Model for address management. In this model, the "Mailing Address" fields on the Person Account are merely a simplified view of a more robust underlying record.
When Automatic Person Account Mailing Address Synchronization is enabled, the system looks for the Contact Point Address (CPA) record marked as Is Primary and mirrors its values onto the Account header.
Managing Multiple Addresses:
* Contact Point Address Object: This is the "source of truth" for all locations associated with a person.
* The Related List: To manage a donor who has a "Home," "Office," and "Summer House" address, the consultant must add the Contact Point Addresses related list to the Person Account page layout.
* Adding Records: From this related list, users can create new addresses, specify the Address Type, and set Seasonal Dates.
* Synchronization: If a user changes the "Primary" flag from the Home CPA record to the Office CPA record, the synchronization feature will automatically update the Account's standard mailing fields to reflect the Office information.
Why other options are incorrect:
* Location (Option A): This object is part of Field Service or Facilities Management and is used for physical sites/buildings, not for constituent mailing addresses.
* Address (Option C): While there is a generic "Address" object, NPC specifically utilizes the Contact Point Address record, which is part of the "Contact Point" family of objects (alongside Email and Phone) used for communication preferences.

NEW QUESTION # 52
An annual fund coordinator wants to create a report that identifies which individual donors have yet to make a gift toward the Annual Fund Campaign this year. It is important that the annual giving coordinator avoids soliciting any individuals who are attending an upcoming gala. The nonprofit uses Campaigns to track event attendance. What should a consultant add to the report to exclude gala attendees?

• A. Summary formula
• B. Cross filter
• C. Filter logic
• D. Bucket field

Answer: B

Explanation:
This is a "Who Has NOT" reporting requirement, which is the primary use case for Cross Filters in Salesforce.
How to build this report:
* Base Report: Create a report of Contacts (or "Contacts with Opportunities").
* Annual Fund Filter: Set the standard report filters to show only those who have $0 in giving for the current year.
* The Exclusion (Cross Filter): Click the "Filters" dropdown and select Add Cross Filter.
* Configuration: * Set the filter to: Contacts WITHOUT Campaign Members.
* Add a sub-filter to the cross filter: Campaign Name EQUALS [Upcoming Gala Name].
* Result: The report will now list only people who are donors but are not currently registered for the Gala.
Why other options are incorrect:
* Filter Logic (Option A): This is used for "AND/OR" statements between existing fields (e.g., 1 AND (2 OR 3)). It cannot easily look "across" to the Campaign Member object to check for the absence of a record.
* Summary Formula (Option C) and Bucket Field (Option D): These are used for calculating or grouping data that is present in the report; they cannot be used to exclude records based on their relationship to other objects.

NEW QUESTION # 53
A consultant is working on a data migration to NPSP that includes tens of millions of records across many objects. The migration needs to take place over a weekend to minimize system downtime. What should the consultant recommend?

• A. Bulk API
• B. Data Import Wizard
• C. SOAP API
• D. NPSP Data Import

Answer: A

Explanation:
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.

NEW QUESTION # 54
A nonprofit has engaged a consultant to help export detailed accounting transactions to its existing external financial system using Accounting Subledger Starter Edition. The nonprofit requires export of all pledges when they are booked. Which solution should the consultant recommend?

• A. Upgrade to Accounting Subledger Growth Edition.
• B. Set "Pledged" stage to "Finalized" in Stage to State Mapping.
• C. Use Flow to create Ledger Entries on Opportunity update.
• D. Set "Pledged" stage to "Committed" in Stage to State Mapping.

Answer: D

Explanation:
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.

NEW QUESTION # 55
A volunteer with a nonprofit works at Universal Containers. The volunteer is recorded in Salesforce as part of the Household's account record, but Universal Containers needs to be entered into the Salesforce system. How should a consultant track the volunteer's relationship with Universal Containers?

• A. Create a Universal Containers Organization Account and create a Relationship record between the volunteer and Universal Containers.
• B. Create a Lead for the volunteer at Universal Containers and create an Affiliation record between the volunteer Lead and Universal Containers.1
• C. Create a Lead for the volunteer at Universal Containers and create a Relationship record between the volunteer Lead and the volunteer Contact.2
• D. Create a Universal Containers Organization Account a3nd create an Affiliation record between the volunteer and Universal Containers.

Answer: D

Explanation:
In NPSP, there is a clear distinction between how we track "people to people" and "people to organizations."
* People to Organizations (Affiliations): When a Contact (the volunteer) has a professional or community connection to an organization (Universal Containers), the Affiliation object is used. An Affiliation is a junction record that links a Contact record to an Account record with an 'Organization
' record type.
* People to People (Relationships): The Relationship object is used exclusively for person-to-person ties (e.g., "Spouse," "Coworker," or "Father"). You do not use the Relationship object to link a person to a business.
The Solution:
To track this volunteer's employment or connection to Universal Containers:
* Step 1: Create an Account record for "Universal Containers" and ensure its record type is
"Organization."
* Step 2: Create an Affiliation record.
* Step 3: On the Affiliation record, link the volunteer's Contact record to the Universal Containers Account record.
* Step 4: Specify the Role (e.g., Employee) and mark it as the Primary Affiliation if this is their main employer.
Using Leads (Options A & B) is incorrect because the volunteer is already an established "Contact" in the system; creating a Lead would create a duplicate record and fragment the data history.

NEW QUESTION # 56
A nonprofit organization wants to enable staff to track detailed notes of conversations with clients. Some of the notes will be associated to multiple individuals. Which Nonprofit Cloud object should the consultant configure?

• A. Action Plans
• B. Outreach Summaries
• C. Interaction Summaries

Answer: C

Explanation:
The Interaction Summary object is a cornerstone of the modern Nonprofit Cloud, borrowed from the Financial Services Cloud architecture to support professional-grade relationship management.
One of the primary advantages of Interaction Summaries over standard Salesforce "Notes" or "Activities" is the ability to relate a single set of notes to multiple participants and entities.
Configuration and Usage:
* The Interaction: Represents the meeting itself (the "Event").
* The Interaction Summary: This is the record where the detailed, often sensitive, notes are stored.
* Multiple Individuals: Using the Interaction Participant related list, a consultant can link the summary to multiple Person Accounts. For example, if a caseworker meets with a mother and her two children, a single Interaction Summary can be created and then related to all three individual records.
This ensures that the meeting notes appear on the "Timeline" and "Related Lists" for every person involved without the caseworker having to copy and paste the notes three times.
* Confidentiality: Because these summaries often contain sensitive case data, they are designed to work with Compliant Data Sharing (CDS). This allows the consultant to ensure that while the note is linked to multiple people, only staff with the correct "Participant Role" can actually read the contents.
Why other options are incorrect:
* Action Plans (Option B): These are used for tracking a series of tasks or checklists (e.g., "Steps to complete intake"). They are not a note-taking or conversation-tracking feature.
* Outreach Summaries (Option C): This object is used in Fundraising to roll up the performance of a specific marketing campaign (e.g., total gifts and donor count from a direct mail appeal); it has no relation to client conversations or case notes.

NEW QUESTION # 57
A nonprofit organization wants to customize the Gift Entry process in Nonprofit Cloud. Which features can be cloned and used in place of the standard version?

• A. Fundraising Flows
• B. Fundraising Invocable Actions
• C. Fundraising Lightning Web Components

Answer: A

Explanation:
The Gift Entry process in Nonprofit Cloud is designed to be flexible and extensible. Salesforce provides a set of standard Screen Flows that handle the user interface and logic for entering single gifts or batches of gifts.
For a consultant, the primary way to customize the "user experience" of gift entry without writing custom code is to leverage Salesforce Flow.
Customization Steps:
* Locate Standard Flows: The consultant goes to Setup > Flows and finds the standard templates provided for Fundraising (e.g., the flow that powers the "New Gift" button).
* Clone the Flow: Because standard flows provided by Salesforce are often protected or intended to be templates, the consultant clones the flow to create a "Save As" version.
* Modify Logic and Fields: In the cloned flow, the consultant can add custom validation logic, remove unnecessary fields to simplify the UI for data entry clerks, or add a specific step to capture "Custom Metadata" unique to the organization's needs.
* Activate and Override: Once the custom flow is active, the consultant updates the Action Buttons or Lightning Pages to point to the new custom flow instead of the standard one.
Why other options are incorrect:
* Invocable Actions (Option A): These are modular pieces of Apex code that perform specific tasks (like "Calculate Tax"). While they can be used inside a flow, they cannot be "cloned" in the same way a flow can; they are fixed logic provided by the system.
* Lightning Web Components (Option C): While LWCs can be custom-built, the standard NPC components (like the Gift Entry table) are managed by Salesforce and are not "clonable" by a consultant in the Setup menu. Cloned Flows provide the highest degree of declarative customization for the gift entry workflow.

NEW QUESTION # 58
A nonprofit organization wants grant seekers to be able to add collaborators in Experience Cloud to help complete grant applications. What should the organization configure in Nonprofit Cloud for Grantmaking?

• A. Compliant Data Sharing
• B. Permission sets
• C. Group Membership

Answer: A

Explanation:
In the Grantmaking lifecycle, transparency and collaboration are key, especially during the application phase. A lead applicant (grant seeker) often needs to bring in subject matter experts, accountants, or board members to help draft specific sections of a complex funding proposal.
To enable this within an Experience Cloud portal, Salesforce utilizes Compliant Data Sharing (CDS). CDS allows for granular, record-level sharing that can be managed directly by end-users (the grant seekers) rather than requiring an administrator to manually adjust sharing rules or public groups every time a collaborator is added.
Step-by-Step Configuration for the Consultant:
* Enable CDS: The consultant must first enable "Compliant Data Sharing" in the Setup menu for the relevant objects, such as Individual Application or Funding Award.
* Define Participant Roles: Roles like "Collaborator," "Reviewer," or "Signatory" are defined. Each role is assigned a specific access level (Read or Read/Edit).
* Add Related Lists: The consultant adds the "Participants" related list to the page layout used in the Grantmaking Portal.
* User Empowerment: Once configured, a grant seeker can navigate to their application in the portal, click "Add Participant," and search for other users within their organization to grant them access to that specific application.
This feature ensures that sensitive financial and program data is shared only with authorized individuals, maintaining a high level of security and "compliance" while still promoting the collaborative effort necessary for high-quality grant applications. Permission sets (Option C) provide the broad ability to use the portal, but CDS provides the specific mechanism for peer-to-peer record sharing.

NEW QUESTION # 59
A consultant is assisting a nonprofit in its data integration and mapping between two systems. The consultant is unsure when a particular field was added to NPSP. Where can the consultant find the NPSP version number for the field in question?

• A. NPSP package details
• B. Custom field definition detail
• C. Schema Builder
• D. NPSP Data Dictionary

Answer: D

Explanation:
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.

NEW QUESTION # 60
A nonprofit wants to record the most recent Opportunity close date on Contact records. The nonprofit expects the field on the Contact to be overwritten every time a new Opportunity meets the criteria. Which feature should the consultant use to meet this requirement?

• A. Roll-up summary field
• B. AppExchange app
• C. Customizable rollups
• D. Formula field

Answer: C

Explanation:
In NPSP, aggregating data from child Opportunity records to the parent Contact or Account record is handled by the Rollup engine. While there are several ways to do this in Salesforce, Customizable Rollups are the standard NPSP tool for this requirement.
Why Customizable Rollups (C) are the best fit:
* Cross-Object Support: Standard Roll-up Summary fields (Option B) only work if there is a Master- Detail relationship. Because the relationship between Opportunities and Contacts in NPSP is technically a Lookup relationship (managed through Opportunity Contact Roles), standard roll-ups cannot be used.
* Logic and Filtering: Customizable Rollups allow the consultant to define specific "Filter Groups." For example, you can set the rollup to only look at "Closed/Won" donations and ignore "In-Kind" gifts.
* Operation Types: To get the "most recent" date, the consultant sets the rollup operation to MAX. The system will look at all qualifying Opportunities, find the one with the latest (highest) date, and write that date to the target field on the Contact.
* Automation: Every time a new Opportunity is added or updated, NPSP's nightly batch (or real-time triggers) will re-calculate the value. If a new gift arrives with a more recent date, the old value on the Contact will be overwritten automatically.
Formula fields (Option A) cannot be used because they can only pull data up from a parent to a child, not aggregate multiple child records into a single parent field.

NEW QUESTION # 61
For a Salesforce implementation project, what is the order of phases in a project lifecycle?

• A. Initiate, Plan, Execute, Monitor and Control, Close
• B. Plan, Initiate, Execute, Close, Monitor and Control
• C. Plan, Initiate, Execute, Monitor and Control, Close

Answer: A

Explanation:
A consultant must follow a structured project management methodology to ensure a Nonprofit Cloud implementation is delivered on time and within budget. The standard lifecycle, aligned with the Project Management Institute (PMI) and Salesforce best practices, consists of five distinct phases.
* Initiate: This is the "Discovery" and "Alignment" phase. The consultant identifies the key stakeholders, defines the high-level project goals (the "Why"), and secures the project charter. For a nonprofit, this often involves the "Power of Us" application and licensing verification.
* Plan: In this phase, the consultant defines the "How." This includes gathering detailed requirements, creating the Solution Design Document (SDD), mapping the data migration strategy, and finalizing the project schedule.
* Execute: This is the "Build" phase. The consultant and developers configure the Nonprofit Cloud (Objects, Flows, DPE, etc.), perform data migrations, and build any necessary integrations.
* Monitor and Control: This phase runs concurrently with Execute. The consultant tracks progress against the plan, manages "Scope Creep," performs User Acceptance Testing (UAT), and handles quality assurance. It ensures that the project doesn't deviate from the organization's mission-critical needs.
* Close: The final phase involves the formal "Go-Live," end-user training, handing over documentation to the nonprofit's admin, and conducting a "Lessons Learned" session.
Why Option B and C are incorrect: You cannot "Plan" (Phase 2) effectively until you have "Initiated" (Phase 1) the project and identified who the stakeholders are and what the project charter entails. Furthermore,
"Monitor and Control" must happen before you can officially "Close" the project.

NEW QUESTION # 62
A nonprofit organization is using Care Plans in Nonprofit Cloud to manage interactions with clients. The organization has standard Care Plan Templates set up but must often add additional elements to a Care Plan based on a client's specific needs. What can be manually added directly to a Care Plan?

• A. Goal Assignments and Benefit Assignments
• B. Document Checklists and Document Templates
• C. Programs and Program Enrollments

Answer: A

Explanation:
In Nonprofit Cloud Case Management, a Care Plan is the central roadmap for a client's journey toward a specific outcome. While Care Plan Templates provide a standardized starting point, the philosophy of person-centered care requires that these plans be customizable to the unique circumstances of each participant.
A Care Plan is structurally composed of two primary "actionable" building blocks:
* Goal Assignments: These represent the milestones the client is working toward (e.g., "Secure Stable Housing" or "Complete GED"). While a template might include five standard goals, a caseworker can manually add a sixth Goal Assignment that is unique to that client's specific barriers.
* Benefit Assignments: These are the services or resources provided to help the client achieve their goals (e.g., "Rental Assistance" or "Weekly Tutoring"). A caseworker can manually link additional Benefits to a Care Plan to ensure the participant has the specific support they need.
Step-by-Step Customization Workflow:
* Template Application: The caseworker begins by applying a standard template, which populates the Care Plan with a set of pre-defined goal and benefit assignments.
* Assessment Review: After a Dynamic Assessment, the caseworker identifies an unmet need.
* Manual Entry: Within the Care Plan interface, the caseworker clicks "New" on the Goal Assignment related list to create a custom goal. They then do the same for Benefit Assignments to link the client to a specific service.
* Linking: The caseworker can then link the manual Benefit Assignment to the manual Goal Assignment to show exactly how that service contributes to the client's progress.
Option B is incorrect because Programs and Program Enrollments are the broader containers that a client is part of. While a Care Plan exists within the context of an enrollment, you don't "add an enrollment" to a plan; rather, the plan is a subset of the enrollment. Option A refers to compliance and document tracking, which are managed via Action Plans, not the core clinical/social service logic of the Care Plan itself.

NEW QUESTION # 63
How does Salesforce support donor cultivation and stewardship strategies for nonprofit organizations?

• A. By enabling nonprofit organizations to track interactions with donors, create and manage campaigns, and log gifts
• B. By centralizing grant application, approval, and reporting processes for outbound grants
• C. By automating financial ledger reporting for various revenue streams, including grants and in-kind donations

Answer: A

Explanation:
Donor cultivation and stewardship are the core pillars of a nonprofit's fundraising strategy. In the modern Nonprofit Cloud (NPC), Salesforce provides a unified platform to manage the entire donor lifecycle-from the initial "prospect" phase to long-term "stewardship." The Stewardship Framework in NPC:
* Tracking Interactions: Salesforce allows development officers to log every "touchpoint" with a donor.
Using the Interaction and Interaction Summary objects, staff can record detailed notes from discovery calls, coffee meetings, or site visits. This historical record ensures that as staff change, the relationship with the donor remains consistent and informed.
* Campaign Management: Cultivation often begins with targeted outreach. NPC uses the Campaign object and Outreach Source Codes to segment donors based on their interests (tracked via Interest Tags) and engage them with specific appeals. By tracking which campaigns a donor responds to, the organization can tailor future communications to the donor's proven interests.
* Gift Logging and Recognition: Stewardship relies on timely and accurate acknowledgment. When a gift is logged via Gift Entry, the system immediately updates the Donor Gift Summary. This allows staff to see the donor's impact at a glance. Features like OmniStudio Document Generation then automate the creation of personalized thank-you letters, which are a vital part of stewardship.
* Moves Management: Using Action Plans, a consultant can build standardized "stewardship tracks." For example, after a major gift is received, the system can automatically assign tasks for the Executive Director to make a thank-you call and for the Program Director to send a 6-month impact report.
While Grantmaking (Option B) and Accounting Subledger (Option C) are important operational features, they do not define the relational strategy of "cultivation and stewardship." Option A correctly identifies the tools used by fundraisers to build and maintain the emotional and financial connection between the donor and the mission.

NEW QUESTION # 64
A consultant wants to view an interactive graph of a donor's key relationships. Which feature available in Nonprofit Cloud should the consultant use?

• A. Flexcard
• B. Contact Profile
• C. Actionable Relationship Center

Answer: C

Explanation:
The Actionable Relationship Center (ARC) is the premier visualization tool in Salesforce Nonprofit Cloud for mapping complex constituent webs. Unlike a standard related list, which shows data in a flat table format, ARC provides a dynamic, multi-level graph that allows fundraisers and case managers to explore the connections between people, households, and organizations.
Key Capabilities for a Consultant:
* Visual Hierarchy: ARC displays nodes representing records (e.g., a Donor, their Spouse, their Employer, and a Foundation board they sit on). Each node can be expanded to show further related records, such as the Foundation's recent grants or the Spouse's individual contact details.
* Standard and Custom Relationships: It natively supports the Party Relationship Model used in NPC, including Account-Account Relationships and Contact-Contact Relationships. This allows for the visualization of both professional affiliations and personal family ties in one view.
* Direct Interaction: It is "Actionable" because users can perform tasks directly from the graph. A consultant can configure the graph so a gift officer can create a new "Follow-up Task" or "Note" on a related relative's record without ever leaving the primary donor's page.
* Customization via Templates: Consultants can build custom ARC graphs using the ARC Graph Builder in Setup. You can choose which objects appear, what fields are shown in the side panel when a node is clicked, and even add filters to show only "Active" relationships.
While Flexcards (Option A) are used to display data visually, they are generally used for summarizing record fields rather than interactive relationship mapping. The Contact Profile (Option B) is a data storage object for wealth and personal attributes but does not provide the interactive, spider-web style graph that characterizes the ARC experience.

NEW QUESTION # 65
The development director at a nonprofit needs to track grant lifecycles using NPSP, including assigning actions to staff members, tracking applications, reporting deadlines, and summarizing the total amount awarded with payments. How should the consultant model payments, applications, reporting deadlines, and actions in NPSP for the grant seeking institution?

• A. Payments = Recurring Donations with Opportunities; Applications = Deliverables; Reporting deadlines
  = Deliverables; Actions = Activities
• B. Payments = Opportunities with Payments; Applications = Deliverables; Reporting deadlines = Deliverables; Actions = Activities
• C. Payments = Opportunities with Payments; Applications = Activities; Reporting deadlines = Activities

Answer: B

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.

NEW QUESTION # 66
A Nonprofit Cloud consultant is troubleshooting Accounting Subledger records that are not being created as expected. What should the consultant use to see which jobs have run recently and whether there have been any errors?

• A. Scheduled Jobs
• B. Monitor Workflow Services
• C. Event Monitoring Analytics App

Answer: B

Explanation:
In the modern Nonprofit Cloud (NPC) architecture, high-volume and complex data processes-such as the generation of financial records for the Accounting Subledger-are managed by the Industries Common Features framework.
When a consultant is troubleshooting why records are not being created, they must look beyond standard Salesforce "Scheduled Jobs" and into the specialized monitoring tools built for Industry Clouds. The Monitor Workflow Services (accessible via the "Industries Service Excellence" or "Monitor Workflow" setup areas) is the central dashboard for tracking the health of these automated processes.
How to Use Monitor Workflow Services for Troubleshooting:
* Accessing the Monitor: The consultant navigates to Setup and searches for Monitor Workflow Services.
* Identifying the Job: The consultant looks for entries related to the Accounting Subledger or the Data Processing Engine (DPE) jobs that power the subledger logic.
* Analyzing Run History: The tool displays a list of recent executions, including the Start Time, End Time, and Status (e.g., Success, Failed, or Completed with Errors).
* Drilling into Errors: If a job fails, the consultant can click on the specific run ID to view the error logs. This provides granular detail, such as "Record Lock Contention," "Validation Rule Violation," or
"Missing Required Mapping," which explains why the financial records were not generated.
This tool is essential because NPC's Subledger often relies on Batch Management and DPE. These processes run asynchronously in the background. Standard Scheduled Jobs (Option A) only show that the "trigger" fired, not whether the internal industry logic successfully completed its task. Monitor Workflow Services provides the "end-to-end" visibility required for a consultant to ensure the nonprofit's financial data is accurately flowing from Fundraising into the subledger.

NEW QUESTION # 67
......

Free Salesforce NP-Con-102 Exam 2026 Practice Materials Collection: https://www.exam4free.com/NP-Con-102-valid-dumps.html

NP-Con-102 Exam Info and Free Practice Test All-in-One Exam Guide Mar-2026: https://drive.google.com/open?id=14Ie5xZIQ7z0rcRv2q9C2PEHe9gZqsYL8