Salesforce NP-Con-102 Practice Exam Questions & Answers

When a Gift Transaction is added to a Gift Commitment in Nonprofit Cloud, the transaction amount is automatically applied toward fulfilling the commitment. The system tracks progress toward the commitment by accumulating the Gift Transaction amounts. This allows organizations to monitor how much of the total commitment has been received. The Gift Commitment record updates to reflect the remaining balance due based on the transactions received, and when the sum of transactions equals the commitment amount, the commitment status can be marked as fulfilled. This relationship enables tracking of pledge fulfillment through actual received gifts.

In Nonprofit Cloud for Grantmaking, managing budgets effectively is crucial for both the grantmaker and the applicant. When setting up a Budget, the consultant uses Budget Category records to define how funds are allocated (e.g., Personnel, Travel, Supplies, Overhead).

In many grant applications, the order in which these categories appear is strictly defined by institutional policy or reporting requirements. Unlike standard Salesforce related lists, which often default to sorting by 'Created Date' or 'Name,' the Grantmaking data model utilizes a Sequence Number to control display logic.

Step-by-Step Implementation:

Define Categories: Identify the necessary categories for the grant (e.g., 1. Personnel, 2. Equipment, 3. Travel, 4. Admin).

Assign Sequence Numbers: When creating the Budget Category records (or the Budget Category Value records associated with a specific budget), the consultant must populate the SequenceNumber field.

Category A gets a sequence of 10.

Category B gets a sequence of 20.

Using increments of 10 is a best practice, as it allows for the insertion of new categories later without renumbering the entire list.

Verification: Once the sequence numbers are saved, the Lightning components used in the Grantmaking portal and internal pages will automatically respect this numerical order when rendering the budget table.

This approach ensures that the budget remains consistent across the entire application lifecycle---from the initial proposal to the final disbursement tracking. Option A is incorrect because 'rearranging' in a related list via the UI is not a persistent configuration that carries over to portals or documents. Option C is a 'hack' that relies on default sorting which is unreliable and difficult to maintain as the record count grows. Using the standard sequence field is the architecturally sound method in NPC.

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.

In Nonprofit Cloud, the Affiliation object is designed to track relationships between different accounts and contacts. For tracking relationships between board members (typically stored as Contacts or Accounts) and major donors, the Affiliation object provides the appropriate structure. It allows organizations to define the nature of the relationship through affiliation types and dates, making it ideal for capturing complex relationship hierarchies such as those between board members who may also be major donors, or between board members and their associated donors.

Before enabling Group Membership for Nonprofit Cloud households, the Household object itself must first be enabled and configured in the organization. The Household object is a prerequisite for Group Membership functionality, as Group Membership allows multiple household members to be grouped for various purposes such as group communications or shared benefits. Without an active Household object in the system, the Group Membership feature cannot function properly. This setup typically occurs during the initial Nonprofit Cloud configuration phase.

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.

The organization should use Process Templates in Nonprofit Cloud. Process Templates allow Program Managers to create standardized sequences of activities and tasks that participants follow to achieve their goals. While the template provides the best-practice framework, it can be customized for individual participants' needs. This provides consistency and efficiency while maintaining the flexibility required for individualized case management.