Nonprofit-Cloud-Consultant Exam Dumps : Salesforce Certified Nonprofit Cloud Consultant (NPC) NP-Con-102

One of the most common configuration hurdles in Nonprofit Cloud is understanding the "Two-Key" access model. Unlike standard Sales or Service Cloud, where a Profile can grant access to almost any object, Industry Clouds (like NPC) require a Permission Set License (PSL) to be assigned before the objects even become "visible" or "available" in the system's schema for that user.

The "Two-Key" Access Model:

The First Key (Permission Set License): The PSL "unlocks" the feature set at the organization level for a specific user. For Fundraising, the user must be assigned the Nonprofit Cloud Fundraising PSL. Without this, the Fundraising objects (like Gift Transaction) literally do not exist from that user's perspective, even if they are a System Administrator.

The Second Key (Permission Set): Once the license is assigned, the user then needs a Permission Set (e.g., "Fundraising Access") to grant the actual CRUD (Create, Read, Update, Delete) permissions.

Step-by-Step Resolution for a Consultant:

Navigate to Setup > Users.

Open the user record for the System Administrator.

Scroll to the Permission Set License Assignments related list and click Edit Assignments.

Locate and check the box for Nonprofit Cloud Fundraising (and any other relevant industry licenses like Nonprofit Cloud Grantmaking).

Once the PSL is saved, the Admin will then be able to assign themselves the necessary Permission Sets to see and manage the Fundraising objects.

Option A is incorrect because Sharing Rules control which records you see, not whether the object itself is visible. Option B is incorrect because tabs are easily accessible via the App Launcher; if the objects are missing from the "All Objects" list, it is a licensing and permissioning issue, not a tab configuration issue.

In Nonprofit Cloud, the way we model groups of people—such as households, families, or boards—has been standardized using the Group Membership feature set.

To represent a "Household," the system uses a combination of a Business Account (as the container) and a Party Relationship Group (as the definition).

Step-by-Step Implementation:

Individual Accounts: First, ensure each spouse has their own Person Account. This is crucial for tracking individual giving history, life milestones, and program participation.

The Group Record: The consultant creates a Business Account with a record type of "Group."

The Party Relationship Group: Crucially, a Party Relationship Group record is created and linked to that Business Account. The Type field on this record must be set to Household. This tells the system that this specific group is a domestic unit rather than a professional association or board.

Relationship Mapping: Finally, the consultant uses the Account Contact Relationship object to link the two Person Accounts to the Household Business Account. Roles (e.g., "Primary Member," "Spouse") are assigned here.

Option C is a "data silo" mistake; you should never track two distinct people in one record as it breaks reporting for birthdays, emails, and individual engagement. Option B is an old NPSP concept; while NPC still uses Contact Roles, they are a result of the relationship model, not the method used to "track that they are part of a household."