[2026年03月] 実際問題を使ってNP-Con-102無料問題集サンプルと問題と練習テストエンジン [Q59-Q83]

[2026年03月] 実際問題を使ってNP-Con-102無料問題集サンプルと問題と練習テストエンジン

合格させるSalesforce NP-Con-102試験問題でテスト復刻エンジンとPDF

質問 # 59
A Household Account has Contacts with Affiliations, Relationships, and Closed/Won donations associated with it. What is the outcome when a system admin attempts to delete this Household Account record?

• A. The Household Account record and its standard related records are deleted.
• B. The Household Account record and its standard related records remain.
• C. Since Closed/Won donations are associated with the Account record, an error message displays.
• D. Since Affiliations and Relationships are associated with the Contacts in this Account, an error message displays.

正解：C

解説：
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.

質問 # 60
A nonprofit organization serves many families in their programs and want to track each family as a household. The organization serves diverse types of families, including blended families and split families, where some of the children divide their time between multiple households. How should the organization track these different family types?

• A. Create a Person Account for each family member. Create Contact Contact Relationship records between the family members.
• B. Create an Account for each family and Contacts for each family member. Create Party Role Relationship records between the family members.
• C. Create a Person Account for each family member. Use the New Group flow to simplify the necessary record creation.

正解：C

解説：
In the new Nonprofit Cloud, the "Household" concept is managed using the Group (Account) and Account Account Relationship model, underpinned by Person Accounts for individuals. This is a departure from the NPSP "Household Account" model.
To handle complex, modern family structures-such as children living in two separate households (split families) or blended families-the consultant follows a specific workflow:
* Individual Representation: Every family member is created as an individual Person Account. This ensures that their data (milestones, benefits, medical records) stays with them regardless of which household they are currently associated with.
* The New Group Flow: Salesforce provides a standard, guided flow called the New Group flow. When a consultant or caseworker uses this flow, it automates the creation of a "Business" Account with a record type of Group (representing the Household). It simultaneously creates the Account Account Relationship records that link the individual Person Accounts to that Group.
* Handling Split Families: Because the system uses a junction-based relationship model (Account Account Relationship), a single child (Person Account) can be linked to multiple Group Accounts (Household A and Household B). One can be marked as the "Primary" household, while the other is
"Secondary."
* Role Definition: Within these relationships, you can specify roles (e.g., "Parent," "Dependent," "Step- Parent") using the Party Role Relationship configuration.
Option B is insufficient because while it tracks person-to-person ties, it fails to aggregate the individuals into a "Household" unit (Group) for reporting and program enrollment. Option C is incorrect because it suggests using the legacy Account/Contact model, which is not the recommended best practice for individuals in the modern Nonprofit Cloud.

質問 # 61
A nonprofit organization plans to use Program and Case Management to track its substance abuse services.
When the Case Managers log in, they cannot see any of the Program and Benefit records that have been set up. What should the organization do to resolve the issue?

• A. Assign the Outcome Management permission set to the users.
• B. Assign the Advanced Program Management permission set to the users.
• C. Mark all the Program and Benefit records as Active.

正解：B

解説：
In Nonprofit Cloud, access to core functionality is governed by specific industry-aligned permission sets. If Case Managers are unable to see Program and Benefit records, it is typically a matter of missing object-level and feature-level permissions.
The Advanced Program Management permission set is a critical requirement for users who need to interact with the full program lifecycle.
Permissions included in Advanced Program Management:
* Object Access: It grants Read, Create, Edit, and Delete access (depending on the specific assignment) to the Program, Benefit, Benefit Type, and Benefit Schedule objects.
* Functional Access: It allows users to manage Program Enrollments and track Benefit Disbursements
.
* Visibility: Without this permission set (or a Permission Set Group containing it), the objects remain hidden from the user's navigation bar and global search, even if the records are marked as "Active." Step-by-Step Resolution:
* The Admin should navigate to Setup > Users.
* Select the Case Manager users.
* Click Permission Set Assignments > Edit Assignments.
* Add Advanced Program Management to the assigned list.
* Note: If the organization wants to limit Case Managers to "Read-Only," they would use this permission set in conjunction with a Muting Permission Set within a Permission Set Group.
Why other options are incorrect:
* Outcome Management (Option A): This grants access to impact tracking (Outcomes, Indicator Definitions) but does not provide the primary access to the Program and Benefit service delivery objects.
* Status Marking (Option C): While a record should be active for operational use, "Active" status on a record does not override Salesforce security. If the user doesn't have object-level permissions via a permission set, they cannot see the record regardless of its status.

質問 # 62
A human services nonprofit needs to track client goals and action items related to those goals. The nonprofit is unsure whether Program Management Module alone will meet its requirements. The nonprofit is considering whether to implement Nonprofit Cloud Case Management. What should the consultant discuss with the nonprofit?

