Partner Central is specifically designed for partner relationship management and channel-sales workflows. Salesforce documents Partner Central as a responsive Experience Cloud template intended to help organizations recruit, build, and grow partner networks while supporting channel sales and marketing activities. Its standard capabilities include lead distribution, deal registration, partner recruitment and onboarding, marketing campaigns, enablement, pipeline management, and related reporting.

Those capabilities correspond directly to the scenario. The external associates function as channel partners, and the agency needs a collaborative portal for onboarding those partners and managing sales-style workflows around licensing activities.

Customer Account Portal is designed primarily for customers managing their own account information and accessing customer-oriented services. Help Center is focused on support and self-service knowledge experiences rather than partner sales processes. Aloha is a legacy template and is no longer the preferred architecture for a new implementation.

Salesforce also requires appropriate partner licensing for Partner Central functionality and explicitly associates the template with Partner Community and related partner-oriented licenses.

Study Guide Reference: Public Sector Solution Product Configuration – Experience Cloud templates, Partner Central, partner onboarding, lead distribution, deal registration, and channel collaboration.

================

Volunteer Management provides capabilities for coordinating volunteer demand, registrations, assignments, projects, shifts, and volunteer activity. Salesforce's official Work.com documentation describes Volunteer Management as supporting volunteer projects at scale and explicitly states that volunteers can sign up for volunteer projects through a community experience and update the time spent on volunteer activities . This directly validates option C.

The package also maintains volunteer capacity and registration information associated with volunteer work. Volunteer-management records track shift requirements and registered resources so that changes in a shift—including cancellation—can be reflected in the volunteer counts. This supports option A's requirement to keep registered-volunteer and volunteer-demand figures synchronized.

Salesforce's volunteer data architecture similarly includes volunteer shifts, volunteer hours, volunteer counts, and "Volunteers Still Needed" information, demonstrating that capacity and participation tracking are integral functions of volunteer management.

Automatic reimbursement claiming is not a standard Volunteer Management capability described for this package. Likewise, a volunteer chatbot is not one of the core Volunteer Management features represented by the question.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Emergency Program Management; Volunteer Management; volunteer projects, shifts, registrations, capacity, and volunteer-hour reporting.

================

Salesforce directly documents Action Plans on Accounts as the mechanism for standardizing grantmaking due-diligence processes. An Action Plan Template acts as a reusable blueprint that defines the activities reviewers must complete consistently for each grantseeking organization.

Salesforce's Grants Management documentation explicitly states that organizations can use Action Plans on Accounts to define due diligence steps, related tasks, and documents to collect . Tasks can represent actions such as requesting tax documentation, verifying organizational eligibility, or completing financial reviews. Document Checklist Items identify supporting documents that must be obtained and reviewed.

This architecture directly addresses the problem in the scenario: reviewers currently follow different processes. A published Action Plan Template converts an informal procedure into a repeatable Salesforce-controlled workflow, improving consistency, traceability, accountability, and reviewer productivity.

A Screen Flow or OmniScript could technically guide a user through steps, but both would duplicate functionality already supplied by Action Plans. Merely supplying procedural documentation also provides no technical enforcement, assignment, due-date management, or document checklist tracking.

Therefore, Action Plans represent the product-native and lowest-customization implementation.

Study Guide Reference: Public Sector Solution Product Configuration – Grants Management; Due Diligence; Action Plans; Action Plan Templates; Tasks; Document Checklist Items.

================

The Public Sector inspection experience provides purpose-built Lightning components that support inspectors while they execute onsite Visits. The three applicable components are Inspection Details, Inspection Action, and Inspection Tab Container .

Inspection Details presents the contextual information an inspector needs for the Visit, such as the inspection subject, location, relevant authorization information, and related inspection data. Inspection Action exposes inspection-specific actions that allow inspectors to execute the operational steps associated with the Visit. Inspection Tab Container organizes the various inspection functions into a usable tabbed workspace, allowing the inspector to move efficiently between inspection information, assessment activities, violations, signatures, and associated tasks.

These components belong to the execution layer of Public Sector inspection management and are intended to reduce navigation between unrelated Salesforce records while an inspector is conducting field work.

Inspection Dynamic Dashboards is not one of the standard built-in inspection execution components represented by this configuration. Inspection Calendar can be useful for scheduling and viewing inspection appointments, but it does not constitute one of the three embedded Visit-execution components asked for here.

The Set 3 question itself also identifies A, D, and E as the selected combination.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Inspection Management; Visits; Inspection Details; Inspection Action; Inspection Tab Container; inspector workspace.

================

The lifecycle begins with Plan , where the grantmaker defines the funding program, objectives, eligibility, funding availability, and program structure. The organization then Engages prospective grantseekers by publishing and communicating the funding opportunity. Eligible grantseekers subsequently Apply , after which the grantmaker conducts the formal Review process and determines which applications receive an Award . The award then enters the Manage stage, covering requirements, disbursements, progress reporting, compliance, and performance monitoring, followed by formal Close Out .

This sequence aligns with Salesforce's Grants Management architecture. Salesforce Trailhead describes the lifecycle operationally: the grantmaker creates and publishes Funding Programs, a grantseeker applies by creating a Funding Request, verification and reviews occur, requirements are processed, and successful applications proceed to disbursement and continuing management.

Salesforce's Grantmaking material likewise separates application decisions from the subsequent Funding Award, then uses the award as the central record for post-award disbursements, requirements, expenditure tracking, progress reporting, and eventual completion.

Options C and D put lifecycle stages in an illogical order. Option A is structurally invalid because it places Apply before planning and repeats Apply.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Grants Management lifecycle; Funding Programs; applications; reviews; awards; post-award management; closeout.

================

