A parks-and-recreation team has an OpenAPI 3.0 description for a new reservations API and wants OCI API Gateway routes pre-populated from that file. Creating an API resource is optional. What happens when they upload the OpenAPI description?
Select an answer to reveal the explanation.
Short Explanation
Uploading OpenAPI is like bringing a blueprint so the permit desk can pre-draw the windows and doors—handy, not mandatory. The description pre-populates deployment routes, and paths without a documented response get a stock 501 until you wire a real back end. You can still author the specification in the console or as JSON without an API resource.
Full Explanation
OCI API Gateway optionally accepts an API resource backed by an OpenAPI 2.0 or 3.0 description that pre-populates deployment routes. Paths that lack a documented response receive a stock 501 response until you configure a real back end. Creating the API resource is optional—you can author the specification in the console or as JSON without importing OpenAPI. Import is a convenience for route scaffolding, not SDK generation or mandatory setup.