Three city departments want separate API path prefixes and policies but one shared public hostname. When is a second API Gateway unnecessary?
Select an answer to reveal the explanation.
Short Explanation
One reception building can host several department desks—multiple deployments on one gateway. Open a second gateway when public versus private front end or VCN attachment must differ.
Full Explanation
Multiple APIs can be deployed on the same API Gateway, each with its own path prefix, routes, and policies, presenting several backend teams under one hostname. Create separate gateways when the front-end type (public versus private) or the VCN attachment must differ—not merely because teams want different path prefixes.