[May-2026] Use Real NP-Con-102 Dumps Free Sample Questions and Practice Test Engine [Q30-Q45]

[May-2026] Use Real NP-Con-102 Dumps Free Sample Questions and Practice Test Engine

Pass Salesforce NP-Con-102 exam - questions - convert Tets Engine to PDF

NEW QUESTION # 30
A user has been assigned the System Administrator Profile in Nonprofit Cloud. The user discovers that they cannot see any Nonprofit Cloud for Fundraising objects. What is a possible cause of this issue?

• A. The custom Tabs have not been created for the Fundraising objects.
• B. The Permission Set License is unassigned.
• C. The Sharing Rules are missing for the Fundraising objects.

Answer: B

Explanation:
One of the most common configuration hurdles in Nonprofit Cloud is understanding the "Two-Key" access model. Unlike standard Sales or Service Cloud, where a Profile can grant access to almost any object, Industry Clouds (like NPC) require a Permission Set License (PSL) to be assigned before the objects even become "visible" or "available" in the system's schema for that user.
The "Two-Key" Access Model:
* The First Key (Permission Set License): The PSL "unlocks" the feature set at the organization level for a specific user. For Fundraising, the user must be assigned the Nonprofit Cloud Fundraising PSL.
Without this, the Fundraising objects (like Gift Transaction) literally do not exist from that user's perspective, even if they are a System Administrator.
* The Second Key (Permission Set): Once the license is assigned, the user then needs a Permission Set (e.g., "Fundraising Access") to grant the actual CRUD (Create, Read, Update, Delete) permissions.
Step-by-Step Resolution for a Consultant:
* Navigate to Setup > Users.
* Open the user record for the System Administrator.
* Scroll to the Permission Set License Assignments related list and click Edit Assignments.
* Locate and check the box for Nonprofit Cloud Fundraising (and any other relevant industry licenses like Nonprofit Cloud Grantmaking).
* Once the PSL is saved, the Admin will then be able to assign themselves the necessary Permission Sets to see and manage the Fundraising objects.
Option A is incorrect because Sharing Rules control which records you see, not whether the object itself is visible. Option B is incorrect because tabs are easily accessible via the App Launcher; if the objects are missing from the "All Objects" list, it is a licensing and permissioning issue, not a tab configuration issue.

NEW QUESTION # 31
A nonprofit receives a donation from a family foundation. What should the consultant recommend to ensure the donation is reflected on the family's household record?

• A. Use Account Soft Credits to credit the household.
• B. Add an additional Account lookup field on the Opportunity for the household.
• C. Add an Account lookup field on the Payment for the Opportunity for the household.
• D. Use a GAU Allocation to credit the donation to the household.

Answer: A

Explanation:
In NPSP, we must distinguish between "Hard Credit" (legal ownership) and "Soft Credit" (influence
/relationship). When a family foundation (a Business Account) gives a donation, the Foundation gets the Hard Credit. However, the organization wants the Household Account (the family themselves) to receive credit for that gift in their "Total Giving" history.
The Solution: Account Soft Credits:
* Hard Credit: The Opportunity is created with the Family Foundation Account in the Account Name field. This is the legal donor.
* Soft Credit: To reflect this gift on the Family's Household, the consultant uses the Account Soft Credit feature.
* Relationship Tracking: A record is created in the Account Soft Credit related list on the Opportunity.
The "Account" is the Family's Household Account, and the "Role" is set to something like "Family Foundation."
* Rollups: NPSP's rollup engine will then pick up this soft credit. The family's Household record will now show this gift in fields like "Total Account Soft Credits" or "Total Gifts" (if the organization includes soft credits in their summary).
Why other options are incorrect:
* GAU Allocation (Option A): This tracks the fund or purpose of the money (e.g., "Building Fund"), not the donor or household credit.
* Lookup Fields (Options B & D): Adding custom lookup fields does not trigger NPSP's complex rollup logic. Only the standard Account Soft Credit object is recognized by the NPSP engine for aggregating influence-based giving to an account.