• A. Case Management has a custom object for tracking goals.
• B. Program Management Module can track Case Plans and Action Items.
• C. Case Management requires Experience Cloud licenses.
• D. Program Management Module has custom objects for calendars and activities.

正解：A

解説：
For a consultant, it is vital to distinguish between the Program Management Module (PMM) and Nonprofit Cloud Case Management (NCCM). While they work together, they serve different functional depths.
* PMM (Standard Service Tracking): PMM is designed for "Service Delivery." It tracks which clients are in which programs and when they received a service (e.g., "John attended the Food Bank on Tuesday"). It is excellent for high-volume, low-touch interactions.
* NCCM (Deep Clinical/Social Work): Nonprofit Cloud Case Management is designed for "high- touch" human services. It introduces a much more granular data model. Specifically, it includes custom objects like Goals and Action Items that are part of a Case Plan. These allow a caseworker to define a specific journey for a client (e.g., Goal: "Secure Employment," Action Item: "Draft Resume").
The Core Distinction:
The consultant should explain that while PMM tracks what was delivered, Case Management provides the specialized objects needed to track the client's long-term progress through Goal tracking.
* Option A: PMM does not have specialized calendar objects; it uses standard Salesforce Activities.
* Option C: This is incorrect. Case Plans and Action Items are features of Case Management, not the standard PMM.
* Option D: Case Management does not require Experience Cloud, though they are often used together for participant portals.
By highlighting the Goal and Action Item objects, the consultant helps the nonprofit understand that Case Management is the correct choice for their "care-centric" requirements.

質問 # 63
A nonprofit receives a donation from a family foundation. What should the consultant recommend to ensure the donation is reflected on the family's household record?

• A. Use a GAU Allocation to credit the donation to the household.
• B. Use Account Soft Credits to credit the household.
• C. Add an additional Account lookup field on the Opportunity for the household.
• D. Add an Account lookup field on the Payment for the Opportunity for the household.

正解：B

解説：
In NPSP, we must distinguish between "Hard Credit" (legal ownership) and "Soft Credit" (influence
/relationship). When a family foundation (a Business Account) gives a donation, the Foundation gets the Hard Credit. However, the organization wants the Household Account (the family themselves) to receive credit for that gift in their "Total Giving" history.
The Solution: Account Soft Credits:
* Hard Credit: The Opportunity is created with the Family Foundation Account in the Account Name field. This is the legal donor.
* Soft Credit: To reflect this gift on the Family's Household, the consultant uses the Account Soft Credit feature.
* Relationship Tracking: A record is created in the Account Soft Credit related list on the Opportunity.
The "Account" is the Family's Household Account, and the "Role" is set to something like "Family Foundation."
* Rollups: NPSP's rollup engine will then pick up this soft credit. The family's Household record will now show this gift in fields like "Total Account Soft Credits" or "Total Gifts" (if the organization includes soft credits in their summary).
Why other options are incorrect:
* GAU Allocation (Option A): This tracks the fund or purpose of the money (e.g., "Building Fund"), not the donor or household credit.
* Lookup Fields (Options B & D): Adding custom lookup fields does not trigger NPSP's complex rollup logic. Only the standard Account Soft Credit object is recognized by the NPSP engine for aggregating influence-based giving to an account.

質問 # 64
A nonprofit organization is evaluating Nonprofit Cloud. Where can the organization see whether they qualify for nonprofit pricing and benefits from Salesforce?

• A. The Power of Us Program pages
• B. Trailhead Academy
• C. The Salesforce Commons Program pages

正解：A

解説：
For any organization beginning its journey with Salesforce, the first critical step in the Nonprofit Implementation Strategy is determining eligibility for discounted or donated technology. Salesforce consolidates these benefits under a specific initiative known as the Power of Us Program.1 The Power of Us Program pages serve as the primary portal for organizations to understand the specific legal and tax requirements needed to access the Nonprofit Cloud. According to Salesforce documentation, this program typically offers eligible nonprofits ten donated Enterprise Edition subscriptions and significant discounts on additional products, including the new Nonprofit Cloud (NPC) industry solution.2 Step-by-Step Qualification and Evaluation Process:
* Reviewing Eligibility: A consultant should direct the organization to the Power of Us portal to review the regional criteria. In the U.S., this usually requires 501(c)(3) status, while international organizations must provide equivalent tax-exempt documentation (such as an IRS Determination Letter or a Charity Commission record).3
* Trial and Application: Organizations are encouraged to start a 30-day Nonprofit Cloud trial.4 During this period, they log into the Power of Us portal using their Trailblazer ID to submit their formal application.5
* Verification: Salesforce's dedicated team reviews the uploaded documentation to verify that the organization's mission aligns with the program's philanthropic goals.
* License Provisioning: Once approved, the organization can view their specific "Power of Us" offers, including the "P10" (10 donated licenses) bundle.6 It is important to note that while Trailhead Academy offers learning paths and Salesforce Commons focuses on community-led open-source contributions, neither handles the financial or legal qualification for licensing.
The Power of Us Program is the official "front door" for the business and legal relationship between a nonprofit and Salesforce.

