A citizen-services team wants HTTPS clients to call an Oracle Function through a normal API path without exposing the signed invoke endpoint or adding a func.yaml triggers block. Which API Gateway back-end type fits?
Select an answer to reveal the explanation.
Short Explanation
Name the function as the route’s back end and let API Gateway ring it for you. That is the documented HTTP API pattern—no triggers stanza and no handing clients a signed invoke URL.
Full Explanation
API Gateway supports a Functions back-end type: you name an OCI Functions application and function, and the gateway invokes that function for matching requests. This is the documented way to present a function as an HTTP API without exposing the signed invoke endpoint or using an unsupported triggers block. The function still keeps its own timeout and 6 MB payload limits.