Question 480
A public SQL-backed REST API receives uncontrolled high-rate requests that exhaust database connections. The team is considering this step: Configure bounded request throttling and authenticated client policies at the proper tier. What evidence should they review before proceeding?
Explanation
Correct Answer
Inspect rate metrics, client identities, SQL pool occupancy and allowed service limits. API gateways and endpoint-level quotas can limit abusive request load independently of SQL roles. Burst tests receive controlled rate-limit responses without starving legitimate users.
Incorrect Answers
This evidence check would miss the central issue: Query efficiency and inbound request control are separate; test burst rate limiting at the right tier.
The proposed diagnostic comparison leaves a gap: Distributed enforcement and identity-aware quotas require appropriate gateway/service tier behavior.
Such observations do not establish the required mechanism: Rate limits should preserve intended clients, return consistent status and avoid starving normal workloads. The candidate check cannot distinguish the required state from a superficial symptom, and so does not justify the proposed change.