The Nonprofit Cloud has adopted the standard Salesforce Information Model for address management. In this model, the " Mailing Address " fields on the Person Account are merely a simplified view of a more robust underlying record.

When Automatic Person Account Mailing Address Synchronization is enabled, the system looks for the Contact Point Address (CPA) record marked as Is Primary and mirrors its values onto the Account header.

Managing Multiple Addresses:

Contact Point Address Object: This is the " source of truth " for all locations associated with a person.

The Related List: To manage a donor who has a " Home, " " Office, " and " Summer House " address, the consultant must add the Contact Point Addresses related list to the Person Account page layout.

Adding Records: From this related list, users can create new addresses, specify the Address Type , and set Seasonal Dates .

Synchronization: If a user changes the " Primary " flag from the Home CPA record to the Office CPA record, the synchronization feature will automatically update the Account ' s standard mailing fields to reflect the Office information.

Why other options are incorrect:

Location (Option A): This object is part of Field Service or Facilities Management and is used for physical sites/buildings, not for constituent mailing addresses.

Address (Option C): While there is a generic " Address " object, NPC specifically utilizes the Contact Point Address record, which is part of the " Contact Point " family of objects (alongside Email and Phone) used for communication preferences.

The Interaction Summary object is a cornerstone of the modern Nonprofit Cloud , borrowed from the Financial Services Cloud architecture to support professional-grade relationship management.

One of the primary advantages of Interaction Summaries over standard Salesforce " Notes " or " Activities " is the ability to relate a single set of notes to multiple participants and entities.

Configuration and Usage:

The Interaction: Represents the meeting itself (the " Event " ).

The Interaction Summary: This is the record where the detailed, often sensitive, notes are stored.

Multiple Individuals: Using the Interaction Participant related list, a consultant can link the summary to multiple Person Accounts . For example, if a caseworker meets with a mother and her two children, a single Interaction Summary can be created and then related to all three individual records. This ensures that the meeting notes appear on the " Timeline " and " Related Lists " for every person involved without the caseworker having to copy and paste the notes three times.

Confidentiality: Because these summaries often contain sensitive case data, they are designed to work with Compliant Data Sharing (CDS) . This allows the consultant to ensure that while the note is linked to multiple people, only staff with the correct " Participant Role " can actually read the contents.

Why other options are incorrect:

Action Plans (Option B): These are used for tracking a series of tasks or checklists (e.g., " Steps to complete intake " ). They are not a note-taking or conversation-tracking feature.

Outreach Summaries (Option C): This object is used in Fundraising to roll up the performance of a specific marketing campaign (e.g., total gifts and donor count from a direct mail appeal); it has no relation to client conversations or case notes.

In the Nonprofit Cloud Program Management data model, the architecture is designed to handle diverse services within a single program. To categorize and report on these services effectively, the Benefit Type object is used.

Categorization Logic:

The Program: You have a " Crisis Support Program. "

The Benefits: Within this program, you have two distinct services: " Food Basket Distribution " and " Rental Assistance Payment. "

The Grouping (Benefit Type): To group these for reporting, the consultant creates two Benefit Type records:

Goods: Linked to the " Food Basket Distribution " benefit.

Monetary Assistance: Linked to the " Rental Assistance Payment " benefit.

Step-by-Step Configuration:

Create Unit of Measure: First, define how each is measured (e.g., " Quantity " for baskets and " Currency " for assistance).

Create Benefit Type: Navigate to the Benefit Type object. Create a " Goods " type and a " Monetary " type. This object acts as the high-level category.

Link to Benefits: When creating the Benefit records, the consultant selects the appropriate Benefit Type .

By using Benefit Types , the nonprofit can run high-level reports across multiple programs to see, for example, " Total Monetary Assistance provided organization-wide " vs. " Total Goods distributed. "

Why other options are incorrect:

Benefit Disbursement (Option A): This is the record of an individual instance of a service being given to a person (e.g., " John Doe received 1 basket on Dec 21st " ). It is not a grouping or categorization object.

