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.