Explanation:
This scenario involves sharing specific custom object records (Assessments, Notes, Alerts) with a defined set of staff who are not necessarily the record owners. In Salesforce, sharing records requires both object-level permissions (to see the object type) and record-level permissions (to see specific records). A two-part approach is needed: 1) grant object access, and 2) share the records.

Correct Options:

B. Create a Public Group of staff that need access to this information.
A Public Group is a collection of users (and potentially other groups) used as a recipient in Sharing Rules. Creating this group is the first step to identify who should get access. The group can then be referenced in the sharing rules to grant access to the records.

C. Create a permission set that grants Read/Write access to Assessments, Client Notes, and Client Alerts objects.
Object-level permissions (CRED) are required for users to see any records of that object type. A Permission Set is the appropriate tool to grant these permissions to the relevant staff without modifying their profiles. This ensures they can see the object tabs and lists.

Incorrect Options:

A. Create Sharing Rules for Assessments, Client Notes, and Client Alerts that share these with the public group.
While Sharing Rules are necessary for record-level access, they cannot be created for custom objects in all orgs unless the custom object's Sharing Setting is set to Controlled by Parent or Public Read/Write. For standalone custom objects, sharing is often managed via Manual Sharing, Apex, or Criteria-Based Sharing if available. A blanket sharing rule to a public group may not be configurable without specific org settings. However, this could be valid if the objects are set to "Private" and criteria-based sharing is used, but it's less straightforward than the standard approach using Permission Sets and Groups.

D. Create a Private Group of staff that need access to this information.
Private Groups are used within Chatter for collaboration and do not function as recipients for Sharing Rules. Sharing rules require Public Groups, Roles, or Roles and Subordinates. A Private Group cannot be used to share records system-wide.
Reference:
Salesforce Help: "Grant Access Using Hierarchies, Sharing Rules, and Manual Sharing" and "Create a Public Group." The standard pattern for sharing custom object data is:
Use Permission Sets to grant object-level CRED access.
Use Public Groups to define the user set.
Use Sharing Rules (if the object supports it) or Apex Managed Sharing to grant record-level access to that group.

Explanation:
The NPSP Account Conversion Utility successfully converts One-to-One Accounts to Household Accounts, creates the new Household Account records, moves all Contacts to the new Households, and updates most standard relationships automatically. However, Opportunities remain attached to the old One-to-One Accounts because Salesforce does not allow mass-reparenting of closed Opportunities. The consultant must manually move (or reparent) these Opportunities to the correct new Household Account (or to the correct Contact in some configurations) after conversion completes.

Correct Option:

B – Move Opportunities from the One-to-One Accounts to the new Household Accounts and Contacts.
Closed/Won Opportunities cannot be mass-reparented via the utility due to Salesforce platform restrictions.

The consultant typically uses Data Loader, NPSP’s “Move Opportunities” tool, or manual reparenting to associate them with the new Household Account (or primary Contact).

This is the only major manual post-conversion step required.

Incorrect Option:

A – Move Tasks from the One-to-One Accounts to the new Household Accounts.
Open and closed Tasks/Events are automatically reparented by the Conversion Utility to the new Household Account.

C – Delete One-to-One account records.
While old One-to-One Accounts can eventually be deleted after cleanup, this is not required immediately and many organizations archive them instead.

D – Select a Primary Contact for each Household Account.
The Conversion Utility automatically designates a Primary Contact (usually the first Contact moved into the Household).

Reference:
NPSP Documentation → Account Model Conversion → “One-to-One to Household Conversion”

Explanation:
The requirement is to categorize donors (Contacts) into recognition levels (Gold, Silver, Bronze) based on their year-to-date giving. This is a classic use case for donor recognition and stewardship. NPSP has a built-in, no-code feature specifically designed for this purpose: Levels. Levels automatically calculate a Contact's cumulative giving (with options for date ranges like "This Year") and assign a corresponding recognition level, which is then displayed on the Contact record.

Correct Option:

C. Set up NPSP Levels for the categories based on Total Gifts This Year.
NPSP Levels are a dedicated feature in Recurring Donations & Levels Settings.

You define Level names (Gold, Silver, Bronze) and the minimum amount for each (e.g., Gold = $1,000+).

You specify the source field for the calculation, such as "Total Gifts This Year" from the Contact's Soft Credit Rollups.

NPSP automatically evaluates each Contact's giving and assigns/updates their Level accordingly, with no custom automation needed.

Incorrect Option:

A. Create a picklist field that will display the categories based on the Total Gifts This Year field.
A simple picklist field is static; it cannot automatically calculate and update its value based on another field's changing total. It would require manual updating, defeating the purpose of automated donor recognition.