質問 # 65
A nonprofit organization wants to give specific users the ability to upload gift acknowledgement templates in Nonprofit Cloud for Fundraising. What should be assigned to the users?

• A. The OmniStudio User permission set
• B. The FundraisingAccess and DocGen Designer permission sets
• C. The FundraisingAccess and DocGen User permission sets

正解：B

解説：
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.

質問 # 66
A nonprofit organization uses Action Plans to guide its work on client Care Plans. The organization needs to add more tasks to an active Action Plan Template. What should the organization do to update the Action Plan Template in Nonprofit Cloud?

• A. Clone the Action Plan Template, select "Let users add items to action plans", and then publish the template.
• B. Clone the Action Plan Template, add tasks, and then publish the template.
• C. Deactivate the Action Plan Template, add tasks, and then publish the template.

正解：B

解説：
In Salesforce Nonprofit Cloud, Action Plan Templates are used to standardize repeatable processes, such as the steps required to onboard a new client or complete a grant application. To ensure data integrity and version control, Salesforce treats published Action Plan Templates as "locked" records.
When an organization needs to modify an "Active" or "Published" template-such as adding new tasks-the system does not allow direct editing of the existing record to prevent breaking current active Action Plans that were generated from that specific version. The standard procedure for a consultant is as follows:
* Clone the Template: The user must select the existing Action Plan Template and use the Clone action. This creates a new "Draft" version of the template with all the existing tasks copied over.
* Modify the Draft: In the new draft record, the consultant can add the additional tasks, define their priority, set the number of days for completion, and assign roles or specific users to those tasks.
* Publish: Once the modifications are complete, the new template must be Published. Publishing makes the template available for users to generate new Action Plans.
* Retire the Old Template: Although not strictly required to make the new tasks work, it is best practice for a consultant to deactivate or rename the old version to ensure staff only use the most up-to-date process moving forward.
Option B is incorrect because Salesforce does not typically allow you to "deactivate and edit" the task structure of a template that has already been published. Option A describes a specific setting that allows end- users to add extra tasks to an individual instance of a plan, but it does not address the requirement of updating the master template itself.

質問 # 67
A nonprofit has its organization-wide sharing settings for all objects set to Private and is using Program Management Module to track Service Deliveries. A subset of Service Delivery records should be visible to selected staff. How should a consultant meet this requirement?

• A. Create a criteria-based sharing rule.
• B. Create and assign a new profile.9
• C. Update default sharing to Public Read/Write.
• D. Update the assigned Permission Set.

正解：A

解説：
When an organization uses a Private sharing model (Organ11ization-Wide Defaults), users can only see records they own or records owned by their subordinates in the role hierarchy. To open up visibility to a
"subset" of records for a "selected" group of staff, the consultant must use a Sharing Rule.
Implementing the Solution:
* Criteria-Based Logic: Since only a subset of Service Deliveries (e.g., those related to "Mental Health" or a specific "Program") needs to be shared, the consultant should use a Criteria-Based Sharing Rule.
* Definition: The rule might state: "Share Service Delivery records where Program Name EQUALS ' Youth Outreach' with the 'Program Staff' Public Group."
* Access Level: The consultant defines the level of access (Read Only or Read/Write).
* Public Groups: The "selected staff" should be added to a Public Group. The sharing rule then targets this group.
Why other options are incorrect:
* Public Read/Write (Option B): This would expose all records to all users, violating the nonprofit's strict security requirements.
* Permission Sets / Profiles (Options C & D): These grant the functional ability to use the object (CRUD), but in a Private sharing model, they do not grant access to specific records owned by others.
Sharing rules are the primary tool for record-level visibility in Salesforce.

質問 # 68
A nonprofit wants to deploy Nonprofit Cloud Case Management into its production org. Which two prerequisites should be considered prior to installing Case Management? (Choose 2)

• A. Ensure Volunteers for Salesforce is properly configured
• B. Enable My Domain
• C. Install NPSP
• D. Ensure appropriate licenses are provisioned

正解：B、D

