NP-Con-102 Exam Preparation Material | Salesforce Certified Agentforce Nonprofit Consultant

Explanation:
In Salesforce Nonprofit Cloud, Care Plans are specifically designed to provide individualized support by documenting goals, objectives, and the specific actions needed to achieve them .
This feature includes:
Goal Definitions: Allows case workers to define specific objectives tailored to each individual's unique circumstances.
Care Barriers: Specifically tracks the challenges and obstacles―such as unstable housing or health issues―that might prevent a participant from reaching their goals.
Task Tracking: Integrates individual tasks and notes within the plan to provide a complete view of a participant’s progress.

Explanation:
Nonprofit Cloud Case Management (NCCM) is a managed package that extends the capabilities of Salesforce for human services. Like many high-end Salesforce industry solutions, it has specific technical and legal prerequisites that must be met before the installation can succeed.
Prerequisite 1: Provisioned Licenses (A):
NCCM is not a free, open-source tool like NPSP. It is a paid product that requires specific Permission Set Licenses (PSLs) to be provisioned in the org. A consultant must verify that the organization has purchased the necessary licenses through their Salesforce Account Executive. Without these licenses appearing in the "Company Information" section of Setup, the managed package will not function, and users will not be able to access the custom Case Management objects like Goals, Action Items, or Case Plans.
Prerequisite 2: My Domain (C):
NCCM relies heavily on modern Lightning components and OmniStudio features to power its interactive interfaces (such as the Case Plan Wizard). Salesforce requires My Domain to be enabled and deployed in any org that uses custom Lightning components. My Domain adds a unique prefix to the Salesforce URL (e.g., https://my-nonprofit.my.salesforce.com), which is necessary for the secure rendering of these components.
Why other options are incorrect:
Volunteers for Salesforce (Option B): This is a completely separate application for managing volunteer shifts and is not required for Case Management to function.
Install NPSP (Option D): While NCCM is often used alongside NPSP, the modern Nonprofit Cloud Case Management package can technically run on a standard Salesforce platform without NPSP, provided the necessary licenses are in place.

Explanation:
This is a "Who Has NOT" reporting requirement, which is the primary use case for Cross Filters in Salesforce.
How to build this report:
Base Report: Create a report of Contacts (or "Contacts with Opportunities").
Annual Fund Filter: Set the standard report filters to show only those who have $0 in giving for the current year.
The Exclusion (Cross Filter): Click the "Filters" dropdown and select Add Cross Filter.
Configuration: * Set the filter to: Contacts WITHOUT Campaign Members.
Add a sub-filter to the cross filter: Campaign Name EQUALS [Upcoming Gala Name].
Result: The report will now list only people who are donors but are not currently registered for the Gala.
Why other options are incorrect:
Filter Logic (Option A): This is used for "AND/OR" statements between existing fields (e.g., 1 AND (2 OR 3)). It cannot easily look "across" to the Campaign Member object to check for the absence of a record.
Summary Formula (Option C) and Bucket Field (Option D): These are used for calculating or grouping data that is present in the report; they cannot be used to exclude records based on their relationship to other objects.

Explanation:
In Salesforce, sensitive data like Social Security Numbers or Tax IDs is often protected using Classic Encryption or Shield Platform Encryption. When a field is encrypted, it appears as masked (e.g., XXXX-XX-1234) to most users, even if they have "Read" access to the Contact object.
To allow a specific subset of users (such as the HR Director or a high-level Compliance Officer) to see the actual, unmasked data, the View Encrypted Data system permission must be utilized.
Step-by-Step Implementation:
Create a Permission Set: The consultant should create a specific Permission Set named "PII Access" or similar.
Enable System Permission: Under the System Permissions section of the Permission Set, the consultant must locate and check the box for View Encrypted Data.
Assign to Users: This Permission Set is then assigned only to the specific users who require access to the sensitive identification numbers.
Security Principle: This follows the "Principle of Least Privilege." Users with this permission can see the data in plain text in reports, list views, and record pages, while all other users see the masked version.
Why other options are incorrect:
View All Data (Option A): This is a very broad and dangerous permission that grants access to almost all data in the org, but even "View All Data" does not automatically unmask encrypted fields unless View Encrypted Data is also present.
Manage Encryption Keys (Option B): This is a highly technical administrative permission for managing the security certificates and keys; it does not grant the ability to view field data.
View All Contacts (Option D): This provides object-level visibility but respects field-level security and masking.

Explanation:
In Nonprofit Cloud for Fundraising, the acknowledgment process is integrated with the OmniStudio Document Generation engine. To allow users to trigger the creation of a letter directly from a donor's record or a specific transaction, a specific action must be available on the interface.
Step-by-Step UI Configuration:
Identify the Object: Acknowledgments are typically generated from the Gift Transaction record (for individual gifts) or the Person Account record (for summaries).
Page Layout / Lightning App Builder: The consultant navigates to the record page in the Lightning App Builder.
Add the Action: The consultant adds the standard Generate Document button (or "Quick Action") to the Highlights Panel or the Actions section of the page.
Workflow Interaction: When a fundraiser clicks the Generate Document button, a modal opens that allows them to:
Select from the predefined Nonprofit Cloud templates (e.g., "Standard Thank You" or "Year-End Tax Receipt").
● Choose the output format (PDF or Word).
Preview the document with live donor data merged.
Completion: Once the document is generated, the system can automatically update the "Acknowledgment Status" on the Gift Transaction record, ensuring the data remains accurate.
Why other options are incorrect:
Create Summary (Option A): This button is typically used for generating internal summaries or record descriptions, not for external-facing document generation based on templates.
FlexCard (Option B): While a FlexCard can display information visually, it is not the mechanism used to produce a downloadable or printable letter. The Generate Document button is the specific functional trigger for the DocGen engine in NPC.