Question 390
An API gateway exposes internal services directly and permits anonymous administrative operations. Which control design should be prioritized to meet the business requirement?
Explanation
Correct Answer
place Azure API Management before APIs with authenticated and authorized management paths. This is the most relevant choice because API gateways can centralize enforcement but require actual policy configuration. An acceptance test should demonstrate that unauthenticated callers cannot invoke privileged backend operations through the gateway.
Incorrect Answers
This measure is suited to a different threat model: An API requires different partner subscriptions to have independent usage quotas. Per-consumer API policies prevent cross-client resource exhaustion. It does not directly establish that unauthenticated callers cannot invoke privileged backend operations through the gateway.
It addresses a neighboring control requirement, not this one: An app needs to expose only selected backend fields to partner consumers. An API facade can enforce data minimization at a shared consumption boundary. The present scenario specifically needs unauthenticated callers cannot invoke privileged backend operations through the gateway.
That recommendation concerns A backend trusts an API gateway header claiming user identity without verifying its provenance. Caller-controlled headers must not substitute for authenticated identity. Here the required proof is that unauthenticated callers cannot invoke privileged backend operations through the gateway.