VS Code and Salesforce DX provide the supported development and deployment tooling for OmniStudio Lightning Web Components associated with DataPacks. Salesforce explicitly states that administrators and developers use Visual Studio Code with Salesforce DX and the Salesforce CLI to manage, develop, and deploy OmniStudio Lightning Web Components between development, sandbox, and production organizations.

This distinction matters because an OmniStudio DataPack can include configuration metadata as well as generated or supporting Lightning Web Component artifacts. When LWC deployment is required, a Salesforce DX project provides the metadata structure, authentication, source management, and deployment commands needed to transfer the components reliably between environments.

VS Code by itself is only the development environment; it does not constitute the complete Salesforce deployment mechanism. Salesforce DX provides the Salesforce-specific project model and deployment capabilities, making option B incomplete. Standard Change Sets aren't the recommended deployment mechanism for these OmniStudio LWC assets, while the ANT Migration Tool represents an older Metadata API deployment approach and isn't the prescribed toolchain for this requirement.

Therefore, the complete supported combination identified by Salesforce is Visual Studio Code together with Salesforce DX.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – OmniStudio deployment, DataPacks, Lightning Web Components, VS Code, Salesforce DX/SF CLI.

================

A Sharing Set is the appropriate Experience Cloud sharing mechanism when external users need access to records associated with their account or contact but don't own those records themselves.

Salesforce states that a sharing set grants Experience Cloud site users access to records by mapping the user's Account or Contact relationship to a corresponding Account or Contact lookup on the target record. Salesforce gives Cases as a specific example: administrators can grant site users access to all Cases associated with the Account identified on the user's Contact record.

That matches this scenario precisely. The internal support team creates the Case, so the external constituent isn't necessarily its owner. A Sharing Set can expose the appropriate Cases to the authenticated external user based on the associated Account or Contact while keeping unrelated constituent Cases inaccessible.

Changing Case OWD to Public Read/Write would be excessively permissive and violate least-privilege principles. A permission set provides object- and field-level authorization but doesn't by itself grant access to specific records restricted by the Salesforce sharing model. Share Groups solve the opposite direction of high-volume sharing: they primarily give internal users access to records owned by high-volume external site users.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud sharing; Sharing Sets; Cases; Account/Contact access mappings; external OWD and least-privilege record access.

Action Plans are intended for exactly this type of repeatable licensing workflow. Salesforce identifies Business License Application as a supported target object for Action Plan Templates, allowing the agency to define standardized reviewer activities that are instantiated whenever the plan is applied to a specific application.

Salesforce also supports Document Checklist Items within action-plan-based document-processing workflows. Document checklist items identify the specific documents that applicants or staff must supply, such as a driver's license. When a document checklist item is included in a published Action Plan Template, it can be propagated to Action Plans created from that template, creating consistent document requirements.

Therefore, option A accurately combines the correct target record—Business License Application—with document tracking for the required identity-document image.

The other statements are overly restrictive. Salesforce supports Action Plan task dependencies in applicable Public Sector implementations, including prerequisite and successor task relationships, so dependent execution can be modeled declaratively. Action Plans also use ordinary task records, and Salesforce supports ad hoc task creation when configured, so staff can supplement standardized plans when case-specific work is necessary.

This gives the agency both governance and flexibility: required standard tasks come from the template, while exceptional application-specific work can still be accommodated.

Study Guide Reference: Public Sector Solution Product Configuration – Action Plans; Action Plan Templates; Business License Applications; Tasks; task dependencies; Document Checklist Items.

================

Volunteer Management for Community is the permission-set license intended for external community users who participate in the Volunteer Management experience. The constituent in this scenario isn't an internal emergency-management administrator; the person is an external volunteer who must access a digital experience and sign up for volunteer projects.

Public Sector's user-access architecture separates feature entitlement from the base Experience Cloud user license. Permission-set licenses extend the capabilities of the underlying Salesforce user license and must correspond to the Public Sector product functionality the user needs. Salesforce's Public Sector permissions documentation confirms this general architecture: users require the appropriate Public Sector permission sets and associated permission-set licenses for the features they consume.

For this specific legacy Volunteer Management implementation, the relevant external entitlement is Volunteer Management for Community . This enables the community-side functionality necessary for volunteers to interact with volunteer projects rather than granting internal emergency-response administration.

Option A relates to broader Community Response capabilities rather than the specific volunteer-user entitlement. Option B is generic Public Sector community access and doesn't, by itself, grant Volunteer Management functionality. Option D is aligned with internal Emergency Response functionality rather than the community volunteer persona.

Study Guide Reference: Public Sector Solution Product Configuration – Volunteer Management; Community Response; Experience Cloud user access; Permission Set Licenses.

================

A high-volume grant window creates a capacity and transaction-load problem , so the implementation must reduce synchronous processing, optimize content delivery, and validate the architecture at anticipated peak volume.

First, computationally expensive operations should be moved away from the synchronous user transaction when possible. Salesforce's high-volume Experience Cloud architecture uses asynchronous processing and micro-batching to prevent heavy record creation and processing from blocking interactive requests during traffic spikes.

Second, Salesforce specifically identifies Content Delivery Network (CDN), caching, Lightning Web Runtime, Apex caching, and progressive rendering among its Experience Cloud performance and scale optimization tools. CDN and caching reduce repeated server processing and improve the delivery of static or reusable resources during high traffic.

Third, the agency must test the expected peak workload rather than assuming functional UAT proves scalability. Salesforce identifies Scale Testing as an optimization tool for heavy transaction loads and customizations.

UAT remains necessary for functional acceptance but does not establish capacity under concurrent traffic. IP restrictions would deliberately restrict legitimate applicants rather than scale the application to serve the expected demand.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Experience Cloud scale; asynchronous processing; CDN; caching; high-volume transactions; performance and load testing.