NP-Con-102 Practice Questions

In Nonprofit Cloud, access to specific features and objects is controlled by permission sets. The "Advanced Program Management" permission set grants users the necessary object and field-level security to create, read, update, and delete Program and Benefit records. If Case Managers cannot see these records, it indicates they lack the fundamental permissions required for access. Assigning this permission set is the correct step to resolve the visibility issue and enable them to perform their duties within Program and Case Management.

A. The Outcome Management permission set grants access to objects like Indicator Definitions and Results, which is separate from core Program and Benefit visibility.

C. Marking records as Active affects their operational status but does not grant visibility to users who lack the underlying object permissions.

1. Salesforce Help. (2024). Assign Program and Case Management Permission Sets. The documentation specifies that the "Advanced Program Management" permission set is required for users who "create and manage programs, benefits, and benefit schedules."

2. Salesforce Help. (2024). Nonprofit Cloud Permission Sets. This overview lists the "Advanced Program Management" permission set and describes its purpose as providing access to Program Management objects.

NPSP's automated reciprocal relationship feature relies on a "Gender" field to determine the correct corresponding relationship. For example, if Contact A's relationship to Contact B is "Spouse," the reciprocal relationship for Contact B to Contact A will be set to "Spouse." However, for gendered relationships like "Husband/Wife" or "Son/Daughter," NPSP needs to know the gender of the other contact in the relationship. Since relationships are between individuals (Contacts), the Gender field must reside on the Contact object for the logic to function correctly.

A. Relationship: The Relationship object records the connection between two Contacts; the personal attributes like gender belong to the Contacts themselves, not the connection.

C. Account: Accounts represent households or organizations. A gender field is not applicable to these entities and is not used by the NPSP reciprocal relationship logic.

D. Affiliation: An Affiliation links a Contact to an Account. It does not store personal demographic data like gender used for reciprocal relationships between two Contacts.

1. Salesforce.org NPSP Documentation, "Create and Manage Reciprocal Relationships". Section: "Enable Gender-Specific Reciprocal Relationships". This section explicitly states, "To use gender-specific reciprocal relationships, you must first create a Gender field on the Contact object."

2. Salesforce Help, "Configure Reciprocal Relationships". Step 2 under "Set Up Gender Fields" instructs: "Create a custom picklist field on the Contact object. We recommend you label it Gender."

When a participant is added to a Benefit Schedule in Nonprofit Cloud, a Benefit Assignment record is created to link the participant to the scheduled benefit. Concurrently, the system automatically generates the future Benefit Disbursement records according to the schedule's defined frequency and duration. While a Program Enrollment is typically a prerequisite, some implementations may automate its creation as part of a holistic process of adding a new participant to a scheduled benefit, thus ensuring the data model's integrity.

B: Contact and Program Enrollment records must already exist; they are not created by the action of adding an existing participant to a schedule.

C: Benefit Sessions are created separately to define specific service times; they are not automatically generated when a participant is added to a schedule.

1. Salesforce Help. (n.d.). Create and Manage Benefit Schedules. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sfdo.NPCProgramManagementBenefitSchedules.htm&type=5. (This document states, "When you add a participant to a benefit schedule, a benefit assignment record is created... Benefit disbursement records are also created based on the schedule’s frequency.")

2. Salesforce Help. (n.d.). Program Management Data Model. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sfdo.NPCProgramManagementDataModel.htm&type=5. (The data model illustrates that Program Enrollment is a prerequisite for Benefit Assignment.)

In Nonprofit Cloud, a recurring donation is represented by a Gift Commitment record. To provide visibility into the future scheduled payments for that commitment, the standard "Upcoming Transactions" Lightning Web Component should be added to the Gift Commitment record page. This component displays a list of pending Gift Transaction records, showing the expected date and amount for each upcoming installment, directly addressing the organization's need to see the schedule for the next several months.

B. The Gift Transactions related list on an Opportunity shows past or current transactions, not a forward-looking schedule in a user-friendly component format.

C. The Timeline component on a Person Account shows past activities and interactions, not future scheduled financial transactions for a specific recurring donation.

1. Salesforce Help. (2023). Fundraising with Nonprofit Cloud. "Manage Gift Commitments". This section details the use of the Gift Commitment object for recurring donations and highlights the "Upcoming Transactions" component for viewing scheduled payments.

2. Salesforce Help. (2023). Nonprofit Cloud Developer Guide. "GiftCommitment". The documentation for the Gift Commitment object describes its relationship to scheduled Gift Transactions, which are surfaced by the Upcoming Transactions component.

For advanced audience segmentation for campaigns in Nonprofit Cloud, the recommended tool is Data Cloud. Data Cloud allows organizations to ingest and unify data from various sources (including Salesforce and external systems) to create a single, comprehensive view of their constituents. Consultants can then use Data Cloud's powerful segmentation tools to build precise audiences based on a wide range of attributes, such as demographics, engagement history, and program participation. These segments can then be activated in marketing and campaign tools like Marketing Cloud Engagement.

A. Agentforce: This is not a recognized Salesforce product or feature. It is not a valid tool for audience segmentation.

C. Tableau Desktop: Tableau is a data visualization and analytics tool. While it can be used to analyze data to identify potential segments, it is not the platform for building and activating those segments for campaigns.

- Salesforce Help, Data Cloud, "What is Data Cloud?". The documentation states, "With Data Cloud, you can unlock, harmonize, and unify all your customer data to create a single source of truth... Use your data to create rich, intelligent audience segments."

- Salesforce.org, Nonprofit Cloud, "Marketing and Engagement for Nonprofits". This solution overview highlights the integration with Data Cloud and Marketing Cloud to "create personalized journeys and segment supporters for targeted campaigns."

