Citizens should reach the production licensing API at api.city.gov rather than the default execute-api URL, and that hostname must map to the prod stage. What configuration achieves that?
Select an answer to reveal the explanation.
Short Explanation
api.city.gov is the polished storefront address—map it to the prod stage, not the warehouse code on the loading dock. Custom domains beat asking people to memorize execute-api URLs. Pointing the public name at test mixes paint colors.
Full Explanation
Citizens should reach the production licensing API at api.city.gov via an API Gateway custom domain mapped to the prod stage rather than bookmarking default execute-api URLs. Custom domains provide stable municipal hostnames bound to specific stages, giving clean environment routing while leaving execute-api URLs for internal use if needed. Hostname-to-stage mapping is the configuration that achieves citizen-facing clarity.
Publishing only the execute-api default URL and asking citizens to bookmark stage names manually fails as poor UX and weak environment hygiene. Pointing api.city.gov at the test stage so production and test share one hostname fails conceptually by mixing environments on the public name. Replacing API Gateway with raw public S3 website hosting for the JSON API fails because S3 websites are not a substitute for API Gateway stage routing and auth integrations.
Exam caveat: custom domain TLS certificates must match the hostname and regional/edge model in use; mis-region ACM certs break attachment. Operational check: configure the custom domain mapping to prod, resolve api.city.gov, invoke a licensing path, confirm the prod stage serves traffic, and ensure test remains on a separate hostname or execute-api URL.