Select the BYO (Lightning Web Runtime) template and deploy custom- built Lightning Components. 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. Use the BYO Lightning Web Runtime template and deploy custom Lightning Web Components.

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.