NEW QUESTION # 32
A nonprofit frequently receives donations through the mail. The consultant recommends using Nonprofit Success Pack (NPSP) Gift Entry. What are three advantages of using NPSP Gift Entry? (Choose 3)

• A. Can create different templates for different types of gifts
• B. Can process credit card payments
• C. Can prefill certain fields for batch entry
• D. Standardizes mailing addresses as they are entered
• E. Includes built-in mapping rules to help prevent duplicates

Answer: A,C,E

Explanation:
NPSP Gift Entry is a high-speed, accurate tool for processing high volumes of donations received through manual channels like direct mail. It is built upon the NPSP Data Import engine but provides a streamlined user interface.
Three Primary Advantages:
* Prefilling Fields (A): When creating a batch for a specific direct mail appeal, the consultant can set
"Default Values." For example, every gift in the "Year-End Appeal" batch can have the Campaign and GAU Allocation prefilled. This drastically reduces the number of keystrokes required for the data entry clerk.
* Mapping Rules and Duplicate Prevention (C): Gift Entry utilizes the NPSP Data Import logic. It doesn't just "create records"; it first attempts to find existing Contacts or Accounts based on sophisticated matching rules. This "Dry Run" capability identifies potential duplicates before the data is committed to the database, maintaining clean data hygiene.
* Customizable Templates (E): Not all gifts are the same. A consultant can create a "Grant Template" with fields for restricted funds and due dates, and a separate "Individual Check Template" that focuses on donor names and mailing addresses. This ensures that users only see the fields relevant to the specific type of entry they are performing.
Why other options are not primary advantages of Gift Entry:
* Address Standardization (B): While NPSP has address management features, it is not a
"standardization" tool (like an AS/400 or SmartyStreets) that happens during entry; that is usually handled by a separate integration.
* Credit Card Processing (D): While NPSP can link to Salesforce Checkout or Elevate, Gift Entry's primary purpose is manual data entry for offline gifts like checks.

NEW QUESTION # 33
A nonprofit wants to send an event cancellation notice to 150 Salesforce contacts without a separate email service provider. It wants to manage bounces, resend the notice as needed, and view the send history on the Contact record. Which option should a consultant recommend to meet the requirements?

• A. Account Engagement
• B. Send List Email
• C. Email-to-Case
• D. Elevate

Answer: B

Explanation:
For a small volume of contacts (150) and a simple one-off requirement like an event cancellation, standard Salesforce functionality is the most cost-effective and efficient choice. Send List Email is a native Lightning Experience feature that meets all the organization's criteria without the complexity of a third-party marketing tool.
How Send List Email Meets the Requirements:
* Direct Send: Users can select up to 2,000 contacts from a list view or a campaign and click Send List Email. This uses Salesforce's internal mail servers (or the organization's connected Office 365/Gmail account).
* Send History: Every list email sent is automatically recorded in the Activity History (specifically the
"HTML Email Status" or "Emails" related list) on the Contact record. This satisfies the requirement to
"view the send history."
* Manage Bounces: Salesforce has a native "Email Bounce Management" feature. If an email address is invalid, a warning icon appears next to the email address on the Contact record, and the staff can see the
"Bounce Reason."
* Resending: Because the send history is logged as an activity, staff can easily identify who didn't receive the message and trigger a follow-up email manually or by creating a filtered list of "bounced" contacts.
Why other options are incorrect:
* Elevate (Option A): This is a payment processing platform for fundraising and has no native bulk email capabilities for event management.
* Email-to-Case (Option B): This is a support tool for receiving incoming emails and turning them into tickets; it is not for proactive event outreach.
* Account Engagement (Option D): Formerly known as Pardot, this is a robust marketing automation platform. While it could do this, it is considered "overkill" for a one-off 150-person email and requires a separate, significant license and technical setup.

