An economic-development office created an OCI API Gateway and defined routes on paper, but callers still receive nothing useful. What must exist before the gateway can serve the API?
Select an answer to reveal the explanation.
Short Explanation
A gateway without a deployment is like a finished storefront with no shelves stocked—nothing for shoppers to match. Until you create an API deployment whose specification has at least one route, the gateway has nothing to serve. Editing routes later updates that deployment; it does not require a brand-new gateway. Think appliance first, then deployment—the same pattern as an Functions application before a function.
Full Explanation
Official OCI API Gateway create-deployment guidance: the gateway serves traffic only after you create an API deployment with a specification that includes at least one route. Subsequent route changes update the existing deployment; they do not require provisioning a new gateway. The mental model mirrors Oracle Functions—an application (or gateway) is the container, and the deployment (or function) is what makes the API live.