Salesforce NP-Con-102 Practice Exam Questions & Answers

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.

Since the organization uses Person Accounts for participants, the Program Manager should:

• Create a list or report of the 50 program participants
• Use the Email feature within Nonprofit Cloud to send a mass email directly from the participant records

Person Accounts in Nonprofit Cloud maintain email addresses just like Contact records, so the Program Manager can select the 50 participants and send an email directly without needing to export to an external email tool. This keeps communication within the system and maintains audit trails of correspondence.

The correct answer reflects realistic implementation project management. Stakeholder Management (person accounts, relationships, address management) is foundational infrastructure that all other features depend on. Case Management can begin delivering value quickly by automating participant tracking and improving service delivery. This builds the data model and user competency needed for more complex features. Grantmaking Sites can then be added once the team is comfortable with core system usage. Finally, Outcome Management and Impact Reporting are layered on top, providing advanced insights once the fundamental processes are mature.

Option B (big-bang simultaneous deployment) overwhelms limited IT resources and training capacity, risking poor adoption and data quality. Option C incorrectly prioritizes revenue over mission and defers critical service delivery capability. Option D reverses proper sequencing by attempting to build dashboards before the underlying data is collected. A phased, foundation-first approach aligns with the Nonprofit Implementation Strategy objective of managing implementation projects through proper lifecycle planning.

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.

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.