NP-Con-102 Dumps 2026 - New Salesforce NP-Con-102 Exam Questions
Free NP-Con-102 Braindumps Download Updated on Apr 19, 2026 with 127 Questions
NEW QUESTION # 25
A nonprofit considers risk mitigation to be vital to the success of its implementation project. What are three elements impacted by change that cause risk?
- A. Quality, processes, time
- B. People, processes, cost
- C. Time, governance, people
- D. Cost, quality, time
Answer: D
Explanation:
In project management and Salesforce implementation strategy, the Triple Constraint (also known as the Iron Triangle) defines the three most critical elements that are impacted by any change to a project's scope.
These three elements are Cost, Quality, and Time.
* Cost: This refers to the financial budget and resources allocated to the project. If a nonprofit decides to add a new "Impact Dashboard" mid-implementation, the cost will likely increase as more consultant hours are required.
* Time: This is the schedule or deadline for the project. Adding features or facing technical hurdles usually extends the timeline. If the "Time" cannot be moved (e.g., a "Go-Live" before a major fundraising gala), then Cost or Quality must be adjusted.
* Quality (or Scope): This represents the robustness and functionality of the final solution. If a project is running over time and over budget, the organization might decide to "cut corners" or reduce the complexity of certain automations to meet the deadline, which negatively impacts the quality of the system.
Risk Mitigation Strategy: A consultant's job is to manage the balance between these three. If one changes, at least one of the others will be impacted. For example, if a nonprofit wants to speed up the Time to go-live, they must either increase the Cost (hiring more people) or decrease the Quality (reducing the initial scope).
Understanding these three risks is essential for settting realistic
NEW QUESTION # 26
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 # 27
A Fundraising Operations Manager is entering checks into Nonprofit Cloud by using Gift Batches. Some of the checks are payments on recurring gifts. When the Fundraising Operations Manager attempts to match the checks with the donor's current Gift Commitment in the Gift Entry window, no matching records appear.
Which Fundraising setting should be configured to resolve the issue?
- A. Select a Donor Matching Method value.
- B. Increase the Installment Extension Day Count setting.
- C. Change the Recency score thresholds.
Answer: B
Explanation:
When processing checks for recurring gifts in the Nonprofit Cloud, the system attempts to find an "expected" payment record to match against the physical check. In the NPC data model, recurring gifts are managed via Gift Commitments and Gift Commitment Schedules.
The system creates "expected" transactions (installments) based on the schedule. However, donors often send checks that arrive slightly before or after the exact scheduled date. If a check arrives outside of the system's
"window of expectation," the Gift Entry interface will not automatically suggest the matching commitment, leading to the "no matching records appear" issue.
The Solution: Installment Extension Day Count
* Function: This setting defines the number of days beyond the scheduled date that the system will look to find a matching installment. For example, if a gift is scheduled for the 1st of the month but the check arrives on the 10th, and the extension is set to 5 days, the system won't see it.
* Configuration: The consultant must go to Fundraising Settings in the Setup menu.
* Adjusting the Value: By increasing the Installment Extension Day Count (e.g., to 14 or 30 days), the consultant widens the "search window."
* Result: The next time the manager enters a check for that donor, the Gift Entry tool will successfully find and display the active Gift Commitment as a suggested match because the check's date now falls within the extended installment window.
Option C is incorrect because "Donor Matching" helps find the person, but the question specifies that the issue is matching the check to a specific Gift Commitment (the recurring gift record). Option B (RFM scoring) is for analytics and has no impact on the technical matching logic of the gift entry engine.
NEW QUESTION # 28
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. Filter logic
- C. Bucket field
- D. Cross filter
Answer: D
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 # 29
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 # 30
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 requires Experience Cloud licenses.
- B. Program Management Module has custom objects for calendars and activities.
- C. Program Management Module can track Case Plans and Action Items.
- D. Case Management has a custom object for tracking goals.
Answer: D
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 # 31
A nonprofit stores a government-issued personal identification number on each constituent's Contact record in an encrypted field. What should a consultant enable on a Permission Set to ensure the personal identification number is fully accessible by a subset of org users?1
- A. View All Data system permission2
- B. Manage Encryption Keys system permission3
- C. View Encrypted Data system permission4
- D. View All Contact object permission5
Answer: C
Explanation:
In Salesforce, sensitive data like Social Security Numbers or Tax IDs is often protected using Classic Encryption or Shield Platform Encryption. When a field is encrypted, it appears as masked (e.g., XXXX- XX-1234) to most users, even if they have "Read" access to the Contact object.
To allow a specific subset of users (such as the HR Director or a high-level Compliance Officer) to see the actual, unmasked data, the View Encrypted Data system permission must be utilized.
Step-by-Step Implementation:
* Create a Permission Set: The consultant should create a specific Permission Set named "PII Access" or similar.
* Enable System Permission: Under the System Permissions section of the Permission Set, the consultant must locate and check the box for View Encrypted Data.
* Assign to Users: This Permission Set is then assigned only to the specific users who require access to the sensitive identification numbers.
* Security Principle: This follows the "Principle of Least Privilege." Users with this permission can see the data in plain text in reports, list views, and record pages, while all other users see the masked version.
Why other options are incorrect:
* View All Data (Option A): This is a very broad and dangerous permission that grants access to almost all data in the org, but even "View All Data" does not automatically unmask encrypted fields unless View Encrypted Data is also present.
* Manage Encryption Keys (Option B): This is a highly technical administrative permission for managing the security certificates and keys; it does not grant the ability to view field data.
* View All Contacts (Option D): This provides object-level visibility but respects field-level security and masking.
NEW QUESTION # 32
A nonprofit needs more insight into why some corporate sponsorships are closing and why others are lost.
They want to evaluate information including pipeline value, number of opportunities, Pardot score, win/lost percentage, stage value, and a table of opportunities. The system admin wants to deploy a solution quickly.
Which solution should a consultant recommend?
- A. B2B Marketing Analytics
- B. NPSP Advanced Mapping
- C. Salesforce Reports
- D. Insights Platform Data Integrity
Answer: C
Explanation:
When a nonprofit requires immediate visibility into their opportunity pipeline and win/loss metrics, the most efficient and "quick to deploy" solution is Salesforce Reports and Dashboards.
Why Salesforce Reports is the best fit:
* Standard Functionality: Reports are a native part of the Salesforce platform. There is no additional software to install or license to procure.
* Cross-Object Reporting: Salesforce allows for "Opportunities with Pardot (Account Engagement)" report types. This allows the consultant to pull in the Pardot Score alongside standard Opportunity fields like Stage, Amount, and Probability.
* Visual Analytics: Using a Dashboard, the consultant can create a "Corporate Sponsorship Pipeline" view. They can include:
* Funnel Charts: For pipeline value by stage.
* Summary Tables: To list the specific opportunities.
* Gauge Charts: For the win/loss percentage.
* Speed of Deployment: A consultant can build a comprehensive dashboard meeting all these requirements in a matter of hours, whereas B2B Marketing Analytics (Option B) requires a complex setup process involving the "Analytics Studio," data syncs, and specialized licenses.
Why other options are incorrect:
* Advanced Mapping (Option A): This is a data import tool, not an analytics or reporting tool.
* Insights Platform (Option D): This is used for data cleansing and duplicate management, not for pipeline performance analysis.
By leveraging standard reports, the nonprofit gets the "insight" they need immediately using the data already sitting in their NPSP instance.
NEW QUESTION # 33
A consultant is engaged by a nonprofit organization during the planning phase of a Nonprofit Cloud implementation project. What should the consultant consider when identifying the business value of the project?
- A. The organization's stakeholders define the business value, but the consultant should have a plan to measure it.
- B. Increased fundraising performance cannot be considered because there is no guarantee that donations will increase.
- C. A change in the project schedule will not impact the business value, but a change in the project cost will.
Answer: A
Explanation:
In the Nonprofit Implementation Strategy phase, defining "Business Value" is critical for securing executive buy-in and ensuring the project delivers meaningful results. Unlike a simple technical installation, a successful implementation must align with the nonprofit's mission-driven goals.
The principle here is that Business Value is subjective and must be defined by the stakeholders (the Executive Director, Board of Directors, Program Managers, etc.). They are the ones who understand what
"success" looks like for their specific mission-whether that is reducing the time it takes to onboard a foster child, increasing the retention rate of first-time donors, or improving the accuracy of grant reporting.
The Consultant's Role:
* Discovery: The consultant conducts workshops to extract these goals from the stakeholders.
* Measurement Planning: Once the value is defined (e.g., "We want to save staff time"), the consultant must establish a plan to measure it. This involves identifying Key Performance Indicators (KPIs) and creating a "before and after" baseline. For instance, if the value is "Efficiency," the consultant might track the hours spent on manual data entry before NPC vs. after the automation is implemented.
* Dashboards and Reporting: The consultant configures Salesforce Dashboards to surface these metrics, providing the organization with a real-time view of the business value being realized.
Why other options are incorrect:
* Option A is incorrect because "Expected Business Value" often includes performance forecasts. While not "guaranteed," it is a perfectly valid target to aim for.
* Option B is incorrect because the project schedule directly impacts business value. If a project is delayed (e.g., missing a major year-end giving season), the value lost in potential donations can be immense, regardless of the software cost.
NEW QUESTION # 34
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. NPSP Data Import
- B. Bulk API
- C. SOAP API
- D. Data Import Wizard
Answer: B
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 # 35
The system administrator at a nonprofit wants to use Advanced Mapping for regular data imports of constituent and donation data. What is an important consideration of Advanced Mapping?
- A. The target objects must directly relate to Accounts, Contacts, or Opportunities.
- B. Checkbox fields are unavailable to map to as target fields.
- C. The target fields can only be text, currency, number, date or address fields.
- D. The target objects must be NPSP objects.
Answer: A
Explanation:
Advanced Mapping in the Nonprofit Success Pack (NPSP) is a powerful tool that allows admins to customize how data from the NPSP Data Import staging object is pushed into target records. However, it operates within a specific architectural framework.
Key Architectural Considerations:
* Object Relationships: Advanced Mapping is designed to handle the core "Nonprofit Triangle" of data:
Accounts, Contacts, and Opportunities. For any additional or custom object to be eligible as a target in Advanced Mapping, it must have a direct lookup or master-detail relationship to one of these three primary objects. This is because the NPSP Data Importer logic relies on these "anchor" records to establish context and maintain data integrity.
* Mapping Groups: The tool organizes mappings into Object Groups. When you create a new group for a custom object (e.g., "Volunteer Hours"), the system validates that the custom object is related to a Contact or Account so it knows which record to link the new data to.
* Field Type Support: Contrary to Option A and C, Advanced Mapping supports a wide variety of field types, including Checkboxes, Picklists, and Lookups. The restriction isn't on the field type, but on the object's position in the data hierarchy.
* Custom Object Support: While the question asks about "NPSP objects" (Option D), Advanced Mapping can map to custom objects created by the organization, provided they follow the relationship rules mentioned above.
Understanding these relationship requirements is essential for a consultant during the data migration or integration design phase. It ensures that the staging file can successfully populate multiple related records in a single execution without custom Apex code.
NEW QUESTION # 36
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 # 37
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 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
- 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 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
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 # 38
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 Transaction Designation
- B. Gift Default Designation
- C. Gift Designation
Answer: A
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 # 39
A nonprofit wants to implement an external email platform that integrates with Salesforce. The integration will record every email sent to a subscriber, as well as which recipients open the email, click a link, or unsubscribe. Which two storage considerations should the consultant take into account before recommending an email platform? (Choose 2)
- A. Email subscribers' activities can be retained for a certain length of time.
- B. Campaign Member records use less storage space than custom object records.
- C. Subscribers must be synced as Leads and Campaign Members in NPSP.
- D. Unsubscribed Leads should be deleted from Salesforce immediately.
Answer: A,B
Explanation:
Data storage is a significant cost and performance consideration for nonprofits. External email platforms (like Mailchimp, Constant Contact, or Marketing Cloud) can generate millions of "Activity" records that quickly consume a Salesforce org's data storage limits.
Two Key Considerations:
* Record Type Efficiency (B): In the Salesforce storage model, Campaign Member records are highly efficient. They take up significantly less space than a record in a custom object (like a "Email Result" object). If the integration uses Campaign Members to track status, the org can store more data before hitting its limits.
* Retention Policies (C): Because individual "Open" and "Click" data becomes less relevant over time, the consultant must consider a Data Retention Policy. For example, the organization might decide to keep granular engagement data for 6 months to drive near-term marketing, but then archive or delete that data to free up space for new records.
Why other options are less relevant:
* Option A: Syncing as Leads is a functional choice, but not a "storage consideration" in itself.
* Option D: Deleting unsubscribed leads is a bad practice; you should keep the record and mark it as
"Email Opt Out" to ensure you don't accidentally re-import and email them in the future, which would violate anti-spam laws.
NEW QUESTION # 40
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 Outcome Management permission set to the users.
- B. Mark all the Program and Benefit records as Active.
- C. Assign the Advanced Program Management permission set to the users.
Answer: C
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 # 41
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. Salesforce Data Loader
- D. NPSP Batch Data Import
Answer: D
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 # 42
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. Accounts with Contact Roles and Household
- B. Contacts with Relationships
- C. Opportunities with Partial Soft Credits and Contacts
- D. Opportunities with Contact Roles
Answer: D
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 # 43
......
Salesforce NP-Con-102 Exam Practice Test Questions: https://www.getvalidtest.com/NP-Con-102-exam.html
Updated Certification Exam NP-Con-102 Dumps - Practice Test Questions: https://drive.google.com/open?id=11Qf2VhgQM7heKci6Dpohfu31mcbm9TTo