A (Enable Chatter); C (Migrate Users to Lightning Experience); E (Customer Community Plus Licenses).
This is the lowest-customization answer that still satisfies the business, security, and lifecycle requirements.
The Core Concept Explained: Experience Cloud design is driven by persona, authentication, scale, and sharing. The wrong template or license can create unnecessary cost, weak security, or excessive customization.
Step-by-Step Technical Analysis: Begin with the external persona, authentication requirement, and transaction volume. Select the Experience Cloud license or template that matches that access pattern, then configure sharing sets, external OWD, site visibility, and page access. Finish by testing the experience as anonymous, authenticated, and internal users. Enable Chatter, migrate staff to Lightning Experience, and procure Customer Community Plus licenses for grant-seeker portal users.
Why the Incorrect Options Are Wrong: B does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario. D adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement.

A (Employee Workspace); B (Employee Concierge); C (HR Service Center). This maps the scenario to the Salesforce-native capability that owns the requirement.
The Core Concept Explained: Experience Cloud design is driven by persona, authentication, scale, and sharing. The wrong template or license can create unnecessary cost, weak security, or excessive customization.
Step-by-Step Technical Analysis: Begin with the external persona, authentication requirement, and transaction volume. Select the Experience Cloud license or template that matches that access pattern, then configure sharing sets, external OWD, site visibility, and page access. Finish by testing the experience as anonymous, authenticated, and internal users. Install and configure the employee-facing packages that deliver the workspace, concierge intake, and HR service capabilities. For exam preparation, validate the answer by tracing the record lifecycle, the user persona, and the automation owner from intake through reporting.
Why the Incorrect Options Are Wrong: D uses the wrong packaged object or module boundary for this scenario. E uses the wrong packaged object or module boundary for this scenario.

Once published, an Action Plan template cannot be changed. This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
The Core Concept Explained: Action Plans standardize repeatable work. They package tasks, dependencies, due dates, and document checklist requirements so staff do not rely on memory or one-off manual steps.
Step-by-Step Technical Analysis: Start by defining the target object that owns the operational work. Build or select the Action Plan Template, add the required tasks or Document Checklist Items, publish the template, and then automate or guide its association to the live record. Test that owners, due dates, dependencies, and applicant-facing upload prompts behave correctly. Once a template is published, it cannot be edited directly.
Why the Incorrect Options Are Wrong: A may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. B may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

Create a custom Approvals dashboard using standard Salesforce Reports and Dashboards and add this to a custom Home Page assigned.. This selection keeps the implementation declarative and within the intended Public Sector operating model.
The Core Concept Explained: Public-sector analytics should reuse packaged datasets and dashboards where possible. Prebuilt assets reduce implementation effort and give agencies consistent metrics across licensing, inspection, case, emergency, and grant operations.
Step-by-Step Technical Analysis: Confirm the operational records and datasets needed for the metric. Use the prebuilt Public Sector or CRM Analytics app when it already models the domain, assign the required admin
/user permissions, and validate that prerequisite records exist. Then review dashboards against real licensing, inspection, case, or emergency-response data. Create a custom approvals dashboard with standard Salesforce Reports and Dashboards and add it to a custom Home Page assigned to the Approver profile.
Why the Incorrect Options Are Wrong: A adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement. B adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement. C adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement.

A (Employee Experience Community Access); B (Employee Productivity Plus Access); E (Employee Experience for Public Sector). This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.
The Core Concept Explained: Experience Cloud design is driven by persona, authentication, scale, and sharing. The wrong template or license can create unnecessary cost, weak security, or excessive customization.
Step-by-Step Technical Analysis: Begin with the external persona, authentication requirement, and transaction volume. Select the Experience Cloud license or template that matches that access pattern, then configure sharing sets, external OWD, site visibility, and page access. Finish by testing the experience as anonymous, authenticated, and internal users. Assign Employee Experience Community Access, Employee Productivity Plus Access, and Employee Experience for Public Sector.
Why the Incorrect Options Are Wrong: C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. D may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.