On a parks recreation API, GET /permits should invoke one Oracle Function and POST /permits should invoke another. What is the correct unit in the deployment specification?
Select an answer to reveal the explanation.
Short Explanation
A route is a labeled hallway: this path, these verbs, that destination. GET and POST on /permits can each point at a different function back end in the specification.
Full Explanation
In an API Gateway deployment specification, a route binds a path together with one or more HTTP methods to a single back end. On the parks recreation API, GET /permits and POST /permits can be modeled as separate method-scoped routes that target different Oracle Functions. That is how read versus create workflows split cleanly under one path prefix without conflating verbs or forcing one function to branch on method internally at the edge.
A Kubernetes Ingress object does not replace API Gateway routes on OCI for this municipal design. Claiming only the path matters and HTTP methods cannot differ per back end on one path is incorrect—method is part of how routes select a back end. Methods are not chosen at invoke time by Object Storage metadata; the deployment specification declares path, method, and destination explicitly.
Exam caveat: request policies and authorization can also vary by route, so method-specific back ends often pair with method-specific access rules on the same path. Operational check: define GET /permits to one Functions back end and POST /permits to another in the deployment specification, call both verbs with representative payloads, confirm each function is invoked appropriately, and ensure disallowed methods return the expected gateway error rather than falling through to the wrong handler.