NEW QUESTION # 34
A nonprofit offers courses that grant teachers credit toward maintaining their teaching certification. Teachers can enroll in an annual cohort to complete the course modules together. The nonprofit needs to track the courses each teacher completes and the credits awarded to them. Which solution should a consultant recommend?

• A. Service Cloud
• B. Program Management Module
• C. Self-Service Portal
• D. Engagement Plans

Answer: B

Explanation:
The Program Management Module (PMM) is the standard industry solution for tracking the delivery of mission-centric services. In this scenario, the "Courses" are the services, and the "Teachers" are the participants.
Mapping the Requirement to PMM Objects:
* The Course (Program/Service): Each certification course is modeled as a Program. Individual modules or sessions within that course are modeled as Services.
* Annual Cohorts (Program Cohort): PMM has a standard Program Cohort object. This is perfectly suited for tracking a group of teachers who start and move through the certification modules together on an annual basis.
* Tracking Completion (Service Delivery): When a teacher completes a module, a Service Delivery record is created. The consultant can add a custom field to the Service Delivery object to track the
"Credits Awarded" for that specific session.
* Teacher Enrollment (Program Engagement): The teacher's overall progress toward their certification is tracked via the Program Engagement record, which rolls up the total number of credits earned from the related Service Deliveries.
While a Self-Service Portal (Option D) might be the interface the teachers use, and Service Cloud (Option B) provides the base infrastructure, the Program Management Module provides the specific data model (Programs, Cohorts, and Deliveries) required to track credits and educational progress out-of-the-box.

NEW QUESTION # 35
The system admin at a nonprofit has set up automated soft credits to grant to the solicitor of each donation.
The development director wants a report to show who the solicitor is for each donor. Which report type does the system admin need to use to create the requested report?

• A. Opportunities with Contact Roles
• B. Contacts with Relationships
• C. Opportunities with Partial Soft Credits and Contacts
• D. Accounts with Contact Roles and Household

Answer: A

Explanation:
In NPSP, soft credits are fundamentally based on the Opportunity Contact Role (OCR) object. Even if
"Partial Soft Credits" are used for splitting a gift, the primary mechanism for attributing a "Solicitor" to a donation is assigning them a specific role on the Opportunity.
Reporting Logic:
* The Junction: The Opportunity Contact Role acts as the bridge between the Opportunity (the donation) and the Contact (the solicitor).
* Standard Report Type: The standard report type Opportunities with Contact Roles allows the user to see the donor (the Account) and all related contacts who have a role on that gift.
* Filtering: The Admin can filter this report by the "Role" field (e.g., Role EQUALS Solicitor). This surfaces exactly who the solicitor was for every donor's transaction.
Why other options are incorrect:
* Option D: Partial Soft Credits is a more complex object used when multiple people get different dollar amounts of credit for a single gift. For a standard report showing "who the solicitor is," the Contact Role is the simpler and more standard starting point.
* Option A: Relationships track person-to-person ties (like "Spouse" or "Coworker"), not who influenced a specific financial transaction.
* Option B: This focuses on the Household structure rather than the individual donation influence history.

NEW QUESTION # 36
A Nonprofit Cloud consultant has been informed that the Donor Gift Summary data is out of date. What is the first step the consultant should take to identify the root cause?

• A. Ensure that the record-triggered flow that updates the Donor Gift Summary is active.
• B. Ensure that the logged in user has the appropriate field-level security on the Donor Gift Summary object.
• C. Navigate to Monitor Workflow Services and identify the failures in the Data Processing Engine definition that calculates the data.

Answer: C

