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.

In the modern Salesforce Lightning experience, the Learning Path is the best tool for an admin or consultant to deliver targeted training directly within the flow of work.
What is a Learning Path?
A Learning Path allows a consultant to curate specific Trailhead modules, internal documents, or videos and assign them to specific users or groups based on the page they are currently viewing. For a nonprofit implementing NPSP, the consultant can:
* Curate Content: Select existing Trailhead modules like "Fundraising with Nonprofit Success Pack."
* Assign to Users: Target the training specifically to the "Fundraising" profile or "Gift Officer" team.
* In-App Access: Instead of forcing staff to leave Salesforce to search a separate help portal, the training appears in the "Learning" side panel (represented by the graduation cap icon) while they are actually looking at Opportunity or Contact records.
* Track Progress: Managers can see who has completed the assigned modules, making it a powerful tool for onboarding and change management.
Why other options are incorrect:
* Salesforce Help and Training (Option A): This is the documentation portal. While useful, it is a
"pull" resource (staff have to go find it) rather than a "push" resource (assigned by the admin).
* Trailblazer Community (Option C): This is a forum for discussion and peer support, not a structured training assignment platform.
* AppExchange Report (Option D): The AppExchange is for downloading apps; there is no such thing as an "AppExchange Report" used for assigning training.

When a nonprofit shifts its mission from direct service delivery (program management) to funding other entities, it moves into the role of a "Grantmaker." In the Salesforce Nonprofit Cloud ecosystem, this specific business process is supported by the Grantmaking module.
The Grantmaking license provides access to a specialized data model and set of features designed for the full grant lifecycle:
* Funding Opportunities: Grantmakers use this object to define the available grants, including eligibility criteria, total funding amounts, and application deadlines.
* Individual Applications: This is the core object for tracking incoming requests for funding. It allows the organization to manage the review process, due diligence, and scoring of applications from other nonprofits or community groups.
* Funding Awards and Disbursements: Once an application is approved, the system tracks the Funding Award and schedules the actual payment of "financial capital" through Disbursements.
* Grantee Portal: Grantmaking often utilizes an Experience Cloud site where applicants can submit their proposals, view their status, and submit required progress reports.
While Program Management (Option B) is used for direct services (like running a food bank), and Outcome Management (Option A) is used to measure the impact of those services, Grantmaking is the specific functional area required for "delivering financial capital" and managing funding applications. For a consultant, identifying this shift in business model is key to ensuring the organization has the correct objects- such as Budget, Funding Opportunity, and Application-available in their org.

Accounting Subledger (ASL) is designed to bridge the gap between Fundraising (Salesforce) and Finance (General Ledger). It uses a "Stage to State" mapping to determine when a fundraising record is ready to be processed as an accounting transaction.
In the Starter Edition of ASL, the system looks for specific "States" to trigger record creation:
* Committed: This state indicates that a donor has made a formal promise to give (a Pledge), but the cash has not necessarily been received yet. In accounting terms, this creates an Accounts Receivable entry.
* Finalized: This state usually indicates that the cash has been received and the transaction is closed.
The Solution for Pledges:
To meet the requirement of exporting pledges "when they are booked," the consultant must map the organization's "Pledged" Opportunity stage to the Committed Accounting State.
Step-by-Step Configuration:
* Navigate to Accounting Subledger Settings.
* Go to Stage to State Mapping.
* Locate the Pledged stage (or whatever custom stage the nonprofit uses for booked pledges).
* Map this stage to Committed.
* Save the settings and run the subledger job.
Once this mapping is in place, as soon as an Opportunity is moved to the "Pledged" stage, ASL will generate Ledger Entries that reflect the revenue as "Committed." These entries can then be exported to the external financial system to record the expected income on the organization's books.

The fundraising data model in the new Nonprofit Cloud (NPC) differs significantly from the older NPSP
"Recurring Donations" object. NPC utilizes the Fundraising feature set, which is built on a high-performance architecture shared with other Industry Clouds.
To manage recurring giving, two primary objects are required:
* Gift Commitment: This object represents the donor's "promise" or agreement to give a certain amount over time. It stores high-level information such as the total amount of the commitment, the donor (Person Account), and the status (e.g., Active, Paused, or Fulfilled).
* Gift Commitment Schedule: This is the engine that drives the frequency of the gift. It defines when and how often the donation should be processed (e.g., Monthly on the 15th, or Weekly on Mondays). A single Gift Commitment can actually have multiple schedules if a donor has a complex giving plan.
The Workflow for a Consultant:
* Create the Gift Commitment: When a donor signs up for a monthly giving program, the consultant (or the automated system) creates a Gift Commitment record.
* Define the Schedule: A Gift Commitment Schedule record is then linked to that commitment, specifying the recurring transaction amount and the transaction period.
* Automated Processing: Once these are active, the Nonprofit Cloud's Gift Processing engine uses the schedule to automatically generate Gift Transaction records (which are the equivalent of "received" donations) on the specified dates.
Option A is incorrect because "Opportunity" is part of the legacy NPSP model or standard Sales Cloud; while NPC can use Opportunities, the specific recurring logic in NPC is handled by Gift Commitments. Option C is incorrect because Gift Designation is used to track the fund or purpose the money is for (e.g., "Scholarship Fund"), which is applicable to both one-time and recurring gifts, but is not the object that establishes the recurring nature of the gift.