解説：
Nonprofit Cloud Case Management (NCCM) is a managed package that extends the capabilities of Salesforce for human services. Like many high-end Salesforce industry solutions, it has specific technical and legal prerequisites that must be met before the installation can succeed.
Prerequisite 1: Provisioned Licenses (A):
NCCM is not a free, open-source tool like NPSP. It is a paid product that requires specific Permission Set Licenses (PSLs) to be provisioned in the org. A consultant must verify that the organization has purchased the necessary licenses through their Salesforce Account Executive. Without these licenses appearing in the
"Company Information" section of Setup, the managed package will not function, and users will not be able to access the custom Case Management objects like Goals, Action Items, or Case Plans.
Prerequisite 2: My Domain (C):
NCCM relies heavily on modern Lightning components and OmniStudio features to power its interactive interfaces (such as the Case Plan Wizard). Salesforce requires My Domain to be enabled and deployed in any org that uses custom Lightning components. My Domain adds a unique prefix to the Salesforce URL (e.g.,
https://my-nonprofit.my.salesforce.com), which is necessary for the secure rendering of these components.
Why other options are incorrect:
* Volunteers for Salesforce (Option B): This is a completely separate application for managing volunteer shifts and is not required for Case Management to function.
* Install NPSP (Option D): While NCCM is often used alongside NPSP, the modern Nonprofit Cloud Case Management package can technically run on a standard Salesforce platform without NPSP, provided the necessary licenses are in place.

質問 # 69
A nonprofit organization wants to summarize donor activity related to Campaigns. Which object stores rollup fields that relate to the Campaigns?

• A. Donor Gift Summary
• B. Outreach Summary
• C. Gift Designation

正解：B

解説：
In the Nonprofit Cloud Fundraising data model (specifically API v59.0 and later), Salesforce introduced the Outreach Summary object to provide deep insights into the performance of marketing and solicitation efforts.
While the standard Campaign object in Salesforce tracks basic metrics like "Total Value Won Opportunities," the Outreach Summary in NPC is designed for the high-volume needs of nonprofits. It stores specialized rollup fields that provide a granular view of how a specific campaign or "Outreach Source Code" is performing.
Standard Rollup Fields in Outreach Summary:
* GiftCount: The total number of gifts received in response to the campaign.
* DonorCount: The number of unique donors who gave.
* TotalGiftAmount: The sum of all gift amounts.
* AverageGiftAmount: Automatically calculated to show donor value.
* TotalRecurringGiftAmount: Specifically tracks the success of sustaining giving appeals.
Implementation Logic:
* Calculation: These fields are not updated by standard Apex triggers in real-time. Instead, they are populated using the Data Processing Engine (DPE).
* Scheduling: A consultant schedules the "Outreach Summary" DPE job to run (e.g., nightly).
* Visibility: The results are written back to the Outreach Summary record, which is linked to the Campaign. This allows the fundraising team to see the true ROI of their outreach without the performance overhead of real-time calculations.
Why other options are incorrect:
* Donor Gift Summary (Option A): This object rolls up data at the Donor/Person Account level (e.g.,
"John Doe's lifetime giving"), not at the Campaign level.
* Gift Designation (Option B): This object tracks the "Fund" or "Purpose" (e.g., "General Fund"), and while it can have rollups, it doesn't represent the "Campaign" or "Outreach" performance.

質問 # 70
A consultant is helping a nonprofit organization set up Outcome Management. Which object should the consultant use to link Programs to Indicator Definitions?

• A. Indicator Result
• B. Indicator Assignment
• C. Indicator Performance Period

正解：B

解説：
In the Salesforce Nonprofit Cloud (NPC) architecture, the Outcome Management feature is designed to provide a standardized way for organizations to define, measure, and track their impact. To successfully implement this, a consultant must understand the hierarchical relationship between several key objects.
The process begins with the Indicator Definition, which acts as a "template" or "master metric." This object stores the logic of what is being measured (e.g., "Number of students who improved their reading level") without being tied to a specific program. To apply this metric to a specific context, Salesforce uses the Indicator Assignment object. This object serves as the essential link (a junction) between the Indicator Definition and the Program, Outcome, or Goal. By using Indicator Assignment, a consultant allows the organization to reuse the same definition across multiple different programs while keeping the tracking and reporting for each program distinct.
Step-by-Step Configuration Flow:
* Create Indicator Definition: Define the global metric, specifying the data type and how the progress will be calculated.
* Create the Indicator Assignment: This is the core step. Here, the consultant links the specific Program record to the Indicator Definition. This creates the specific context for measurement.
* Establish Indicator Performance Periods: Once the assignment is made, the consultant must define the timeframes (e.g., "Q1 2025" or "Annual 2025") during which the program will be evaluated.
* Record Indicator Results: Finally, as the program progresses, actual data points are entered into the Indicator Result object, which rolls up to the Performance Period and is contextualized by the Assignment.
Without the Indicator Assignment, the system would have no way of knowing which programs are responsible for which metrics. This structure ensures that a nonprofit can scale its impact measurement across various departments while maintaining a single, clean library of Indicator Definitions.

質問 # 71
A consultant began an implementation project with a nonprofit that is new to Salesforce. The nonprofit's leadership is hesitant to spend time at the beginning of the project on change management. What are three reasons the consultant can share to emphasize the value and importance of governance? (Choose 3)

• A. Technical interoperability
• B. Compliance
• C. Delivery Speed
• D. Security
• E. Cost savings

正解：B、D、E

解説：
Governance in a Salesforce project is the framework of rules and processes that ensure the system remains healthy, secure, and aligned with the mission. While leadership may view it as "bureaucracy," a consu1ltant must frame it as risk2 management.
Three Core Pillars of Governance Value:
* Security (E): Without governance, users might be granted broad permissions "to move fast," leading to data breaches or the exposure of sensitive donor/client information. Governance ensures a "Principle of Least Privilege" is maintained through a structured review of Permission Sets and Sharing Rules.
* Compliance (C): Nonprofits are subject to strict regulations (e.g., GDPR, HIPAA, or IRS audit requirements). Governance provides the documentation and audit trail needed to prove that the organization is handling data according to legal standards.
* Cost Savings (B): This is often the most persuasive argument for leadership. Poor governance leads to
"Technical Debt"-duplicate apps, messy data, and conflicting automations that require expensive consultant hours to fix later. By establishing a Change Control Board (CCB), the organization avoids wasting money on redundant tools or poorly designed features.
While Delivery Speed (D) and Interoperability (A) are benefits of a well-run project, they are often the result of good governance rather than the primary strategic reasons to implement it. Security, Compliance, and Cost Savings are the fundamental justifications for a nonprofit's long-term sustainability on the platform.

質問 # 72
A nonprofit organization wants to implement donor levels. The organization wants to see at-a-glance identifiers that show how often a donor donates and how much they have donated. What should the organization do in Nonprofit Cloud?

• A. Configure Recency, Frequency, and Monetary Value (RFM) Scoring. Add the scoring fields to a Related Record Detail Display for the Donor Gift Summary object.
• B. Configure a Record Alert FlexCard with the values for donor levels. Add the Record Alert component to the Person Account layouts.
• C. Create custom donor level fields on the Contact Profile object. Add the scoring fields to a Related Record Detail Display for the Contact Profile object.

正解：A

解説：
To implement "donor levels" based on behavior (frequency and amount), the modern Nonprofit Cloud utilizes the RFM Scoring framework. RFM stands for Recency (how recently they gave), Frequency (how often they give), and Monetary Value (how much they give). This is the standard industry method for segmenting donors into tiers like "Champion," "Loyal," or "At Risk." Step-by-Step Implementation for the Consultant:
* Configure RFM Scores: In the Setup menu, the consultant goes to Recency, Frequency, and Monetary Value (RFM) Score. Here, you define the "Source" objects (typically the Donor Gift Summary or Gift Transactions) and set the ranges. For example, you might define "Frequency" as: 1-
2 gifts = Score 1; 3-5 gifts = Score 2; 5+ gifts = Score 3.
* Calculate Scores: The consultant then schedules the RFM Data Processing Job. This job runs in the background, evaluates every donor's history, and assigns numerical scores to each category.
* The Composite Score: The system can combine these into a Composite RFM Score (e.g., "3-3-3" for the best donors).
* Displaying the Data: To make these scores "at-a-glance" identifiers, the consultant adds these fields to the Donor Gift Summary object. Using the Related Record Detail Display or a standard Record Detail component on the Person Account page, the staff can immediately see the donor's scores alongside their contact info.
This approach provides a dynamic, data-driven way to identify donor levels without manual updates. Option B is incorrect because Record Alerts are for transient warnings (e.g., "Do not call") rather than persistent behavioral metrics. Option C is incorrect because while the Contact Profile stores donor attributes, the specific engine for calculating and displaying frequency/monetary "levels" is designed to work with the Donor Gift Summary object within the NPC Fundraising architecture.

質問 # 73
What is a consideration a consultant should be aware of when implementing Person Accounts in Nonprofit Cloud?

• A. The Is Person Account field can be used to exclude Person Accounts from Automation Rules and Validation Rules on the Account object.
• B. All standard and custom Contact fields will have an API name that begins with Person when being referenced through a Person Account.
• C. All AppExchange Packages have been confirmed to be compatible with Person Accounts.

正解：A

解説：
When implementing the new Nonprofit Cloud (NPC), the shift toward Person Accounts as the default model for individual constituents is a significant change from the traditional Nonprofit Success Pack (NPSP) model. A consultant must understand how this architecture impacts system logic and data integrity.
The Is Person Account (API name: IsPersonAccount) field is a standard Boolean field on the Account object that automatically evaluates to true when an account record is a Person Account. This field is critical for consultants for several reasons:
* Filtering Automation: Because Person Accounts live on the Account object alongside Business Accounts (like Foundation or Corporate partners), a single Flow or Apex Trigger on the Account object will fire for both. To ensure that "Company-specific" logic doesn't execute for an individual donor, a consultant uses the IsPersonAccount field as a decision element or entry criteria in Salesforce Flows.
* Validation Rules: Validation rules intended for businesses (e.g., "Tax ID is required for all Corporate Accounts") would fail for individual donors if not properly scoped. By adding AND(NOT (IsPersonAccount), ...) to the formula, the consultant ensures the rule only applies to Business Accounts.
* Reporting and List Views: This field is the primary way to segment data. While Person Accounts mimic Contacts, they are technically Accounts, so this flag is the only way to quickly differentiate individuals from organizations in global queries.
Regarding the other options: Option A is incorrect because while many packages support Person Accounts, it is not a universal guarantee, and a consultant must always verify compatibility during the design phase.
Option B is a common misconception; while some fields are prefixed in certain API contexts, standard contact fields on the Person Account record page often retain their standard labels, and custom fields created on the Contact object specifically for Person Accounts are suffixed with __pc, not prefixed with "Person" for the API name.

質問 # 74
A nonprofit enters donation data both into Salesforce and an external accounting system to reconcile financial support. This process is time-consuming. What should the consultant recommend to reduce manual data entry and improve efficiency?

• A. Advanced Mapping
• B. NPSP Data Importer Templates
• C. Data Import Wizard
• D. Accounting Subledger

正解：D

解説：
The primary pain point described is the "double entry" of financial data between a CRM (Salesforce) and an external General Ledger (GL) or accounting system. To resolve this, Salesforce developed Accounting Subledger.
Accounting Subledger acts as the translator between fundraising language and accounting language. It automatically generates Ledger Entry records based on donation data (Opportunities and Payments) in Salesforce. These ledger entries are formatted to align with standard accounting principles (Debits and Credits) and can be easily exported in a format that the external accounting system can ingest.
Step-by-Step Efficiency Gains:
* Automation: Instead of a staff member manually typing data into a second system, Accounting Subledger identifies "Closed/Won" gifts and creates the corresponding accounting records in the background.
* Accuracy: It eliminates human error associated with manual entry, ensuring that the total "Revenue" in Salesforce matches the "Income" in the accounting software.
* Transparency: Because the ledger entries are linked directly to the original Opportunity in Salesforce, the finance team and the development team can reconcile records using a shared "source of truth."
* Audit Trail: It maintains a permanent record of when data was "finalized" for accounting purposes, which is essential for annual audits.
By implementing Accounting Subledger, the consultant moves the nonprofit from a manual reconciliation process to an automated "subledger" model, significantly reducing administrative overhead and allowing staff to focus on mission-driven tasks rather than data entry.

質問 # 75
The development director at a nonprofit needs to track grant lifecycles using NPSP, including assigning actions to staff members, tracking applications, reporting deadlines, and summarizing the total amount awarded with payments. How should the consultant model payments, applications, reporting deadlines, and actions in NPSP for the grant seeking institution?

• A. Payments = Recurring Donations with Opportunities; Applications = Deliverables; Reporting deadlines
  = Deliverables; Actions = Activities
• B. Payments = Opportunities with Payments; Applications = Activities; Reporting deadlines = Activities
• C. Payments = Opportunities with Payments; Applications = Deliverables; Reporting deadlines = Deliverables; Actions = Activities

正解：C

解説：
Tracking the "Grant Seeking" process in NPSP requires a specific mapping of business requirements to the NPSP data model. Unlike "outbound" grantmaking, "inbound" grant seeking uses the Opportunity object as the primary record for each grant proposal.
Mapping the Lifecycle:
* Applications & Reporting Deadlines (Deliverables): In NPSP, the Deliverable object is specifically designed to track milestones associated with a grant Opportunity. An "Application Submission" is a deliverable (the first milestone), and "Mid-Year Report" or "Final Report" are subsequent deliverables with specific due dates. This allows the development director to see a calendar of all upcoming grant requirements.
* Payments (Opportunities with Payments): While the Opportunity tracks the total amount awarded, the Payment object in NPSP tracks the actual cash coming in. Since grants are often paid in multiple installments (multi-year grants), using the related Payments list is the standard way to reconcile the total award against what has actually been deposited in the bank.
* Actions (Activities): Standard Salesforce Activities (Tasks and Events) are used to track the day-to- day engagement steps, such as "Draft Narrative," "Call Program Officer," or "Review Budget." These are the "internal" actions assigned to staff members.
Why other options are incorrect:
* Option A: Recurring Donations are for open-ended, sustaining gifts (like monthly donors), not for specific fixed-amount grant awards with a set payment schedule.
* Option C: Using Activities for reporting deadlines is a poor practice because activities are easily deleted or closed without the formal tracking and field-level detail (like "Grantee Requirements") that the Deliverable object provides.

質問 # 76
The admin at a nonprofit is implementing Salesforce Shield in its org to enable field platform encryption.
What are three NPSP considerations when implementing Shield Platform Encryption? (Choose 3)

• A. The NPSP Data Import object supports encryption of all fields in the import batch.
• B. The NPSP MergeContacts list button on Contact list views will fail if the Contact Name is encrypted.
• C. If the Role Name field is encrypted on the NPSP Partial Soft Credit object, the nightly Soft Credit rollups fail.
• D. NPSP Data Import is unable to perform Custom Unique Id matching on Accounts and Contacts with an encrypted field.
• E. Fields on the NPSP Address object can be encrypted, but encryption is unavailable for address fields on the Account and Contact object.

正解：B、C、D

解説：
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.

質問 # 77
A consultant is assisting a nonprofit in its data integration and mapping between two systems. The consultant is unsure when a particular field was added to NPSP. Where can the consultant find the NPSP version number for the field in question?

• A. Custom field definition detail
• B. NPSP package details
• C. NPSP Data Dictionary
• D. Schema Builder

正解：C

解説：
When performing complex integrations or troubleshooting why a field is missing in an older sandbox, a consultant needs a reliable reference for the NPSP metadata.
The NPSP Data Dictionary:
* Historical Reference: The NPSP Data Dictionary is an official Salesforce resource (usually provided as a spreadsheet or a dedicated help article). It lists every object and field included in the managed package.
* Version Tracking: Crucially, the Data Dictionary includes a column for "Introduced In" or " Package Version." This tells the consultant exactly which release of NPSP (e.g., 3.154) first included that specific field.
* Object Mapping: It also provides the API names, descriptions, and help text for all NPSP-specific fields, making it the primary "source of truth" for mapping projects.
Why other options are incorrect:
* Custom Field Definition (Option C): In the Salesforce Setup menu, the field detail page will show the
"Installed Package" (Nonprofit Success Pack), but it does not tell you which version of that package introduced the field.
* NPSP Package Details (Option A): This shows you the current version installed in the org, but not the historical release version for individual fields.
* Schema Builder (Option D): This is a visual tool for seeing relationships between objects; it contains no versioning or historical metadata.

質問 # 78
A volunteer with a nonprofit works at Universal Containers. The volunteer is recorded in Salesforce as part of the Household's account record, but Universal Containers needs to be entered into the Salesforce system. How should a consultant track the volunteer's relationship with Universal Containers?

• A. Create a Universal Containers Organization Account and create a Relationship record between the volunteer and Universal Containers.
• B. Create a Universal Containers Organization Account a3nd create an Affiliation record between the volunteer and Universal Containers.
• C. Create a Lead for the volunteer at Universal Containers and create an Affiliation record between the volunteer Lead and Universal Containers.1
• D. Create a Lead for the volunteer at Universal Containers and create a Relationship record between the volunteer Lead and the volunteer Contact.2

正解：B

解説：
In NPSP, there is a clear distinction between how we track "people to people" and "people to organizations."
* People to Organizations (Affiliations): When a Contact (the volunteer) has a professional or community connection to an organization (Universal Containers), the Affiliation object is used. An Affiliation is a junction record that links a Contact record to an Account record with an 'Organization
' record type.
* People to People (Relationships): The Relationship object is used exclusively for person-to-person ties (e.g., "Spouse," "Coworker," or "Father"). You do not use the Relationship object to link a person to a business.
The Solution:
To track this volunteer's employment or connection to Universal Containers:
* Step 1: Create an Account record for "Universal Containers" and ensure its record type is
"Organization."
* Step 2: Create an Affiliation record.
* Step 3: On the Affiliation record, link the volunteer's Contact record to the Universal Containers Account record.
* Step 4: Specify the Role (e.g., Employee) and mark it as the Primary Affiliation if this is their main employer.
Using Leads (Options A & B) is incorrect because the volunteer is already an established "Contact" in the system; creating a Lead would create a duplicate record and fragment the data history.

質問 # 79
Caseworkers at a nonprofit organization want to see a single chronological view of all past interactions, cases, referrals, and care plans for a participant. Which Nonprofit Cloud feature should the organization use?

• A. Timeline
• B. Contact Profile
• C. Events and Milestones

正解：A

解説：
For caseworkers managing complex social services, the ability to see a participant's "story" in chronological order is vital for providing informed care. The Timeline component in Nonprofit Cloud is the specific feature designed to solve this need.
Key Features for Caseworkers:
* Chronological Aggregation: The Timeline pulls records from various objects-Case Proceedings, Referrals, Care Plans, Tasks, and Benefit Disbursements-and plots them on a single horizontal or vertical axis based on their date.
* Filtering and Search: Caseworkers can filter the view to show only specific types of interactions (e.g.,
"Show me only medical referrals from the last 6 months").
* Actionability: From the timeline, a caseworker can hover over an event to see summary details or click directly into the record to view full notes.
* Configuration: A consultant configures the Timeline via the Timeline Settings in Setup. You can define "Timeline Configurations" for different user personas; for example, a caseworker might see
"Care Plans," while a fundraiser might see "Gift History" on their version of the timeline for the same Person Account.
Why other options are incorrect:
* Contact Profile (Option A): This is a summary view of person-centric data (like age, preferred language, or wealth indicators) but is a static layout, not a chronological view of events.
* Events and Milestones (Option B): This feature is used to track "Life Events" (like birth, marriage, or graduation). While these can be surfaced on the Timeline, the feature itself is a component for life-stage tracking, not a comprehensive chronological record of all cases and interactions.

質問 # 80
A large nonprofit is a social enterprise that functions like a for-profit corporation. The funding the nonprofit tracks in Salesforce only comes from corporations. The nonprofit needs to manage Leads and track its Opportunity pipeline. Which account model should the consultant recommend?

• A. One-to-One Account Model in NPSP
• B. Individual Account Model in NPSP
• C. Person Account Model without NPSP
• D. Standard Account Model without NPSP

正解：D

解説：
This is a "Solution Design" question where the organization's business model dictates the architecture. While NPSP is the default for most nonprofits, it is specifically designed for Individual and Household giving.
If an organization functions like a B2B (Business-to-Business) corporation and only receives funding from other corporations:
* Simplification: They do not need the "Household" or "One-to-One" complexity of NPSP. These models are designed to "wrap" a contact in an account to support individual donations.
* Standard Sales Cloud: The Standard Account Model (where a Contact belongs directly to an Account/Corporation) is exactly how Salesforce was originally designed to work for corporate sales.
* Lead/Pipeline Management: By using Standard Salesforce (without NPSP), they get the cleanest experience for Lead conversion and Opportunity management, as all the NPSP-specific automation (like Household naming) would be unnecessary overhead for a purely corporate funding model.
Option A (Person Accounts) is also a specialty model, but it is intended for B2C (Business-to-Consumer) interactions. For a social enterprise dealing with corporations, Standard Accounts provide the best "out-of- the-box" fit.

質問 # 81
In the NPSP Data Import Template, the Account fields should contain which two types of information?
Choose 2 answers

• A. Business-related data
• B. Contact's employer-related data
• C. Household-related data
• D. Contact's address-related data

正解：A、C

解説：
The NPSP Data Import Template is a "flat file" structure designed to populate multiple objects in the NPSP data model simultaneously. Because NPSP uses a "Household-centric" model but also supports corporate and foundation giving, the Account fields in the template serve a dual purpose depending on the record being imported.
* Business-related data (A): If the nonprofit is importing donations from a corporation, foundation, or local business, the "Account" fields in the template (such as Account Name, Account Phone, etc.) are used to create or match an Organization Account. This allows the consultant to track the entity's history and give them "Hard Credit" for their donations.
* Household-related data (B): If the nonprofit is importing individual donors, the Account fields are used to define the Household Account. For example, if the template specifies "The Smith Household" in an Account field, NPSP logic will use that data to name the household record it creates for the associated contacts.
* Address Logic (C): While addresses are part of an account, in the NPSP Data Importer, address data is typically handled by specific Address fields that NPSP then intelligently routes to the Household or the Contact record.
* Employer Logic (D): Tracking an employer is usually handled via Affiliations. While the employer is an Account, the template has specific "Home" vs. "Work" logic to handle these relationships separately from the primary account being created.
In summary, the Account columns in the CSV template are the landing spot for any data related to the
"Institutional" or "Household" entity that owns the donation or contains the contact.

質問 # 82
A nonprofit offers courses that grant teachers credit toward maintaining their teaching certification. Teachers can enroll in an annual cohort to complete the course modules together. The nonprofit needs to track the courses each teacher completes and the credits awarded to them. Which solution should a consultant recommend?

• A. Engagement Plans
• B. Service Cloud
• C. Program Management Module
• D. Self-Service Portal

正解：C

解説：
The Program Management Module (PMM) is the standard industry solution for tracking the delivery of mission-centric services. In this scenario, the "Courses" are the services, and the "Teachers" are the participants.
Mapping the Requirement to PMM Objects:
* The Course (Program/Service): Each certification course is modeled as a Program. Individual modules or sessions within that course are modeled as Services.
* Annual Cohorts (Program Cohort): PMM has a standard Program Cohort object. This is perfectly suited for tracking a group of teachers who start and move through the certification modules together on an annual basis.
* Tracking Completion (Service Delivery): When a teacher completes a module, a Service Delivery record is created. The consultant can add a custom field to the Service Delivery object to track the
"Credits Awarded" for that specific session.
* Teacher Enrollment (Program Engagement): The teacher's overall progress toward their certification is tracked via the Program Engagement record, which rolls up the total number of credits earned from the related Service Deliveries.
While a Self-Service Portal (Option D) might be the interface the teachers use, and Service Cloud (Option B) provides the base infrastructure, the Program Management Module provides the specific data model (Programs, Cohorts, and Deliveries) required to track credits and educational progress out-of-the-box.

質問 # 83
......

あなたを合格させるNP-Con-102お手軽に試験合格リアルNP-Con-102練習問題集で更新されたのは2026年03月03日：https://www.goshiken.com/Salesforce/NP-Con-102-mondaishu.html

2026年最新の実際に出ると確認されたSalesforce NP-Con-102無料試験問題：https://drive.google.com/open?id=1-f78nedw2B_HsOh_LEKoxI27AZ97gokt