Explanation:
The calculation of giving totals (e.g., Lifetime Giving, Last Gift Date) in Nonprofit Cloud is a major departure from the older NPSP. In NPC, these summaries are not updated by real-time code or flows; they are managed by the Data Processing Engine (DPE).
Because DPE is a batch-based processing tool, the data is only as "up to date" as the last successful run of the engine. If a user reports that the data is stale, the issue is almost certainly a failure in the background job rather than a UI or security issue.
Step-by-Step Troubleshooting for the Consultant:
* Monitor Workflow Services: This is the "Command Center" for all Industry Cloud background processes. The consultant should search for this in the Setup menu.
* Locate the Job: Within the monitor, find the entry for the specific Data Processing Engine definition responsible for Fundraising summaries (often titled something like "Calculate Donor Gift Summary").
* Check the Status: Look for runs marked as "Failed" or "Completed with Errors."
* Analyze Error Logs: Clicking into a failed run will reveal the specific technical reason for the failure (e.g., "System Limit Exceeded," "Data Mapping Error," or "Inactive Picklist Value").
* Rerun: Once the underlying data or configuration issue is resolved, the consultant can manually trigger the DPE run from this screen to bring the summaries up to date immediately.
Option A is incorrect because there is no standard record-triggered flow for these rollups in NPC. Option B is a valid check for visibility, but the question specifically states the data is "out of date" (meaning it exists but is wrong), suggesting a calculation/sync failure.

NEW QUESTION # 37
A nonprofit organization wants to track participants who attend drop-in programs. Which Nonprofit Cloud feature should the organization use?

• A. Benefit Schedule Assignments
• B. Anonymous Benefit Disbursements
• C. Ad Hoc Benefit Disbursements

Answer: C

Explanation:
In Nonprofit Cloud's Program Management module, tracking how services are delivered to constituents is handled through Benefit Disbursements. When dealing with "drop-in" programs-where participants may arrive without a prior appointment or a recurring schedule-the system uses Ad Hoc Benefit Disbursements.
Step-by-Step implementation for Drop-in Programs:
* Identify the Benefit: The consultant first ensures a Benefit record exists (e.g., "Daily Hot Meal" or
"Walk-in Counseling").
* Bulk Logging: For drop-in scenarios, the organization typically uses the New Ad Hoc Bulk Disbursement tool. This allows a staff member to select multiple individuals who showed up that day and record the benefit delivery in a single action.
* Walk-in Processing: Within the Ad Hoc tool, there is a specific "Walk-in" functionality. When a staff member records a benefit for someone who isn't yet enrolled in the program, the system can automatically create the Program Enrollment, Benefit Assignment, and the Benefit Disbursement simultaneously. This is the hallmark of a "drop-in" workflow, as it reduces the administrative burden of manually creating three separate records for every new visitor.
Why other options are incorrect:
* Anonymous Benefit Disbursements (Option A): This is used only when the organization wants to track the quantity of benefits given (e.g., 50 coats distributed) but does not record who received them.
The question specifically mentions tracking "participants," implying that their identities should be recorded.
* Benefit Schedule Assignments (Option B): This is intended for structured, recurring sessions where you know who is coming in advance (e.g., a 10-week GED course). Drop-in programs by definition lack a rigid pre-assigned schedule for specific participants.
Using Ad Hoc Benefit Disbursements ensures that the organization maintains a complete history of every interaction a participant has with their programs, which is vital for calculating the "Total Units Delivered" and evaluating the individual's progress over time.

NEW QUESTION # 38
A nonprofit organization has a successful company match donation process. The development team wants to attribute the grouped check to the company, but also ensure that individual donors are credited for their individual match. How should the organization accomplish this goal in Nonprofit Cloud?

• A. Record the individual as the donor on the Gift Transactions for their respective amount of the grouped check. Create a Gift Soft Credit for the company on each of those gifts.
• B. Record the company as the donor on the Gift Transaction of the grouped check. Create a Gift Soft Credit for each individual donor and their respective amounts.
• C. Record the company as the donor on the Gift Transaction of the grouped check. Create a Gift Designation for each individual donor and their respective amounts.

Answer: B