Program Enrollment (Option B): This links a specific Person Account to a Program . It tracks who is in the program, not how the different services within the program are categorized.

In the Nonprofit Cloud (NPC) Fundraising model, tracking donor intent—where the money is " designated " to go—is a core requirement for financial transparency. It is important to distinguish between the " Fund " and the " Allocation. "

Gift Designation (The Fund): This object represents the master fund or program area (e.g., " Clean Water Initiative " ). It is a static record that holds rollup data for that specific fund.

Gift Transaction Designation (The Allocation): This is the junction object that records the donor ' s specific intent for a particular gift. When a consultant identifies that a donation needs to be split across multiple programs, they create multiple Gift Transaction Designation records linked to a single Gift Transaction . This object stores the specific amount or percentage of that transaction that should be credited to a particular program.

Workflow During Solicitation:

During the solicitation of an Opportunity, the consultant or gift officer captures the donor’s intent. Even if the money has not yet arrived, the data model for NPC Fundraising (v59 and higher) anticipates that this intent will eventually live on the Gift Transaction Designation record. When an Opportunity is " Won " and converted into a Gift Transaction, the system uses the metadata captured during solicitation to populate these designation records.

Why other options are incorrect:

Gift Default Designation (Option C): These are used at the Campaign or Org-wide level to define where unrestricted or " unmarked " gifts should go by default. They are templates for inheritance rather than the record that tracks a specific donor ' s intent for a specific solicitation.

Gift Designation (Option B): As mentioned, this is the master definition of the fund, not the record of a specific allocation instance.

In NPSP, soft credits are fundamentally based on the Opportunity Contact Role (OCR) object. Even if " Partial Soft Credits " are used for splitting a gift, the primary mechanism for attributing a " Solicitor " to a donation is assigning them a specific role on the Opportunity.

Reporting Logic:

The Junction: The Opportunity Contact Role acts as the bridge between the Opportunity (the donation) and the Contact (the solicitor).

Standard Report Type: The standard report type Opportunities with Contact Roles allows the user to see the donor (the Account) and all related contacts who have a role on that gift.

Filtering: The Admin can filter this report by the " Role " field (e.g., Role EQUALS Solicitor). This surfaces exactly who the solicitor was for every donor ' s transaction.

Why other options are incorrect:

Option D: Partial Soft Credits is a more complex object used when multiple people get different dollar amounts of credit for a single gift. For a standard report showing " who the solicitor is, " the Contact Role is the simpler and more standard starting point.

Option A: Relationships track person-to-person ties (like " Spouse " or " Coworker " ), not who influenced a specific financial transaction.

Option B: This focuses on the Household structure rather than the individual donation influence history.

In the Nonprofit Success Pack (NPSP) , Salesforce implements strict data integrity guardrails to prevent the accidental loss of financial history. One of the most critical protections involves the deletion of Account records that have associated " financial " records.

According to NPSP documentation and standard database behavior:

Opportunity Protection: An Account cannot be deleted if it has any associated Opportunity (Donation) records that are in a " Closed/Won " stage. This is a hard-coded safety feature in NPSP ' s trigger framework.

The Error Message: When a user attempts to delete the Household Account, the system will halt the operation and display an error message such as: " This Account has Opportunities. You must delete all Opportunities before you can delete this Account. "

Audit Integrity: This ensures that the organization ' s total revenue figures remain accurate. If a household gave $1,000 last year, deleting that account would " orphan " or delete those gifts, leading to a reconciliation nightmare in the general ledger.

Regarding other objects:

Affiliations and Relationships (Option C): These are child records of the Contact , not the Account. If you were deleting a Contact , these might be impacted, but they do not typically prevent the deletion of the parent Account directly; the primary blocker is the financial transaction.

Option A and B: These are incorrect because they imply the operation would either complete silently or be ignored without feedback. Salesforce always provides a clear error when a trigger validation (like NPSP ' s Opportunity check) fails.

To successfully delete such an account, the admin would first have to delete (or re-parent) the Closed/Won Opportunities.