Question 690
A business exposes legacy APIs but cannot prevent unauthorized methods or parameter values. Which design choice best addresses the identified risk without unnecessary privileges?
Explanation
Correct Answer
API validation should enforce intended contracts before backend execution. Therefore, the targeted architectural decision is apply explicit method, schema, and authorization validation at the API layer. Confirm that unsupported methods and malformed high-risk parameters receive controlled rejection.
Incorrect Answers
The alternative focuses on An API gateway exposes internal services directly and permits anonymous administrative operations. API gateways can centralize enforcement but require actual policy configuration. It is not the direct response needed to demonstrate unsupported methods and malformed high-risk parameters receive controlled rejection.
This measure is suited to a different threat model: An app needs to expose only selected backend fields to partner consumers. An API facade can enforce data minimization at a shared consumption boundary. It does not directly establish that unsupported methods and malformed high-risk parameters receive controlled rejection.
It addresses a neighboring control requirement, not this one: An application uses HTTP APIs to issue payment transfers without recording idempotency keys. API security includes protection against unintended transaction replay. The present scenario specifically needs unsupported methods and malformed high-risk parameters receive controlled rejection.