While Duplicate Rules and Matching Rules are essential for preventing new duplicates from being created, they do not help with a database that already contains existing duplicates (which is common after large direct mail imports).12 The Solution for "Auto13mating the Search":
On Unlimited Edition, Salesforce provides a feature called Duplicate Jobs.
* Scanning the Database: Unlike rules that fire during a save, a Duplicate Job runs a scan across the entire existing database (or a specific segment) to find existing duplicate records based on your Matching Rules.
* Reporting: Once the job completes, it generates a list of "Duplicate Record Sets." This allows the nonprofit's data integrity team to review and merge records in bulk.
* Use Case: For a direct mail organization, running a Duplicate Job before a large mailing ensures they aren't wasting money by sending two identical letters to the same household.
Why other options are incorrect:
* Duplicate/Matching Rules (Options A & C): These act as "gatekeepers" during data entry. They find duplicates only when a record is created or edited; they do not proactively "search" the existing database.
* Scheduled Apex (Option D): This is a custom coding solution. A consultant should always recommend native, declarative features like Duplicate Jobs before suggesting custom code.

For a small volume of contacts (150) and a simple one-off requirement like an event cancellation, standard Salesforce functionality is the most cost-effective and efficient choice. Send List Email is a native Lightning Experience feature that meets all the organization's criteria without the complexity of a third-party marketing tool.
How Send List Email Meets the Requirements:
* Direct Send: Users can select up to 2,000 contacts from a list view or a campaign and click Send List Email. This uses Salesforce's internal mail servers (or the organization's connected Office 365/Gmail account).
* Send History: Every list email sent is automatically recorded in the Activity History (specifically the
"HTML Email Status" or "Emails" related list) on the Contact record. This satisfies the requirement to
"view the send history."
* Manage Bounces: Salesforce has a native "Email Bounce Management" feature. If an email address is invalid, a warning icon appears next to the email address on the Contact record, and the staff can see the
"Bounce Reason."
* Resending: Because the send history is logged as an activity, staff can easily identify who didn't receive the message and trigger a follow-up email manually or by creating a filtered list of "bounced" contacts.
Why other options are incorrect:
* Elevate (Option A): This is a payment processing platform for fundraising and has no native bulk email capabilities for event management.
* Email-to-Case (Option B): This is a support tool for receiving incoming emails and turning them into tickets; it is not for proactive event outreach.
* Account Engagement (Option D): Formerly known as Pardot, this is a robust marketing automation platform. While it could do this, it is considered "overkill" for a one-off 150-person email and requires a separate, significant license and technical setup.

In the modern Nonprofit Cloud (NPC) for Fundraising, the generation of gift acknowledgments and tax receipts is powered by Document Generation (DocGen) technology. This system allows organizations to move beyond simple mail merges into a robust, server-side document creation process.
To manage these templates effectively, a consultant must understand the distinction between "Designers" and
"Users" within the permission set framework.
* FundraisingAccess: This is the foundational permission set group (or permission set) that grants the user rights to interact with fundraising-specific objects like Gift Transactions, Gift Commitments, and Gift Designations. Without this, the user cannot access the data that needs to be merged into the templates.
* DocGen Designer: This specific permission set is required for administrative or "super user" tasks. A user with the DocGen Designer permission set is granted the ability to upload, manage, and customize the .docx or .pptx files that serve as the templates. This includes mapping Salesforce fields to the document tokens and organizing the library of available templates for the rest of the team.
* DocGen User (Contrast): In contrast, the DocGen User permission set is intended for staff who only need to trigger the creation of a document (e.g., clicking a "Generate Receipt" button). They cannot upload new templates or change the underlying logic of existing ones.
Step-by-Step Assignment Logic:
* Navigate to Setup > Users > Permission Sets.
* Locate the DocGen Designer permission set and assign it to the staff responsible for template creation.
* Ensure the user also has the SalesforceCRM Content User license enabled on their User record, as templates are stored and managed within Salesforce Files/Content.
* Verify that the FundraisingAccess group is assigned to provide the necessary object-level permissions.
By correctly separating these roles, a consultant ensures that only authorized personnel can modify the official legal and branding language used in the organization's donor communications.

Salesforce Shield Platform Encryption provides high-level security, but it has significant "functional trade- offs" because the system cannot "read" encrypted data in the same way it reads plain text for certain automated processes.
Three Critical NPSP Considerations:
* Soft Credit Rollup Failure (C): NPSP's Customizable Rollups often use the Role Name on the Partial Soft Credit object to determine how to aggregate credits. Because encryption prevents the database from performing "Group By" or "Where" queries on that field effectively, the nightly rollup jobs will fail to process those credits.
* Merge Contacts Failure (D): The NPSP Contact Merge tool relies on identifying and comparing names. If the Contact Name is encrypted, the SOSL/SOQL queries used by the "Merge" button cannot properly index or find the records, rendering the specialized NPSP merge interface unusable.
* Data Import Matching (E): The NPSP Data Importer relies heavily on "Matching Rules." If you are trying to match a legacy donor ID or a custom unique ID that has been encrypted, the system cannot perform the "Exact Match" check needed to prevent duplicates during the import process.
Why other options are incorrect:
* Option A: Standard address fields on Account/Contact can be encrypted with Shield, so this is not a limitation.
* Option B: The Data Import object does not support "all fields" for encryption; like most objects, it has specific supported field types and limits.

The Actionable Relationship Center (ARC) is the premier visualization tool in Salesforce Nonprofit Cloud for mapping complex constituent webs. Unlike a standard related list, which shows data in a flat table format, ARC provides a dynamic, multi-level graph that allows fundraisers and case managers to explore the connections between people, households, and organizations.
Key Capabilities for a Consultant:
* Visual Hierarchy: ARC displays nodes representing records (e.g., a Donor, their Spouse, their Employer, and a Foundation board they sit on). Each node can be expanded to show further related records, such as the Foundation's recent grants or the Spouse's individual contact details.
* Standard and Custom Relationships: It natively supports the Party Relationship Model used in NPC, including Account-Account Relationships and Contact-Contact Relationships. This allows for the visualization of both professional affiliations and personal family ties in one view.
* Direct Interaction: It is "Actionable" because users can perform tasks directly from the graph. A consultant can configure the graph so a gift officer can create a new "Follow-up Task" or "Note" on a related relative's record without ever leaving the primary donor's page.
* Customization via Templates: Consultants can build custom ARC graphs using the ARC Graph Builder in Setup. You can choose which objects appear, what fields are shown in the side panel when a node is clicked, and even add filters to show only "Active" relationships.
While Flexcards (Option A) are used to display data visually, they are generally used for summarizing record fields rather than interactive relationship mapping. The Contact Profile (Option B) is a data storage object for wealth and personal attributes but does not provide the interactive, spider-web style graph that characterizes the ARC experience.