Explanation:
Before installing any managed package, especially one that adds objects and automation like Volunteers for Salesforce (V4S), a consultant should perform a technical assessment of the target org. V4S uses customizable roll-up summary fields to calculate volunteer hours and other aggregates. The consultant must ensure the org has not already reached its limit of roll-up summary fields to avoid installation failure or performance issues.

Correct Option:

D. Compare usage of roll-up summary fields to limits.
Salesforce orgs have a governor limit on the number of roll-up summary fields allowed (varies by edition). V4S installation creates several new roll-up fields. If the org is near or at this limit, the installation may fail or cripple future customization. Checking and planning for this limit is a critical pre-installation step.

Incorrect Options:

A. Apply for license donation for Volunteers for Salesforce.
V4S is a free, open-source managed package available on the AppExchange; no license donation application is required. This step is unnecessary and incorrect.

B. Check that the nonprofit has the most recent NPSP release.
While V4S is designed to work with NPSP, it does not require NPSP and can be installed in a standalone Salesforce org. Checking the NPSP release is not a prerequisite. Compatibility with the Salesforce platform version is more relevant, but that's typically managed by the package itself.

C. Ensure the Program Management Module Is already Installed.
The Program Management Module is part of Nonprofit Cloud for case management and is completely unrelated to volunteer management. V4S does not depend on it; they are separate products for different use cases.

Reference:
Volunteers for Salesforce installation guide and Salesforce help on "Limits Quick Reference." The pre-installation checklist for V4S includes verifying roll-up summary field limits because the package adds multiple such fields. Exceeding this hard limit can block installation.

Explanation:
Governance establishes the framework for decision-making, roles, and processes to ensure the Salesforce implementation is sustainable, secure, and aligned with business goals. For leadership hesitant about upfront investment, the consultant must emphasize tangible benefits that directly impact the project's success and the organization's bottom line—specifically avoiding future costs, ensuring adherence to regulations, and maintaining project momentum.

Correct Options:

A. Cost savings
Effective governance prevents costly rework, redundant licenses, and uncontrolled customizations that are expensive to fix later. By establishing clear standards upfront, the nonprofit avoids waste and ensures budget efficiency.

B. Compliance
Nonprofits often handle sensitive donor and beneficiary data subject to regulations (e.g., GDPR, PCI, funder requirements). Governance ensures data handling, security, and reporting processes meet legal and contractual obligations, reducing risk of fines or loss of funding.

E. Delivery speed
A clear governance model accelerates decision-making by defining who has authority, streamlining approvals, and reducing bottlenecks. This keeps the project on schedule and ensures timely delivery of value, addressing leadership's desire for efficiency.

Incorrect Options:

C. Security
While security is a critical outcome of good governance, it is often viewed as a subset of compliance and risk management. In this context, security is implicitly covered under Compliance (B). Leadership may see it as a technical issue rather than a governance driver.

D. Technical interoperability
This refers to how well systems integrate and communicate. While governance can influence integration standards, technical interoperability is more of a technical architecture concern than a primary governance selling point to hesitant leadership focused on time and cost.

Reference:
Salesforce implementation best practices and governance frameworks (e.g., Salesforce Governance Guide). They highlight that proactive governance delivers cost savings, ensures compliance, and increases delivery speed by preventing chaos, rework, and misalignment—key points to persuade leadership of its upfront value.

Explanation:
To test upcoming release features (including new Nonprofit Cloud features), a consultant must use a Sandbox with the upcoming release loaded. Salesforce provides special “Preview” sandboxes that automatically receive the new release early. The only way to get a sandbox on the preview release is to have a sandbox that is refreshed immediately before or during the published preview window. Refreshing just prior to the preview period ensures the sandbox receives the new release when the preview window opens.

Question Correct Option:

A. Refresh a preview Instance sandbox just prior to sandbox preview period.
This is the required and officially supported method. Salesforce documentation explicitly states that existing sandboxes refreshed shortly before the preview window (or during it) will be upgraded to the upcoming release automatically, giving administrators and consultants early access to test new features, including Nonprofit Cloud enhancements, weeks before production orgs are upgraded.