Explanation:
In the context of a Solution Design for corporate giving, a consultant must balance the "Hard Credit" (legal
/accounting ownership of the funds) with the "Soft Credit" (relationship and influence credit).
When a company sends a single "grouped check" that represents the matching funds for multiple employees, the legal donor is the Company. Therefore, according to standard accounting principles, the Hard Credit must be assigned to the company's Business Account.
Step-by-Step Solution Workflow:
* Create the Gift Transaction: The consultant records a single Gift Transaction (or a batch gift) where the Donor field points to the Business Account of the company. This ensures that the organization's financial reports correctly show that the cash came from the corporation.
* Identify the Individuals: The consultant then identifies the individual employees whose gifts triggered the match.
* Assign Gift Soft Credits: For each individual donor, a Gift Soft Credit record is created and linked to the company's Gift Transaction.
* The Soft Credit Recipient is the individual's Person Account.
* The Amount is the specific portion of the matching check that applies to them.
* The Role can be set to "Matched Donor."
* Reporting: When the organization runs its "Total Giving" reports for individuals, it can include "Soft Credit" amounts. This allows the development team to recognize the individuals for their influence in bringing in the matching funds, even though the company technically provided the money.
Why other options are incorrect:
* Option B: This would incorrectly attribute the "Hard Credit" (the legal ownership of the money) to the individuals. This would cause issues with tax receipts and financial reconciliation, as the individual did not personally write the check for the matching portion.
* Option C: Gift Designations are used to track which internal fund the money is for (e.g., "Education Fund"); they are not used to credit people or organizations for their involvement in a gift. Using Soft Credits is the correct architectural approach in NPC for influence and matching-gift recognition.

NEW QUESTION # 39
A nonprofit organization wants to track constituents who helped solicit donations. Which object should the organization use to track this influence in Nonprofit Cloud?

• A. Gift Soft Credit
• B. Gift Tribute
• C. Gift Designation

Answer: A

Explanation:
In fundraising, it is essential to distinguish between the person who physically wrote the check (the "Hard Credit") and the person who influenced the gift (the "Soft Credit"). In Nonprofit Cloud for Fundraising, this influence is tracked using the Gift Soft Credit object.
How a Consultant Configures Influence Tracking:
* The Transaction: A Gift Transaction is created for the donor who made the payment.
* The Influence: If a board member or a volunteer solicitor was responsible for bringing in that gift, a Gift Soft Credit record is created and linked to that Gift Transaction.
* Soft Credit Roles: The consultant can define different types of soft credits using the Role field.
Common roles include "Solicitor," "Peer-to-Peer Fundraiser," or "Household Member."
* Reporting: By using this object, the organization can run reports on "Total Influence" per volunteer.
This is vital for donor recognition programs where "Solicitors" are honored for the total funds they helped raise, even if they didn't donate the money personally.
Why other options are incorrect:
* Gift Tribute (Option A): This is used to track gifts made "In Honor Of" or "In Memory Of" someone.
While it involves a third party, it is specifically for the sentiment of the gift rather than the professional or volunteer solicitation influence.
* Gift Designation (Option C): This object is used to allocate the funds to specific internal accounts or programs (e.g., "General Fund" or "Building Campaign"). It tracks where the money goes, not who helped get it.
The Gift Soft Credit object ensures that the organization has a 360-degree view of constituent engagement, acknowledging both financial contributors and the champions who drive the fundraising engine.

NEW QUESTION # 40
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 a3nd create an Affiliation record between the volunteer and Universal Containers.
• B. Create a Lead for the volunteer at Universal Containers and create a Relationship record between the volunteer Lead and the volunteer Contact.2
• C. Create a Universal Containers Organization Account and create a Relationship record between the volunteer and Universal Containers.
• D. Create a Lead for the volunteer at Universal Containers and create an Affiliation record between the volunteer Lead and Universal Containers.1

Answer: A

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 # 41
A nonprofit wants to make a substantial technology shift that will affect multiple teams and departments.
Which two initial steps should a consultant discuss with the nonprofit? (Choose 2)

