Explanation:
Integrating an external email platform (like Marketing Cloud, Mailchimp, etc.) involves syncing subscriber data and engagement activities to Salesforce. This creates records (e.g., Campaign Members, custom objects for opens/clicks) that consume data storage. The consultant must plan for data volume and retention policies to manage storage costs and system performance, and understand the required data model in NPSP for tracking subscribers.

Correct Options:

B. Email subscribers' activities can be retained for a certain length of time.
Email engagement data (opens, clicks) can generate a high volume of records. The consultant should define a data retention policy (e.g., keep activity records for 12 months) to limit storage consumption and avoid hitting data limits. This is a critical storage consideration.

D. Subscribers must be synced as Leads and Campaign Members in NPSP.
In the NPSP model, external subscribers are typically synced as Leads (if they are not yet Contacts) or Contacts, and their email campaign participation is tracked as Campaign Members. This creates Lead, Contact, and Campaign Member records, all of which consume storage. Understanding this required data model is essential for storage planning.

Incorrect Options:

A. Campaign Member records use less storage space than custom object records.
This is a misleading generalization. The storage footprint depends on the number of fields and data types, not the object type. A Campaign Member with many custom fields could use more storage than a lean custom object. This is not a reliable consideration.

C. Unsubscribed Leads should be deleted from Salesforce immediately.
Deleting records immediately is generally not advised for compliance and historical reporting. Unsubscribed Leads should be marked as unsubscribed and potentially archived or suppressed, not deleted. Immediate deletion is not a standard storage management practice.

Reference:
Salesforce Data Storage Management best practices and email integration guides. Key considerations include:

Data retention policies for high-volume activity data (Option B).

Understanding the data model impact (Leads, Contacts, Campaign Members) of syncing subscribers (Option D).
These help forecast storage needs and avoid limit issues.

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:
Loading a large volume of data can be slowed down significantly by background automation and system overhead. To optimize performance, you should temporarily disable non-essential processes that would otherwise run on each record during the load. This includes deferring system calculations that can be run later in bulk and turning off automated triggers.

Correct Options:

B. Defer Sharing Rule Calculation.
Deferring sharing rule calculation prevents Salesforce from recalculating sharing for each record as it's loaded. This dramatically speeds up the load, as sharing calculations are resource-intensive. After the load, you can manually recalculate sharing in bulk.

C. Disable related Apex classes in TDTM.
The Trigger Handler (TDTM) framework in NPSP controls automation (like rollups, address management, household naming). Disabling these handlers during a bulk load prevents Apex triggers from firing on each record, which reduces processing time and avoids CPU limit errors.

Incorrect Options:

A. Add record owners to Role Hierarchy.
Modifying the Role Hierarchy is a structural change to user permissions and record visibility, not a performance optimization step for data loading. It has no meaningful impact on load speed and could complicate sharing later.

D. Recalculate Sharing Rules.
Recalculating sharing rules is a post-load step, not a pre-load one. Doing this before the load would be pointless and would actually slow down the initial load because the system would be busy calculating sharing on existing data. You defer first, load, then recalculate.

Reference:
Salesforce Data Load Best Practices and NPSP Implementation Guides recommend:

Defer Sharing Calculations (via Setup → Data Management → Defer Sharing Calculations) before large data loads.

Disable Triggers/Automation (via NPSP Trigger Handlers or Apex code) to prevent governor limit exceptions and speed up DML operations.

Explanation:
Customizable Rollups (CRs) are the modern, flexible, and powerful feature in NPSP designed to aggregate data (like donation totals, last gift dates, etc.) from child records (Opportunities) up to parent records (Contacts and Accounts). CRs are an advanced feature built specifically to support the way NPSP structures its data. Because CRs rely heavily on the automatic relationship creation and management of individual records grouped under an Account, they are fundamentally dependent on and built for the Household Account Model, which is the recommended and standard NPSP data structure.

Correct Option: D

D. Customizable Rollups can only be used in orgs using the Household Account model.
Rationale: This is the core architectural requirement for NPSP's modern features. The NPSP Household Account Model automatically creates Household Accounts and manages the Contact-to-Account relationship for individuals. Customizable Rollups depend on these structured relationships to accurately calculate and push aggregated data (like a donor's total giving) from their Opportunities up to their Contact record and their Household Account record. CRs are not designed to function correctly or efficiently in the legacy 1-to-1 Account Model.

Incorrect Option:

A. After Customizable Rollups are enabled, it is irreversible
Rationale: This is incorrect. While it is strongly discouraged, you can disable the Customizable Rollup engine via NPSP Settings. Moreover, NPSP provides a tool to convert legacy User Defined Rollups (UDRs) to CRs, a process that is designed to be manageable, not irreversible. The system is designed for flexibility.

B. Advanced Currency Management is unsupported by Customizable Rollups.
Rationale: This is incorrect. Customizable Rollups support Advanced Currency Management (ACM). They are designed to aggregate currency fields, and when ACM is enabled, CRs properly handle conversions and currency codes in their calculations, ensuring accurate rollups of donation amounts in multi-currency environments.

C. Existing User Defined Rollups need to be re-created as Customizable Rollups.
Rationale: This is incorrect. NPSP provides a specific Rollup Conversion Utility within the NPSP Settings to help administrators automatically convert existing User Defined Rollups (UDRs) into the new Customizable Rollups (CRs) format. They do not need to be manually re-created from scratch.

Reference:
NPSP Customizable Rollups Documentation - Salesforce Help (Look for Prerequisites and Data Model requirements).

Explanation: The organization needs an email marketing tool that (1) measures engagement (opens, clicks, etc.) and (2) evaluates how well a prospect fits the ideal supporter profile. Pardot (now Marketing Cloud Account Engagement) is the only solution among the options that natively provides both Scoring (measuring engagement/behavior) and Grading (evaluating how closely a prospect matches the defined ideal supporter profile). These two features together give a complete picture of both interest and fit.

Correct Option:

A – Pardot Grading
Grading evaluates how closely a prospect matches the nonprofit’s ideal supporter profile (e.g., interests, giving capacity, location, volunteer history).

Grades (A, B, C, D, F) are adjusted based on explicit data (job title, wealth indicators) and demographic criteria, helping prioritize high-fit prospects.

D – Pardot Scoring
Scoring automatically increases or decreases a numeric score based on engagement actions (email opens +3, clicks +5, form submissions +20, etc.).

High scores indicate strong behavioral interest, allowing the nonprofit to identify actively engaged prospects for cultivation or solicitation.

Incorrect Option:

B – Marketing Cloud Measures
“Measures” is not an actual feature name in Marketing Cloud. Marketing Cloud has robust tracking (opens, clicks, bounces), but it does not have a native grading system to evaluate prospect fit.

C – Marketing Cloud Reporting
Marketing Cloud offers excellent reporting and Journey Builder analytics, but it lacks built-in profile grading and automated lead scoring comparable to Pardot. Scoring/grading would require complex custom Attribute-based work in Marketing Cloud.

Reference:
Pardot Help → Scoring and Grading Overview