NP-Con-102 Exam Dumps and Practice Questions

When migrating data into the Nonprofit Success Pack (NPSP), the most efficient and robust tool is the NPSP Data Importer. This tool was specifically built to handle the 'multi-object' nature of nonprofit data in a single pass.

Why NPSP Data Importer is the Correct Choice:

Single File Processing: Standard Salesforce tools like Data Loader or the Data Import Wizard usually require separate files and separate 'upserts' for each object. You would have to import Accounts, then export the IDs, then import Contacts, then export those IDs, then import Opportunities.

Complex Logic in One Row: The NPSP Data Importer allows you to put the Contact Name, the Household address, and the Donation Amount on the same row of a CSV file.

Automatic Relationship Management: When you process the file, the Importer automatically:

Creates or finds the Contact.

Automatically creates the Household Account.

Creates the Opportunity (Donation) and links it to the Account.

Creates the Payment record (if payment info is included).

Handles GAU Allocations and Campaign Memberships.

Dry Run Capability: It includes a 'Dry Run' feature that validates the data and checks for duplicates before any actual records are created, which is vital for a clean migration.

While Workbench and Data Loader are powerful technical tools, they lack the specific NPSP business logic that makes the NPSP Data Importer the fastest and safest way to move a legacy database into Salesforce using a single flat file.

To track individual tutoring services, the nonprofit should use:

• Program Engagement records - To track each participant's enrollment in tutoring services
• Service Delivery records - To record each individual tutoring session provided, including the date, subject, and tutor information

By creating a Service Delivery record for each session, the organization can track the unlimited number of sessions per participant, generate reports on total sessions delivered, and analyze which tutoring subjects are most requested. This object structure also allows for outcomes tracking and performance metrics.

To create a sophisticated, multi-section grant application in Nonprofit Cloud for Grantmaking, Salesforce leverages the Discovery Framework and Dynamic Assessments. This combination allows a consultant to build an interactive digital experience that goes far beyond simple data entry.

Step-by-Step Application Build:

Discovery Framework: The consultant starts by creating the individual 'Questions' in the Discovery Framework. Each question (e.g., 'Number of individuals served' or 'Geographic focus') is a reusable record.

Assessment Definition: These questions are then organized into an Assessment Task or Assessment Definition.

OmniScript Design: Using OmniStudio, the consultant builds an OmniScript that serves as the 'Dynamic Assessment' engine. This is where the multi-section logic is defined. For example, a 'Counseling Details' section might only appear if the applicant selects 'One-on-one Counseling' as their service type.

Mapping: Using DataRaptors, the data entered into the form is mapped directly to the Individual Application object and its related records (like Budget or Contact Profile).

Experience Cloud Integration: Finally, the consultant places the Assessment component on the Grantmaking portal. The Form Overview and Form Review components (part of the Grantmaking template) work specifically with this Discovery Framework/OmniScript data to show the applicant their progress and allow them to review their answers before a final submission.

Why other options are incorrect:

Option A: 'Form Framework' is not a standard, named feature in NPC; the required technology is Discovery Framework.

Option B: While Dynamic Forms (and Field Sets) work for internal record pages, they do not support the complex multi-step, branching logic or the specialized 'Overview/Review' components required for a public-facing Grantmaking portal application. Using Discovery Framework is the architecturally correct way to provide a professional and compliant grant seeking experience.

In NPSP, Engagement Plans are used to automate the creation of a set of tasks when a specific goal is identified (e.g., 'Major Donor Stewardship'). It is critical to understand the relationship between the Template and the Instance.

The Logic of Decoupling:

The Template: This is the 'blueprint' that defines which tasks should be created, who should own them, and what their due dates are relative to the start date.

The Engagement Plan (Instance): When a user applies a template to a Contact or Campaign, the system 'explodes' the template and creates actual Task records and an Engagement Plan record.

Persistence: Once those tasks are created, they become independent records. If an admin modifies the original Engagement Plan Template (e.g., adding a new task or changing a deadline), NPSP does not retroactively update existing tasks or plans that were already generated. This is intentional to prevent disrupting ongoing workflows or overwriting manual changes staff may have made to their active tasks.

Result: Any modifications to the template will only be visible on new Engagement Plans created after the change was saved.

To update existing plans, the manager would have to delete the current Engagement Plan and re-apply the updated template, or manually add the new tasks to the current records.