A building-department API receives incomplete permit payloads that waste Function invocations. The team wants malformed requests rejected at the front door before any back end runs. Which API Gateway feature fits?
Select an answer to reveal the explanation.
Short Explanation
Validating at the gateway is like a clerk rejecting an incomplete permit form before it reaches the plan-reviewer—saving everyone’s time. A request validation policy checks schema and required parameters and fails junk at the front door instead of invoking a Function or HTTP back end. Validation shields the back end; it is not a substitute for proper testing.
Full Explanation
OCI API Gateway request validation policies validate inbound requests against the deployment’s schema and required-parameter rules and fail them at the gateway. That prevents Functions or HTTP back ends from being invoked with incomplete or invalid input. Validation is a front-door shield for the back end, not a replacement for unit, contract, or integration testing of the application itself.