Explanation:
A Lean Governance Framework for a Salesforce implementation focuses on agile, iterative processes that ensure the system evolves in a controlled, compliant, and user-centric manner. It's not just about roles and feedback; it's about the structured process for developing, deploying, and maintaining the system. The Software Development Lifecycle (SDLC) is the core operational process within such a framework, defining how changes are requested, built, tested, and released.

Correct Option:

B. Software Development Lifecycle (SDLC)
The SDLC is a fundamental process within a Lean Governance Framework. It provides the structured methodology for managing change—from requirement gathering and development to testing, deployment, and post-launch review. This process directly ensures compliance (through testing and controls), risk assessment (via impact analysis), and successful rollout (through user acceptance testing and training).

Incorrect Options:

A. Executive buy-in
While executive sponsorship is critical for governance success, it is an enabler or input, not a process within the framework itself. The Lean Governance Framework would include processes for securing and maintaining buy-in, but "buy-in" itself is not the process.

C. End user management
Managing end users (onboarding, training, support) is an important operational activity, but it is typically an outcome of processes defined within the governance framework (like change management). It is not the core governance process itself.

D. Power user feedback
Feedback loops (including from power users) are essential for continuous improvement and are part of the SDLC's planning and review phases. However, "feedback" alone is not a standalone process; it is integrated into the broader SDLC and change management processes.

Reference:
Salesforce's Governance & Implementation Methodology guides, which emphasize establishing a lightweight, agile SDLC as a core process within a governance model. This ensures changes are delivered quickly but safely, managing risk and ensuring user adoption in a dynamic environment.

Explanation:
When using NPSP Data Import for Contacts, the system can automatically create associated Household Accounts. If this fails despite correct mappings, the issue is typically that the system cannot create the required parent Account record. This failure is almost always due to missing data required by either the import process itself or by validation rules on the Account object that must be satisfied upon record creation.

Correct Options:

C. If the required fields are included in the import.
The Data Import object itself has required fields. For a Contact import, the Contact1_Firstname and Contact1_Lastname fields are mandatory. If these are missing for a given row, the entire import for that row will fail, preventing both the Contact and the automatic Account creation.

D. If there are required fields on the Account.
If the Account object has validation rules or system-required fields (beyond Name) that are not populated by the Data Import process, the automatic Account creation will fail.

The import process automatically sets the new Account's Name using the Household Naming convention, but if another field is required (e.g., a custom Region__c field), the process cannot provide a value and will fail to create the Account.
Incorrect Options:

A. If all the email addresses are properly formatted.
While important for data quality, an improperly formatted email address on a Contact is unlikely to prevent the Account from being created. The Account creation is a separate DML operation. Validation rules on the Contact might fail, but the core issue described is specifically about Account creation.

B. If all records have a phone number.
A phone number is not a system-required field for Contact or Account records in a standard NPSP configuration. Its absence should not block the automatic creation of an Account during a Data Import.

Reference:
NPSP Documentation on Using the Data Import Tool. It specifies that imports will fail if required fields on the target object are not mapped or populated, and highlights that validation rules on the target objects (like Account) are executed during the import process and can cause failures.

Explanation:
The requirement is to track three distinct areas: fundraising (traditional NPSP/Nonprofit Cloud), courses, and training participation (academic/educational activities). This combination spans donor management and educational program management. The consultant must recommend a data architecture that can handle both domains within a single Salesforce org without creating siloed solutions.

Correct Option:

D. Use Education Data Architecture to track fundraising, courses, and training participation.
The Education Data Architecture (EDA) is the managed package (formerly HEDA) designed to manage the academic lifecycle—students, courses, terms, and program participation. It can coexist with NPSP/Nonprofit Cloud in the same org. This allows the nonprofit to use NPSP for fundraising and EDA for tracking courses and training, providing a unified platform for both needs.

Incorrect Options:

A. Add Program Management Module to track courses and training participation.
The Program Management Module is for social service case management (tracking clients, service delivery, outcomes). It is not designed for academic course catalogs, enrollment, and academic participation tracking. Using it for courses/training would be a misuse of the data model.

B. Add Volunteers for Salesforce to track courses and training participation.
Volunteers for Salesforce (V4S) is for managing volunteer shifts, hours, and jobs. While training could be a type of volunteer activity, V4S is not structured to manage a curriculum, course catalog, or academic progress. It is not the appropriate tool for educational program tracking.

