Get Salesforce NP-Con-102 Exam Practice Questions - Real and Updated

Answer : B

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.

Answer : A

When an organization uses a Private sharing model (Organ11ization-Wide Defaults), users can only see records they own or records owned by their subordinates in the role hierarchy. To open up visibility to a 'subset' of records for a 'selected' group of staff, the consultant must use a Sharing Rule.

Implementing the Solution:

Criteria-Based Logic: Since only a subset of Service Deliveries (e.g., those related to 'Mental Health' or a specific 'Program') needs to be shared, the consultant should use a Criteria-Based Sharing Rule.

Definition: The rule might state: 'Share Service Delivery records where Program Name EQUALS 'Youth Outreach' with the 'Program Staff' Public Group.'

Access Level: The consultant defines the level of access (Read Only or Read/Write).

Public Groups: The 'selected staff' should be added to a Public Group. The sharing rule then targets this group.

Why other options are incorrect:

Public Read/Write (Option B): This would expose all records to all users, violating the nonprofit's strict security requirements.

Permission Sets / Profiles (Options C & D): These grant the functional ability to use the object (CRUD), but in a Private sharing model, they do not grant access to specific records owned by others. Sharing rules are the primary tool for record-level visibility in Salesforce.

Answer : C

In the Nonprofit Cloud Fundraising data model (specifically API v59.0 and later), Salesforce introduced the Outreach Summary object to provide deep insights into the performance of marketing and solicitation efforts.

While the standard Campaign object in Salesforce tracks basic metrics like 'Total Value Won Opportunities,' the Outreach Summary in NPC is designed for the high-volume needs of nonprofits. It stores specialized rollup fields that provide a granular view of how a specific campaign or 'Outreach Source Code' is performing.

Standard Rollup Fields in Outreach Summary:

GiftCount: The total number of gifts received in response to the campaign.

DonorCount: The number of unique donors who gave.

TotalGiftAmount: The sum of all gift amounts.

AverageGiftAmount: Automatically calculated to show donor value.

TotalRecurringGiftAmount: Specifically tracks the success of sustaining giving appeals.

Implementation Logic:

Calculation: These fields are not updated by standard Apex triggers in real-time. Instead, they are populated using the Data Processing Engine (DPE).

Scheduling: A consultant schedules the 'Outreach Summary' DPE job to run (e.g., nightly).

Visibility: The results are written back to the Outreach Summary record, which is linked to the Campaign. This allows the fundraising team to see the true ROI of their outreach without the performance overhead of real-time calculations.

Why other options are incorrect:

Donor Gift Summary (Option A): This object rolls up data at the Donor/Person Account level (e.g., 'John Doe's lifetime giving'), not at the Campaign level.

Gift Designation (Option B): This object tracks the 'Fund' or 'Purpose' (e.g., 'General Fund'), and while it can have rollups, it doesn't represent the 'Campaign' or 'Outreach' performance.

Answer : D

When a nonprofit requires a 'portal' or a 'web experience' for external users (constituents) to interact directly with Salesforce data, Experience Cloud (formerly Community Cloud) is the required solution.

How this solution meets the requirements:

Incoming Donations (NPSP): NPSP provides the foundational data model for managing individual donors, household accounts, and the donation (Opportunity) pipeline.

Constituent Portal (Experience Cloud): By implementing an Experience Cloud site (such as the Customer Service or Build Your Own template), the nonprofit can allow donors to:

Log in to view their giving history.

Download tax receipts.

Update their contact information or communication preferences.

Staff Management: While staff members typically use the internal Salesforce Lightning interface, Experience Cloud can also be configured for staff who need a simplified web interface for specific tasks.

New Web Experience: Experience Cloud is a highly customizable CMS (Content Management System). It allows the nonprofit to build a branded, mobile-responsive web experience that looks and feels like their main website while being natively connected to their Salesforce data.

Why other options are incorrect:

Program Management Module (Option A): This tracks service delivery, not web portals.

Accounting Subledger (Option B): This is a back-office tool for finance reconciliation.

Account Engagement (Option C): This is a marketing automation tool (Pardot) for sending emails and tracking engagement, but it does not provide a logged-in 'portal' experience for constituents.

Answer : C