A long-running permitting microservice already listens behind a load balancer on OKE. The team wants API Gateway to forward /v1/applications there. Which back-end choice is appropriate?
Select an answer to reveal the explanation.
Short Explanation
If the work already has an address, send the gateway there with an HTTP(S) URL back end. Do not wrap a healthy microservice in a do-nothing function just to look serverless.
Full Explanation
API Gateway’s HTTP or HTTPS URL back end forwards the request to an existing URL such as a microservice on OKE via a load balancer, a compute listener, or a partner API. You configure timeout and whether to skip SSL verification. Use this when the workload already lives behind a URL rather than forcing a no-op Functions wrapper.