View NP-Con-102 Exam Question Dumps With Latest Demo [Jun 15, 2026]
Free NP-Con-102 Test Questions Real Practice Test Questions
NEW QUESTION # 33
A large nonprofit is a social enterprise that functions like a for-profit corporation. The funding the nonprofit tracks in Salesforce only comes from corporations. The nonprofit needs to manage Leads and track its Opportunity pipeline. Which account model should the consultant recommend?
- A. Person Account Model without NPSP
- B. Individual Account Model in NPSP
- C. One-to-One Account Model in NPSP
- D. Standard Account Model without NPSP
Answer: D
Explanation:
This is a "Solution Design" question where the organization's business model dictates the architecture. While NPSP is the default for most nonprofits, it is specifically designed for Individual and Household giving.
If an organization functions like a B2B (Business-to-Business) corporation and only receives funding from other corporations:
* Simplification: They do not need the "Household" or "One-to-One" complexity of NPSP. These models are designed to "wrap" a contact in an account to support individual donations.
* Standard Sales Cloud: The Standard Account Model (where a Contact belongs directly to an Account/Corporation) is exactly how Salesforce was originally designed to work for corporate sales.
* Lead/Pipeline Management: By using Standard Salesforce (without NPSP), they get the cleanest experience for Lead conversion and Opportunity management, as all the NPSP-specific automation (like Household naming) would be unnecessary overhead for a purely corporate funding model.
Option A (Person Accounts) is also a specialty model, but it is intended for B2C (Business-to-Consumer) interactions. For a social enterprise dealing with corporations, Standard Accounts provide the best "out-of- the-box" fit.
NEW QUESTION # 34
What are two benefits of using Agile project management?
- A. All risks defined early in the project and the result is a single deliverable
- B. Iterative planning and hands-on stakeholder involvement
- C. A linear sequence of steps and carefully controlled change
Answer: B
Explanation:
In the context of a Nonprofit Cloud implementation, the Agile methodology is often preferred over traditional methods because it accounts for the evolving needs of mission-driven organizations. Unlike a rigid framework, Agile focuses on delivering value in small, manageable increments called "Sprints." Two of the most significant benefits of this approach are:
* Iterative Planning: Rather than trying to document every single requirement for a complex feature like
"Outcome Management" at the very start, Agile allows for continuous planning. The consultant and the nonprofit stakeholders prioritize a "Backlog" of work. At the start of each sprint, the team plans only the work for that cycle. This allows the organization to pivot if, for example, a new grant requirement is announced mid-project that changes how they need to track benefits.
* Hands-on Stakeholder Involvement: Agile requires constant collaboration. Stakeholders (such as Program Managers or Gift Officers) are involved in "Sprint Reviews" where they see live demonstrations of the work completed. This "fail-fast" or "learn-early" model ensures that if a consultant builds a Gift Entry flow that doesn't quite match the staff's physical workflow, it is caught and corrected within weeks rather than months.
Why other options are incorrect:
* Option A: Defining all risks early and producing a "single deliverable" is a hallmark of the Waterfall method. In Agile, risks are identified continuously, and deliverables are produced incrementally.
* Option C: A "linear sequence" and "carefully controlled change" describes a rigid Waterfall environment. In contrast, Agile is non-linear and embraces change as a way to improve the final product's relevance to the nonprofit's mission.
NEW QUESTION # 35
A nonprofit organization uses Nonprofit Cloud and wants to ensure that members of the fundraising department cannot access the program department's Interaction Summaries. What should the organization use to accomplish this goal?
- A. Permission Sets
- B. Compliant Data Sharing
- C. Session Security Levels
Answer: B
Explanation:
In many nonprofits, "Interaction Summaries" (meeting notes) contain highly sensitive information. A caseworker's notes on a victim of domestic violence must be kept strictly confidential from a fundraiser who might be looking at the same constituent record for a donation appeal.
To solve this challenge, Nonprofit Cloud utilizes Compliant Data Sharing (CDS).
How CDS Secures Interaction Summaries:
* Record-Level Restriction: By default, Interaction Summaries can be set to "Private" in the Organization-Wide Defaults (OWD).
* Role-Based Access: Compliant Data Sharing allows the organization to grant access based on the user's specific role in relation to that record. For example, only the "Assigned Caseworker" and
"Program Supervisor" roles are granted "Read" access to the summary.
* Departmental Silos: Because fundraisers are not assigned a "Program" role in the CDS configuration for those specific records, they will not be able to see the Interaction Summaries, even if they have access to the Person Account record.
* Auditability: CDS provides a clear audit trail of who was granted access to sensitive notes and why, which is critical for legal compliance in social services.
Why other options are incorrect:
* Permission Sets (Option A): These grant the ability to use the Interaction Summary object (CRUD), but they do not control which specific records a user can see. If OWD is set to Public, Permission Sets won't hide specific department notes.
* Session Security (Option B): This deals with 2-factor authentication and login requirements, not record-level data visibility between departments. Compliant Data Sharing is the standard Industry Cloud tool for this level of granular privacy.
NEW QUESTION # 36
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. Actionable Relationship Center
- C. Contact Profile
Answer: B
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 # 37
A nonprofit enters donation data both into Salesforce and an external accounting system to reconcile financial support. This process is time-consuming. What should the consultant recommend to reduce manual data entry and improve efficiency?
- A. Data Import Wizard
- B. Accounting Subledger
- C. Advanced Mapping
- D. NPSP Data Importer Templates
Answer: B
Explanation:
The primary pain point described is the "double entry" of financial data between a CRM (Salesforce) and an external General Ledger (GL) or accounting system. To resolve this, Salesforce developed Accounting Subledger.
Accounting Subledger acts as the translator between fundraising language and accounting language. It automatically generates Ledger Entry records based on donation data (Opportunities and Payments) in Salesforce. These ledger entries are formatted to align with standard accounting principles (Debits and Credits) and can be easily exported in a format that the external accounting system can ingest.
Step-by-Step Efficiency Gains:
* Automation: Instead of a staff member manually typing data into a second system, Accounting Subledger identifies "Closed/Won" gifts and creates the corresponding accounting records in the background.
* Accuracy: It eliminates human error associated with manual entry, ensuring that the total "Revenue" in Salesforce matches the "Income" in the accounting software.
* Transparency: Because the ledger entries are linked directly to the original Opportunity in Salesforce, the finance team and the development team can reconcile records using a shared "source of truth."
* Audit Trail: It maintains a permanent record of when data was "finalized" for accounting purposes, which is essential for annual audits.
By implementing Accounting Subledger, the consultant moves the nonprofit from a manual reconciliation process to an automated "subledger" model, significantly reducing administrative overhead and allowing staff to focus on mission-driven tasks rather than data entry.
NEW QUESTION # 38
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. Matching Rules
- B. Duplicate Jobs
- C. Duplicate Rules
- D. Scheduled Apex Jobs
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 # 39
A nonprofit organization uses Action Plans to guide its work on client Care Plans. The organization needs to add more tasks to an active Action Plan Template. What should the organization do to update the Action Plan Template in Nonprofit Cloud?
- A. Clone the Action Plan Template, select "Let users add items to action plans", and then publish the template.
- B. Clone the Action Plan Template, add tasks, and then publish the template.
- C. Deactivate the Action Plan Template, add tasks, and then publish the template.
Answer: B
Explanation:
In Salesforce Nonprofit Cloud, Action Plan Templates are used to standardize repeatable processes, such as the steps required to onboard a new client or complete a grant application. To ensure data integrity and version control, Salesforce treats published Action Plan Templates as "locked" records.
When an organization needs to modify an "Active" or "Published" template-such as adding new tasks-the system does not allow direct editing of the existing record to prevent breaking current active Action Plans that were generated from that specific version. The standard procedure for a consultant is as follows:
* Clone the Template: The user must select the existing Action Plan Template and use the Clone action. This creates a new "Draft" version of the template with all the existing tasks copied over.
* Modify the Draft: In the new draft record, the consultant can add the additional tasks, define their priority, set the number of days for completion, and assign roles or specific users to those tasks.
* Publish: Once the modifications are complete, the new template must be Published. Publishing makes the template available for users to generate new Action Plans.
* Retire the Old Template: Although not strictly required to make the new tasks work, it is best practice for a consultant to deactivate or rename the old version to ensure staff only use the most up-to-date process moving forward.
Option B is incorrect because Salesforce does not typically allow you to "deactivate and edit" the task structure of a template that has already been published. Option A describes a specific setting that allows end- users to add extra tasks to an individual instance of a plan, but it does not address the requirement of updating the master template itself.
NEW QUESTION # 40
Which two objects in the Program Management Module are directly connected to objects in Nonprofit Cloud Case Management?
Choose 2 answers
- A. Case
- B. Service Delivery
- C. Client Alert
- D. Program
Answer: B,D
Explanation:
The relationship between the Program Management Module (PMM) and Nonprofit Cloud Case Management (NCCM) is one of "broad service tracking" meeting "individualized care." While PMM provides the framework for what services an organization offers, NCCM provides the specific tools for caseworkers to manage a participant's journey.
Two objects serve as the primary "connectors" between these two modules:
* Program (C): In PMM, the Program object defines the high-level initiative (e.g., "Housing First"). In Case Management, the Case Plan is often directly linked to a Program. When a caseworker creates a Case Plan for a client, they select the Program that the plan supports. This ensures that the individual's goals and action items are contextualized within the organization's broader mission.
* Service Delivery (A): This is the functional link. PMM uses Service Deliveries to track when a service was provided. In NCCM, when a caseworker fulfills an Action Item that involves providing a specific service (like a "Counseling Session"), the system can automatically generate a Service Delivery record.
This allows the organization to see how specific case-managed activities contribute to overall program outputs.
Why other options are incorrect:
* Case (Option B): While NCCM uses the standard Salesforce Case object, it is a base platform object.
The specific PMM objects are designed to link to the program-centric logic, not just the generic case container.
* Client Alert (Option D): This is a specific feature of Case Management used to flag sensitive information (e.g., "Allergy" or "Safety Risk") on a contact record, but it does not have a direct architectural relationship with the PMM objects like Programs or Service Deliveries do.
NEW QUESTION # 41
A nonprofit organization plans to use Program and Case Management to track its substance abuse services.
When the Case Managers log in, they cannot see any of the Program and Benefit records that have been set up. What should the organization do to resolve the issue?
- A. Assign the Advanced Program Management permission set to the users.
- B. Assign the Outcome Management permission set to the users.
- C. Mark all the Program and Benefit records as Active.
Answer: A
Explanation:
In Nonprofit Cloud, access to core functionality is governed by specific industry-aligned permission sets. If Case Managers are unable to see Program and Benefit records, it is typically a matter of missing object-level and feature-level permissions.
The Advanced Program Management permission set is a critical requirement for users who need to interact with the full program lifecycle.
Permissions included in Advanced Program Management:
* Object Access: It grants Read, Create, Edit, and Delete access (depending on the specific assignment) to the Program, Benefit, Benefit Type, and Benefit Schedule objects.
* Functional Access: It allows users to manage Program Enrollments and track Benefit Disbursements
.
* Visibility: Without this permission set (or a Permission Set Group containing it), the objects remain hidden from the user's navigation bar and global search, even if the records are marked as "Active." Step-by-Step Resolution:
* The Admin should navigate to Setup > Users.
* Select the Case Manager users.
* Click Permission Set Assignments > Edit Assignments.
* Add Advanced Program Management to the assigned list.
* Note: If the organization wants to limit Case Managers to "Read-Only," they would use this permission set in conjunction with a Muting Permission Set within a Permission Set Group.
Why other options are incorrect:
* Outcome Management (Option A): This grants access to impact tracking (Outcomes, Indicator Definitions) but does not provide the primary access to the Program and Benefit service delivery objects.
* Status Marking (Option C): While a record should be active for operational use, "Active" status on a record does not override Salesforce security. If the user doesn't have object-level permissions via a permission set, they cannot see the record regardless of its status.
NEW QUESTION # 42
A nonprofit has its organization-wide sharing settings for all objects set to Private and is using Program Management Module to track Service Deliveries. A subset of Service Delivery records should be visible to selected staff. How should a consultant meet this requirement?
- A. Update default sharing to Public Read/Write.
- B. Create a criteria-based sharing rule.
- C. Create and assign a new profile.9
- D. Update the assigned Permission Set.
Answer: B
Explanation:
When an organization uses a Private sharing model (Organ11ization-Wide Defaults), users can only see records they own or records owned by their subordinates in the role hierarchy. To open up visibility to a
"subset" of records for a "selected" group of staff, the consultant must use a Sharing Rule.
Implementing the Solution:
* Criteria-Based Logic: Since only a subset of Service Deliveries (e.g., those related to "Mental Health" or a specific "Program") needs to be shared, the consultant should use a Criteria-Based Sharing Rule.
* Definition: The rule might state: "Share Service Delivery records where Program Name EQUALS ' Youth Outreach' with the 'Program Staff' Public Group."
* Access Level: The consultant defines the level of access (Read Only or Read/Write).
* Public Groups: The "selected staff" should be added to a Public Group. The sharing rule then targets this group.
Why other options are incorrect:
* Public Read/Write (Option B): This would expose all records to all users, violating the nonprofit's strict security requirements.
* Permission Sets / Profiles (Options C & D): These grant the functional ability to use the object (CRUD), but in a Private sharing model, they do not grant access to specific records owned by others.
Sharing rules are the primary tool for record-level visibility in Salesforce.
NEW QUESTION # 43
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. Group Membership
- B. Compliant Data Sharing
- C. Permission sets
Answer: B
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 # 44
The development director wants all users to only see Engagement Plans on Opportunity records for donations with an Amount greater than 10,000. How should this be accomplished?
- A. Add the Related List - Single Lightning component to the Opportunity Lightning pa13ge. Add a component visibility filter to display the Engagement Plan when the Opportunity Amount field is greater than 10,000.
- B. Create a tab and associate the Engagement Plan object to the tab. Add the Related List - Single Lightning component and set it to Engagement Plans. Give read access for the Engagement Plan object to all profiles.8
- C. Add the Related Lists component to the Opportunity Lightning page. Set the component visibility filter to ensure the Opportunity Amount field is greater than 10,000. Assign the page to the development director's profile.
- D. Create a custom Lightning component that dis9plays all Engagement Plans. Add the component to the Opportunity Lightning Page. Assign the Lightning Page as the Org Default and Activate it.101112
Answer: A
Explanation:
To meet this requirement, a consultant should leverage Dynamic Lightning Pages, specifically using Component Visibility Filters. This allows for a declarative solution that does not require multiple page layouts or custom code.
Step-by-Step Implementation:
* Edit the Page: Navigate to an Opportunity record and select Edit Page from the Setup (gear) icon to open the Lightning App Builder.
* Add the Component: Drag the Related List - Single component onto the page layout.
* Configure the Component: In the component properties sidebar, set the Related List to "Engagement Plans."
* Set Visibility Filter: Scroll down to the Set Component Visibility section and click + Add Filter.
* Define Criteria: * Field: Amount
* Operator: Greater Than
* Value: 10,000
* Save and Activate: Save the page. When "All Users" (per the requirement) view an Opportunity, the Engagement Plan related list will simply be invisible if the amount is $10,000 or less. If it is $10,001 or more, the component will appear.
Why other options are incorrect:
* Option A: Assigning the page only to the development director's profile violates the requirement that
"all users" should see it when the criteria is met.
* Option B: This is an overly complex and disjointed user experience that doesn't actually filter the view based on the specific Opportunity's amount.
* Option C: A custom component is unnecessary "Technical Debt" since standard functionality meets the requirement perfectly.
NEW QUESTION # 45
A nonprofit organization performs wealth prospecting on a donor. The organization wants to track the real estate value and the business ownership value of the donors. Which Nonprofit Cloud object has standard fields to track these values?
- A. Business Account
- B. Contact Profile
- C. Opportunity
Answer: B
Explanation:
In the context of the new Nonprofit Cloud (NPC) and its Fundraising capabilities, Salesforce has introduced a more granular data model to support wealth screening and donor prospecting. The correct object for tracking specific financial indicators like real estate and business ownership is the Contact Profile.
In earlier versions of Salesforce for nonprofits (like NPSP), this data might have required custom fields on the Account or Contact. However, in the modern Nonprofit Cloud architecture, the Contact Profile object is specifically designed to store sensitive, person-centric data that aids in major gift strategies. This object contains standard, out-of-the-box currency fields such as:
* RealEstateValue: To track the estimated value of property owned by the constituent.
* BusinessOwnershipValue: To record the value of private businesses the contact owns.
* AssetLiquidationValue: For tracking liquid assets.
* StockValue: For public equity holdings.
Step-by-Step Configuration for Wealth Prospecting:
* Enable Fundraising: The consultant must first ensure that Fundraising is enabled in the Setup menu, as the Contact Profile fields for fundraising are available in more recent API versions (v59.0 and later).
* Set Up Donor Profiles: The consultant should configure the Donor Profile-an account page layout within the Fundraising app.11 This page uses the Contact Profile record to display a "Donor Summary" card.
* Data Integration: Often, wealth data is imported from external screening services (like WealthEngine or iWave). The consultant maps these external data points directly to the standard fields on the Contact Profile object.
* ARC Integration: To provide a 360-degree view, the Contact Profile data can be surfaced alongside the Actionable Relationship Center (ARC), allowing major gift officers to see a donor's net worth alongside their professional and personal affiliations.
By utilizing the standard Contact Profile object, nonprofits ensure their data remains compatible with built-in analytics and future Salesforce updates.
NEW QUESTION # 46
A nonprofit has employed a contract developer for work involving objects that contain personal and personally identifiable information. The contractor is working in a full copy sandbox. What should the consultant recommend to ensure the contractor is unable to access this sensitive data?
- A. Implement Salesforce Shield and apply it to the sensitive data.
- B. Encrypt all fields containing sensitive data with Classic Encryption.
- C. Configure the contractor's Profile to prevent access to the sensitive data.
- D. Implement Salesforce Data Mask and mask the sensitive data.
Answer: D
Explanation:
When a nonprofit uses a Full Copy Sandbox, the sandbox contains an exact replica of all the production data, including sensitive donor PII (Personally Identifiable Information). Giving a contractor access to this data is a significant security and compliance risk.
The Solution: Salesforce Data Mask:
* Anonymization: Salesforce Data Mask is a powerful managed package that allows an admin to
"scrub" or "mask" sensitive data in a sandbox.
* Methods: It can replace real names with random names (Anonymization), replace characters with "X" (Deletion), or shuffle values within a column (Pseudonymization).
* Developer Experience: The contractor can still see the structure of the data and write code against it, but the actual "John Doe at Main St" becomes "Sam Smith at 999 West Rd."
* Security: This ensures that even if the developer's local machine or account is compromised, no real constituent data is exposed.
Why other options are incorrect:
* Encryption (Options A & C): This protects data at rest but does not help if the developer has the permissions to view the decrypted data for testing purposes.
* Profiles (Option D): This is insufficient because a developer often needs access to the fields themselves to write code; Data Mask allows them to see the field while hiding the sensitive content.
NEW QUESTION # 47
A nonprofit is loading 5 million donation history records into Salesforce from a payment processing system.
What should the consultant do to ensure the data load is successful?
- A. Disable Data Validation Rules.
- B. Deploy a Custom Apex Class with TDTM.
- C. Temporarily disable TDTM Trigger Handlers.
- D. Create an Apex Test Class.
Answer: C
Explanation:
When performing large-scale data migrations-specifically loading millions of records-performance and system limits become the primary concern. In the Nonprofit Success Pack (NPSP), almost all automation is governed by the Table-Driven Trigger Management (TDTM) framework.
The Logic of Disabling TDTM:
* Reducing Overhead: By default, TDTM triggers a series of complex operations every time an Opportunity (donation) is inserted, such as calculating rollups, creating recurring donation installments, and managing household naming. For a historical data load of 5 million records, running these processes in real-time would likely hit Salesforce governor limits and significantly slow down the migration.
* Sequential Execution: Disabling the Trigger Handlers allows the data to be loaded in its "raw" state.
The consultant can then run specialized batch jobs (like Customizable Rollups) after the load is complete to calculate the totals all at once.
* Process: To do this, the consultant navigates to the Trigger Handlers tab in NPSP and unchecks the
"Active" box for specific handlers (like OPP_Rollup_TDTM or REL_Relationships_TDTM) or uses the NPSP Settings to disable the entire framework for the migration user.
While Validation Rules (Option B) might also need to be disabled if the legacy data is messy, the most critical step for a high-volume load to prevent "Apex CPU time limit exceeded" errors is managing the TDTM framework. Option C and D are development tasks that do not assist in the immediate efficiency of a data load.
NEW QUESTION # 48
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 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.
- B. 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.
- C. 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.
- D. 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.
Answer: C
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 # 49
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 Lightning Web Components
- C. Fundraising Invocable Actions
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 # 50
A nonprofit needs to frequently import membership renewal and donation data. Each import needs a different configuration that will create or update existing Contacts in addition to creating Opportunities. Which tool should the consultant recommend?
- A. Salesforce Import Wizard
- B. NPSP Data Importer
- C. NPSP Batch Data Import
- D. Salesforce Data Loader
Answer: C
Explanation:
The NPSP Data Importer (Option D) is the underlying engine, but the requirement for "frequent imports" with "different configurations" specifically points to the NPSP Batch Data Import (A) feature.
Why NPSP Batch Data Import is the correct recommendation:
* Saved Configurations: In NPSP, a "Batch" is a record that stores specific configuration settings. A consultant can create one Batch for "Membership Renewals" and another for "General Donations." Each batch can have different matching rules (e.g., match by Email for memberships vs. match by External ID for donations).
* Multi-Object Creation: Like the standard importer, it creates or updates Contacts and Accounts while simultaneously creating the Opportunity and Payment records in a single step.
* Efficiency: For "frequent" work, a user doesn't have to re-map fields every time. They simply select the appropriate Batch, upload the CSV, and the system uses the pre-saved mapping and logic associated with that batch.
* Dry Run: It allows for a "Dry Run" on the specific batch to ensure the data is clean before it is committed to the database.
Why other options are incorrect:
* Data Loader (Option C): This would require multiple imports (Contacts first, then Opportunities) and does not support the automated "Match or Create" logic of NPSP.
* Import Wizard (Option B): This is a standard tool that cannot handle the complex NPSP multi-object relationship logic in a single pass.
* NPSP Data Importer (Option D): While technically the engine, the "Batch" feature is what provides the ability to store different configurations for frequent use.
NEW QUESTION # 51
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. Interaction Summaries
- C. Outreach Summaries
Answer: B
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 # 52
......
View All NP-Con-102 Actual Free Exam Questions Updated: https://www.actual4dump.com/Salesforce/NP-Con-102-actualtests-dumps.html
NP-Con-102 Dumps Updated Jun 15, 2026 WIith 127 Questions: https://drive.google.com/open?id=1W-bmhrKPjacqt0_ZhPRWA11Nd-xY1nq4