• A. Summarize final technology implementation steps.
• B. Establish a sense of urgency.
• C. Deploy features to meet departmental requirements.
• D. Form a powerful guiding coalition.

Answer: B,D

Explanation:
For a "substantial technology shift," a consultant must apply Change Management principles, such as Kotter's 8-Step Process for Leading Change. Technology is only one part of the project; the human element is what determines success.
Initial Strategic Steps:
* Establish a Sense of Urgency (C): People are naturally resistant to change. The consultant must help the organization articulate why this shift is necessary now. This involves identifying the risks of staying with the current siloed systems (e.g., "We are losing 20% of our donors because our data is inaccurate") and the opportunities of the new system. Without urgency, the project will likely lose momentum.
* Form a Powerful Guiding Coalition (D): A technology shift cannot be led by the IT department alone. A consultant must encourage the formation of a team that includes Executive Sponsors (to provide budget and authority) and Departmental Champions (to provide ground-level influence). This coalition works together to overcome resistance and ensure the project remains aligned with the mission.
Why other options are incorrect:
* Summarizing final steps (Option A): This happens at the end of the project lifecycle.
* Deploying features (Option B): You cannot deploy features successfully until the groundwork for change has been laid. Jumping straight to deployment without leadership alignment is a leading cause of implementation failure.

NEW QUESTION # 42
A nonprofit organization serves many families in their programs and want to track each family as a household. The organization serves diverse types of families, including blended families and split families, where some of the children divide their time between multiple households. How should the organization track these different family types?

• A. Create a Person Account for each family member. Use the New Group flow to simplify the necessary record creation.
• B. Create a Person Account for each family member. Create Contact Contact Relationship records between the family members.
• C. Create an Account for each family and Contacts for each family member. Create Party Role Relationship records between the family members.

Answer: A

Explanation:
In the new Nonprofit Cloud, the "Household" concept is managed using the Group (Account) and Account Account Relationship model, underpinned by Person Accounts for individuals. This is a departure from the NPSP "Household Account" model.
To handle complex, modern family structures-such as children living in two separate households (split families) or blended families-the consultant follows a specific workflow:
* Individual Representation: Every family member is created as an individual Person Account. This ensures that their data (milestones, benefits, medical records) stays with them regardless of which household they are currently associated with.
* The New Group Flow: Salesforce provides a standard, guided flow called the New Group flow. When a consultant or caseworker uses this flow, it automates the creation of a "Business" Account with a record type of Group (representing the Household). It simultaneously creates the Account Account Relationship records that link the individual Person Accounts to that Group.
* Handling Split Families: Because the system uses a junction-based relationship model (Account Account Relationship), a single child (Person Account) can be linked to multiple Group Accounts (Household A and Household B). One can be marked as the "Primary" household, while the other is
"Secondary."
* Role Definition: Within these relationships, you can specify roles (e.g., "Parent," "Dependent," "Step- Parent") using the Party Role Relationship configuration.
Option B is insufficient because while it tracks person-to-person ties, it fails to aggregate the individuals into a "Household" unit (Group) for reporting and program enrollment. Option C is incorrect because it suggests using the legacy Account/Contact model, which is not the recommended best practice for individuals in the modern Nonprofit Cloud.

NEW QUESTION # 43
A nonprofit needs to send automated renewal emails on a 30/60/90/180-day cadence. Each email template needs to be different based on the members' website visits. Which solution should a consultant recommend?

• A. Flow
• B. Apex
• C. Account Engagement
• D. Engagement Plans

Answer: C