C. Use Engagement Plans for donor engagement that includes courses and training participation.
Engagement Plans automate a sequence of tasks (emails, calls) for fundraisers. They are an internal workflow tool, not a data model for tracking external participant enrollment, course completion, or academic records. They cannot track the structure or outcomes of courses and training programs.

Reference:
Salesforce Architects and Implementation Guides for Nonprofit Cloud and Education Cloud coexistence. EDA is the standard package for educational institutions and lifelong learning programs. For a nonprofit that also fundraises, using NPSP/Nonprofit Cloud alongside EDA is the documented approach to manage both fundraising and educational programs in a single org.

Explanation:
The requirement is to grant specific users (case managers) the ability to create and edit records of a particular object (service delivery records, likely Program Engagements or Service Deliveries within PMM). This is a granular permission issue: granting Create, Read, Edit, Delete (CRED) access to an object and its fields. In Salesforce, this level of access is controlled by Profiles and Permission Sets, not by sharing or roles alone.

Correct Option:

A. Permission Sets
Permission Sets are the correct tool to grant additional object and field permissions to specific users without modifying their base profile. The consultant can create a Permission Set that grants Create and Edit access to the relevant Program Management objects and assign it to case managers.

Incorrect Options:

B. Sharing Rules
Sharing Rules control record-level visibility (which records a user can see), not object-level permissions (whether they can create or edit records of that type at all). A user must first have CRED permissions via their Profile or Permission Set; sharing rules then determine which specific records they can access.

C. License Type
The License Type determines which features and objects are available in the org (e.g., Nonprofit Cloud licenses include PMM). However, it does not grant granular permissions to individual users. All case managers likely already have an appropriate license; the issue is configuring their permissions within that license.

D. Role Hierarchy
The Role Hierarchy controls record-level visibility based on a user's role (users in higher roles can see records owned by users below them). Like sharing rules, it does not grant object-level create/edit permissions. It also does not help if case managers need to edit records owned by others at the same role level.

Reference:
Salesforce Help: "Permission Sets." Object-level permissions (CRED) are managed via Profiles (base permissions) and Permission Sets (additional permissions). For granting specific user groups like case managers access to PMM objects, Permission Sets are the standard, flexible tool.

Explanation:
When a nonprofit organization learns a donor is deceased, the primary action is to update the Contact record to reflect this status accurately. The Nonprofit Success Pack (NPSP) provides a dedicated, standard field for this purpose: the Deceased checkbox field on the Contact object. Selecting this field is the most appropriate action because it automatically triggers behind-the-scenes NPSP logic to prevent future outreach, roll up the status to the Household, and ensure data integrity without deleting valuable historical information.

Correct Option: C

C. Select the Deceased field
Rationale: The Deceased field is a standard NPSP checkbox field specifically designed to handle this scenario.

NPSP Automation: When this field is selected, it triggers NPSP automation that:

Automatically updates soft credit calculations to ensure the deceased donor no longer receives soft credit for gifts made by their spouse or partner.

Prevents future mailing and outreach by implicitly or explicitly linking to the organization's mailing suppression lists.

Maintains the donor's historical giving data (Opportunities, Affiliations, Relationships) for accurate reporting and auditing.

Incorrect Option:

A. Delete the values in the phone and email fields
Rationale: Deleting communication fields is insufficient for permanent suppression. While it stops communication through those channels, it does not flag the individual as deceased, meaning they may still appear on reports, be included in future segments if those fields aren't the primary filter, and their death status is not permanently recorded.

B. Delete the Contact record
Rationale: Deleting the Contact record is highly discouraged. It results in the permanent loss of all historical giving data (Opportunities, Payments, Relationships) associated with the donor. This loss of historical data is unacceptable for financial reporting, auditing, and understanding the full history of the organization's relationship with the donor's family.

D. Select the Do Not Email, Do Not Contact, and Email Opt Out fields
Rationale: While selecting these fields will stop immediate communication, it misrepresents the reason for the suppression. These fields are typically used for living donors who have requested suppression (e.g., preference management). Using the dedicated Deceased field (C) is a more accurate and comprehensive solution that triggers the correct NPSP data model updates for this specific life event.

Reference:
NPSP Documentation - Manage Deceased Contacts - Salesforce Help