Bobahaven has previously implemented Agentforce Service to handle constituent queries and complaints, including a constituent...

The Licenses and Permits Experience Cloud template should be used because Salesforce supplies it specifically for constituent licensing and permitting experiences. It includes preconfigured pages for applying for licenses or permits, renewing authorizations, viewing applications and licenses, reviewing inspection history, filing complaints, and identifying permit requirements.

Using this purpose-built template significantly reduces custom implementation and long-term maintenance compared with retrofitting a generic Help Center site. Salesforce also provides OmniStudio-driven application capabilities that can be placed directly into Experience Cloud, including dynamic application forms built with OmniScripts and supporting components.

Option C could technically be implemented, but it would require the agency to manually recreate capabilities that Salesforce already supplies through the dedicated template. That contradicts the requirement to minimize customization and maintenance.

OmniOut is intended for scenarios where OmniStudio experiences must run outside Salesforce-hosted environments. Since the requested constituent application experience is being implemented directly on Experience Cloud, OmniOut adds unnecessary architecture and deployment complexity. Therefore, neither A nor D represents the most maintainable design.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Licenses and Permits Experience Cloud Site; Experience Cloud templates; OmniScripts; FlexCards; reuse of preconfigured Public Sector components.

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