Incorrect Options:

B. Refresh a preview instance sandbox during the sandbox preview period.
While refreshing during the preview period may work in some cases, Salesforce recommends and guarantees the preview upgrade only when the refresh is performed just prior to or at the very start of the preview window. Refreshing later in the period can result in receiving the current release instead.

C. Create a new sandbox during the sandbox preview period.
New sandboxes created during the preview window are provisioned with the current production release, not the upcoming preview release. Only refreshes of existing sandboxes qualify for the automatic preview upgrade.

D. Create a preview instance sandbox during the sandbox preview period.
There is no sandbox type called “preview instance sandbox” that you manually create. Salesforce automatically designates eligible refreshed sandboxes as preview instances; you cannot force-create one directly.

Reference:
Salesforce Help: “Sandbox Preview Instructions” (Winter/Summer/Spring release notes)

Explanation:
The core problem is duplicate manual entry between Salesforce (for fundraising/CRM) and an external accounting system (for financials). The goal is to eliminate the manual sync by automatically exporting transaction data from Salesforce to the accounting system. The solution needs to be a bi-directional or export-oriented integration, not just a better import tool into Salesforce.

Correct Option:

A. Accounting Subledger
Accounting Subledger (part of Nonprofit Cloud) is designed specifically for this. It sits between Salesforce (CRM) and the external General Ledger (GL). It automatically creates accounting entries (Ledger Entries) in Salesforce from fundraising transactions (Opportunities, Payments) and can export them to the external accounting system via APIs or files, eliminating duplicate manual entry and ensuring reconciliation.

Incorrect Options:

B. NPSP Data Importer Templates
This tool is for importing data into Salesforce (e.g., from spreadsheets), not for exporting data out to an accounting system. It does not solve the dual-entry problem; it might even add more import work.

C. Data Import Wizard
Similar to B, this is for importing data into Salesforce. It does not help with exporting Salesforce data to an external accounting system.

D. Advanced Mapping
Advanced Mapping is a feature of the Data Import tool used to map CSV columns to Salesforce fields during imports. It is irrelevant to the problem of syncing data out of Salesforce to an accounting system.

Reference:
Nonprofit Cloud documentation: "Accounting Subledger." This module is built to automate the bridge between fundraising CRM and financial systems, generating GAAP-compliant journal entries in Salesforce that can be exported to external GLs, directly addressing the manual reconciliation pain point.

Explanation:
Wealth scoring (or wealth screening) involves appending external data about a prospect's capacity to give (e.g., estimated net worth, stock holdings, real estate) to Salesforce records. Salesforce does not have a native wealth scoring product. Therefore, integration requires a third-party data provider that specializes in this service, which typically offers a connector or app on the Salesforce AppExchange to sync data into standard or custom fields.

Correct Option:

D. A third-party app on the AppExchange
The AppExchange hosts numerous wealth screening and prospect research applications (e.g., iWave, DonorSearch, WealthEngine) that integrate with Salesforce/NPSP. These apps provide connectors to pull wealth indicators and scores into Contact or Account records, meeting the requirement directly.

Incorrect Options:

A. Pardot (Marketing Cloud Account Engagement)
Pardot is a B2B marketing automation tool focused on lead scoring based on engagement (email opens, website visits). It does not provide wealth or philanthropic capacity scoring based on external financial data.

B. Philanthropy Cloud
Salesforce Philanthropy Cloud is a platform for employee giving and volunteering, connecting corporations with charitable causes. It is not a wealth scoring or prospect research tool for individual donor capacity.

C. Salesforce Optimizer
The Salesforce Optimizer is a free diagnostic tool that analyzes an org's setup for performance, security, and health recommendations. It has nothing to do with donor wealth scoring or external data integration.

Reference:
Nonprofit prospecting and donor research best practices. Consultants routinely recommend AppExchange applications for wealth screening, as these are specialized third-party services that integrate with Salesforce to enhance donor profiles with propensity and capacity scores.