NPSP Configuration and Setup AGENTFORCE-NONPROFIT-CONSULTANT Practice Questions (Page 4)

Questions 16–19

1. 16expert · hard

   A nonprofit is installing NPSP in an org that already has a large amount of data and customizations. They want to minimize the risk of data loss and downtime. What is the best practice?

   • AInstall NPSP in production immediately and rely on the uninstall option if issues arise.
   • BDisable all customizations before installation to avoid conflicts.
   • CPerform a full sandbox test with a copy of production data, then schedule the production installation during a low-usage period.
   • DCreate a new org and migrate all data to it before installing NPSP.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A nonprofit wants to track donations that are received as pledges and then paid later. They want the Opportunity to be marked as 'Pledged' until payment is received, then 'Paid'. What should the admin configure in NPSP?

   • AUse the 'Opportunity Contact Role' to track the pledge status.
   • BUse a custom field on the Opportunity to track payment status and a workflow rule to update it.
   • CEnable 'Pledge Management' in NPSP Settings and set the default stage for Pledge Opportunities to 'Pledged'.
   • DCreate a Recurring Donation for each pledge and set the stage to 'Pledged'.
   Reveal Solution Discussion Select an answer first
4. 18expert · hard

   A nonprofit wants to ensure that all Opportunities created from donations have a specific record type and stage. They have set the default record type and stage in NPSP Donation Management Settings. However, some Opportunities are still being created with a different record type. What is the most likely cause?

   • AThe Opportunity stage is being overwritten by a workflow rule.
   • BThe user creating the Opportunity does not have access to the default record type.
   • CThe Opportunity is being created via a custom process that bypasses NPSP's default settings.
   • DThe default record type is not set as 'Active' in the Record Type settings.
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A nonprofit wants to capture a donor's preferred name and gender identity at the Contact level, but they also want to ensure that when a new Contact is created from a Lead conversion, the Lead's custom field values are copied over. The admin has enabled the 'Enable Lead Conversion' feature in NPSP Settings. What additional configuration is required to meet this requirement?

   • AUse Process Builder to copy Lead fields to Contact after conversion, since NPSP does not support custom field mapping.
   • BCreate custom fields on both Lead and Contact, then map them in the Lead Conversion mapping section of NPSP Settings.
   • CEnable the 'Auto-Convert Leads' setting in NPSP, which automatically copies all custom fields to Contact.
   • DAdd the fields to the Lead and Contact page layouts; Salesforce will copy them automatically during conversion.
   Reveal Solution Discussion Select an answer first