Care Plan Templates in Nonprofit Cloud's Program and Case Management functionality are designed for this exact purpose. A program team can define a standardized template with common goals and action items (tasks). Program Managers can then apply this template to a participant's Care Plan. This creates a baseline set of activities which the manager can then modify—adding, removing, or editing tasks—to tailor the plan to the individual's specific needs, providing both standardization and flexibility.

B. Record-Triggered Flows are automation tools that execute a rigid process. They lack the user-facing flexibility for a Program Manager to easily customize the process per participant.

C. Milestones and Life Events are used to track significant occurrences or achievements, not to manage a reusable, templated set of tasks and activities.

1. Salesforce Help, Nonprofit Cloud for Programs, "Create and Manage Care Plan Templates". This document states, "Create care plan templates to standardize your intake and case management processes...Then, apply the template to a client's care plan and customize it as needed."

2. Salesforce Trailhead, "Program Management with Nonprofit Cloud", Unit: "Manage Programs". This module explains how Care Plans and their templates are used to deliver standardized yet customizable services to program participants.

To provide read-only access, an administrator must ensure users have "Read" permission but not "Edit" or "Delete" permissions for the specified objects. If users are assigned permissions via a Permission Set Group that grants broader access (e.g., edit), a Muting Permission Set can be added to that group. The muting set would explicitly remove the "Edit" and "Delete" permissions for the Fundraising and Grantmaking objects, effectively limiting the user's access to read-only for those objects within the group.

A. Restriction Rules do not control object-level permissions (like read-only). They filter which records a user can see after access has been granted, based on record criteria.

C. Sharing Rules are used to grant users more access to records than the organization-wide defaults allow. They open up access, they do not restrict it to read-only.

1. Salesforce Help. (2023). Muting Permission Sets. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.permsetgroupsmuting.htm&type=5. (This document explains that a muting permission set lets you disable, or mute, selected permissions in a permission set group).

2. Salesforce Help. (2023). Restriction Rules. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.securityrestrictionrules.htm&type=5. (This source defines Restriction Rules as a tool to enhance security by allowing only certain records to be visible to specified users, confirming it is for record visibility, not object permissions).

The organization's primary business objective is time-based: completing the project before a specific date (the annual fundraising event). The Schedule Performance Index (SPI) is a standard project management metric that measures how efficiently a project is progressing against its planned schedule. It is calculated as Earned Value (EV) divided by Planned Value (PV). An SPI value greater than 1 indicates the project is ahead of schedule, while a value less than 1 indicates it is behind, directly measuring success against the stated objective.

B. Conversion rate: This is a fundraising or marketing metric that measures the effectiveness of a campaign, not the progress of a technology implementation project.

C. Cost performance index: This metric measures the project's cost efficiency against its budget. While important, it does not directly measure performance against a time-based deadline.

1. Salesforce Help. Nonprofit Cloud Implementation Guide. "Define Success Metrics". While not explicitly naming SPI, the guide emphasizes defining metrics that align with business objectives, such as timelines. The principle of aligning metrics to goals is paramount.

2. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.7.2, "Performance," discusses measuring project performance, including schedule performance through metrics like SPI. This is a foundational academic source for project management principles applicable to any technology implementation.

The logical sequence for configuring relationship tracking in Nonprofit Cloud is to first enable foundational features, then configure the user interface, and finally define the relationship models. Enabling Person Accounts is a prerequisite. Assigning Record Types and Page Layouts configures the user experience. Enabling Group Membership and creating Party Role Relationships establishes the data structure for tracking connections. This sequence ensures the system is properly set up before data models are implemented.

A. This option incorrectly suggests enabling features like Person Accounts after configuring UI elements like Record Types and Page Layouts, which is an illogical setup order.

B. This option proposes creating relationship records before assigning the page layouts needed to view and manage them, which is an inefficient and illogical configuration workflow.

1. Salesforce Help. (2023). Prepare for Nonprofit Cloud: Enable Person Accounts. Section: "Before you install and configure Nonprofit Cloud, enable person accounts." This confirms Person Accounts are a prerequisite.

2. Salesforce Help. (2023). Configure Relationships in Nonprofit Cloud. This guide details the setup of Party Relationship Groups and adding the necessary components to page layouts, which logically follows the initial enabling of prerequisite features.

3. Salesforce Developer Documentation. (2023). Nonprofit Cloud Developer Guide: Party Relationship Group. This document describes the underlying data model, which is configured after the core platform features and UI are prepared.

In Nonprofit Cloud, recurring donations are managed through Gift Commitment records, which have an associated Gift Commitment Schedule. The Pause Gift Commitment Schedule Action is an invocable action specifically designed to temporarily suspend the schedule of expected transactions for a recurring donation. This directly addresses the donor's request for a temporary break without canceling the entire commitment, allowing it to be resumed later.

A. The Close Gift Commitment Action would permanently terminate the recurring donation, which is not what the donor requested. The request was for a temporary suspension.

C. The Process Gift Entries Action is used for batch data entry to create new donation records from a staging object. It does not manage the status of existing recurring donations.

1. Salesforce Help. (2023). Manage and Process Donations in Fundraising: Pause a Gift Commitment. "To temporarily stop a gift commitment, pause its schedule... Use the Pause Gift Commitment Schedule action to pause a gift commitment."

2. Salesforce Developer Documentation. (2023). Nonprofit Cloud Developer Guide: Fundraising Actions. This guide lists and describes the available invocable actions, specifying that PauseGiftCommitmentSchedule is used to "Pause a gift commitment schedule."