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.

Disable the Grant Access Using Hierarchies setting on the Case object. 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. Disable Grant Access Using Hierarchies on the Case object where supported for the Employee Experience security design.
Why the Incorrect Options Are Wrong: A points to a disablement approach that either is not supported for the tested feature or would remove a capability the scenario depends on. B does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario. D does not meet the implementation-quality bar for security, scale, auditability, or maintainability in this scenario.

Salesforce OmniStudio, Flows, Employee and Public Sector Data Models, and Employee Community. This is the packaged route that keeps the process supportable, auditable, and aligned to the data model.
The Core Concept Explained: OmniStudio separates guided interaction, data mapping, orchestration, and UI presentation. That separation is critical for high-volume public-sector intake because each asset can be tested and reused independently.
Step-by-Step Technical Analysis: Design the user journey first, then decide which OmniStudio asset owns each responsibility. OmniScript captures guided input, DataRaptors map Salesforce data, Integration Procedures orchestrate server-side work, and FlexCards expose summarized context. After assembly, validate data payloads, error handling, security, and performance with realistic application records. Use OmniStudio, Flow, Employee and Public Sector data models, and an Employee Community experience.
Why the Incorrect Options Are Wrong: B adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement. C may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer. D adds a custom build path and increases lifecycle, security, and upgrade effort when a packaged or declarative capability already supports the requirement.

DocuSign. This answer fits because the requirement is about the specific platform mechanism named in the option, not a nearby workaround.
The Core Concept Explained: Document automation reduces manual review by turning files into governed records, checklist items, extracted fields, or signature events. The design must preserve traceability from upload through review.
Step-by-Step Technical Analysis: Separate document intake from record processing. Configure the document type, checklist, extraction, signature, or IDA/IFR behavior, map the captured values to the application record, and test with real sample files. Confirm exception handling for unreadable documents, missing uploads, and resubmission cycles. Use the DocuSign integration supported by the Public Sector toolkit.
Why the Incorrect Options Are Wrong: 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. D may look related, but it does not place the logic in the correct declarative Public Sector or OmniStudio configuration layer.

The new Action Plan Template has not been activated. This is the lowest-customization answer that still satisfies the business, security, and lifecycle requirements.
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. Activate the new Action Plan Template version and ensure the inspection type points to the intended active template.
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. 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.