B. Create a custom field on the Opportunity that will display the categories and a process in Process Builder to populate the value based on the Total Gifts This Year field.
This is misplaced logic. Donor Levels are an attribute of the Contact (the donor), not of individual Opportunities (gifts). Building automation on the Opportunity to try to set a Contact-level category is unnecessarily complex and would require aggregating gifts, which is what the NPSP Levels feature already does efficiently.

D. Create a custom field on the Opportunity that will display the categories and a custom trigger to populate the value based on the Total Gifts This Year field.
Similar to Option B, this places the logic on the wrong object (Opportunity instead of Contact). More importantly, writing a custom trigger is unnecessary "re-inventing the wheel" when a robust, configurable, and supported standard NPSP feature (Levels) exists for this exact purpose.

Reference:
NPSP Documentation on Levels. This feature is explicitly described as a way to "recognize donors by creating donor levels" that are "automatically assigned to contacts based on their total giving within a specific date range," using fields like "Total Gifts Last Year" or "Total Gifts This Year."

Explanation:
The Case Plan Wizard in the Program Management Module is used to assign a pre-defined set of services or tasks (Action Items) to a client's Program Engagement. To use the wizard effectively, the underlying structure of services and objectives must be pre-configured as templates. This includes both the overarching goals (outcomes) and the specific action items (tasks/services) that make up the plan.

Correct Option:

B. A Program with Goals and Action Item Templates
Before using the Case Plan Wizard, the consultant must ensure:

A Program exists (the overall service offering).

Goals are defined within that Program (the target outcomes).

Action Item Templates are created and associated with those Goals (the specific tasks or services to be performed).

The wizard allows the case manager to select from these pre-configured Goals and Action Item Templates to quickly build a case plan for a client.

Incorrect Options:

A. A Program with Goals
This is incomplete. While Goals define the outcomes, the wizard needs Action Item Templates linked to those Goals to create the actual tasks/services assigned to the client. Without Action Item Templates, the case plan would have no actionable steps.

C. A new Case Plan
The Case Plan is the output of the wizard, not a prerequisite. The wizard is used to create a new Case Plan. Configuring templates (Goals and Action Items) must happen first.

D. A Program with Action Item Templates
This is also incomplete. Action Item Templates should be linked to Goals to provide structure and meaning. Creating them without associated Goals would make it difficult to organize services around client outcomes within the wizard.

Reference:
Nonprofit Cloud Program Management Module documentation: "Case Plan Wizard" and "Set Up Action Item Templates." The setup guide specifies that to use the wizard, you must first create Programs with Goals and then create Action Item Templates associated with those Goals. The wizard leverages this configuration to generate client-specific plans.

Explanation:
The nonprofit needs a comprehensive solution to train and test its employees on various skills (brand messaging, IT support, video publishing). This requirement goes beyond simple in-app guidance or help pages and demands a dedicated, scalable learning management system (LMS). myTrailhead (now known as Trailhead Academy and its associated tools for creating customized learning) is Salesforce's branded platform that allows organizations to create and publish customized learning modules (Trails, Modules, Quizzes) based on their specific content and skills, including brand messaging, internal procedures (like creating support cases), and specific technology tasks (like video publishing).

Correct Option: C

C. myTrailhead
Rationale: myTrailhead is Salesforce's platform that allows organizations to create a completely customized, branded learning environment.

Train and Test: It is specifically designed to handle training (via Modules and Trails) and testing (via Quizzes and Challenges), which directly addresses the core requirement.

Content: It allows the nonprofit to build and track learning paths for complex, organization-specific skills such as brand messaging, internal process training (like creating support cases), and technology skills (like publishing online videos).

Incorrect Option:

A. Custom Help pages
Rationale: Custom Help pages are passive documentation. They can display information but do not provide a mechanism for structured training, testing, tracking progress, or certifying completion of a skill, which are all key requirements for the nonprofit.

B. Prompts for In-App Guidance
Rationale: In-App Guidance Prompts are small messages used to provide quick tips or surface contextual information within the Salesforce interface (e.g., reminding a user how to fill out a field). They are excellent for minor process reminders but are not suitable for comprehensive training or formalized testing on complex skills like brand messaging or IT procedures.

D. Knowledge
Rationale: Knowledge is a solution for creating, publishing, and managing articles or documentation (e.g., FAQs, troubleshooting guides, how-to articles). It is a passive content repository and an excellent resource for support agents and self-service, but it is not a learning management system with built-in features for structured training, progress tracking, and formal quizzes/testing.

Reference:
Salesforce Trailhead Documentation - Learn about myTrailhead (Focus on custom content creation, training, and testing).