Explanation:
This requirement involves complex Marketing Automation that goes beyond the capabilities of standard Salesforce transactional tools. While Salesforce Flow (Option C) can handle time-based triggers, it cannot natively track and react to specific "website visits" or web behavior without significant custom coding or integration.
Account Engagement (formerly Pardot) is the ideal solution for this scenario because of its specialized feature set:
* Website Tracking: Account Engagement uses a tracking code (cookie) to monitor constituent behavior on the nonprofit's website. This allows the system to "know" which pages a member visited (e.g., a
"Benefits" page vs. a "Donate" page).
* Engagement Studio: This is a visual journey builder. A consultant can create an "Automated Renewal Program" where the system waits 30, 60, 90, and 180 days.
* Dynamic Content: At each step of the 30/60/90/180-day cadence, the system can use Dynamic Content to swap out parts of the email template. If a member visited the "Member Events" page recently, the renewal email can automatically include a section about upcoming events to increase the relevancy of the appeal.
* Recency and Frequency: The tool can segment members based on how recently they visited the site, ensuring the messaging is timely and tailored to their current level of engagement.
Why other options are incorrect:
* Engagement Plans (Option B): These create internal Tasks for staff, not automated external emails with web-tracking logic.
* Flow (Option C): While it can send emails, it lacks the built-in web-tracking and high-volume marketing analytics provided by Account Engagement.
* Apex (Option A): This would be an expensive, high-maintenance custom solution for a problem that is solved out-of-the-box by a marketing automation platform.

NEW QUESTION # 44
A board member introduced a high-net-worth individual to the work of the nonprofit. The individual made a donation at an event. The fundraising manager wants to record this information in Salesforce. It is important the donation is hard credited to the individual while ensuring this donation, as well as any future donations from the individual, are soft-credited to the board member. The board member and the individual already exist as contacts in Salesforce. How should the data be entered?

• A. Create the donation opportunity for the individual. Add the board member as a Soft Credit contact role for the donation. Create a relationship between the board member and the individual.
• B. Create a relationship between the individual and the board member. Create the donation opportunity for the individual. Enter a Partial Soft Credit for the board member.
• C. Create a relationship between the individual and the board member. Create the donation opportunity for the individual. Add the board member as a Soft Credit contact role to the donation.
• D. Create a relationship between the individual and the board member with a Related Opportunity Contact Role of Soft Credit. Create the donation opportunity for the individual.

Answer: D

Explanation:
This requirement involves two parts: a one-time transaction and an automated long-term "influence" tracking.
In NPSP, this is best accomplished by using the Relationship object's advanced soft-credit capabilities.
Step-by-Step Implementation:
* Define the Automated Soft Credit: The consultant should create a Relationship record between the Board Member and the Donor.
* Set the Related Opportunity Contact Role: On this Relationship record, there is a field called Related Opportunity Contact Role. The consultant should select Soft Credit (or a custom role like
"Solicitor").
* The Automation Logic: By setting this field on the relationship, NPSP's trigger framework is instructed that every time a donation is created where the donor is the "Primary Contact," the person on the other end of the relationship should automatically be added to that donation as an Opportunity Contact Role with the specified soft 3credit role.45
* Result: When the fundraiser creates the current donation, the board member is automatically soft- credited. For every future donation the do6nor makes, the system will continue to grant that soft credit automatically, satisfying th7e requirement to track all future gifts without manual intervention.
Why other options are incorrect:
* Option A and D: These suggest adding the soft credit manually to the current donation. While this works for the current gift, it does not address the "any future donations" requirement, which would require the fundraiser to remember to do it every single time.
* Option C: Partial Soft Credits are used for splitting gifts among multiple people (e.g., $50 to person A, $50 to person B). It is more complex than needed here and does not have the automated "future" triggering logic found in the Relationship-based soft credit model.

NEW QUESTION # 45
......

Pass Your NP-Con-102 Exam Easily - Real NP-Con-102 Practice Dump Updated May 16, 2026: https://www.prep4sureguide.com/NP-Con-102-prep4sure-exam-guide.html

2026 Realistic Verified Free Salesforce NP-Con-102 Exam Questions: https://drive.google.com/open?id=1Sfa-Tkr7CD9jTuVVkFqiUJMi2Fh8Xa5q