Test your API Gateway knowledge with a free interactive quiz — 27 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What should happen if a gateway has no timeout configured on calls to a backend service?
In this round
What should happen if a gateway has no timeout configured on calls to a backend service?
What problem does request/response transformation at the gateway solve?
Which statement about TLS termination at the API gateway is accurate?
What is the risk of an API gateway configuration that applies no request size limit on incoming bodies?
Why is it considered an anti-pattern to accumulate business logic (e.g. pricing rules, discount calculations) inside the gateway layer?
What does rate limiting at an API gateway protect against?
A gateway route returns inconsistent error shapes depending on which backend service failed. What is the best gateway-level fix?
What is the key architectural difference between an API gateway and a plain load balancer?
Fine-grained, resource-level authorization (e.g. "can this user edit this specific order") is best enforced where?
What is a key operational risk of a gateway plugin that retries every failed upstream call indefinitely with no backoff or cap?
A gateway route is configured with `strip_path: false` for a service mounted at `/api/orders`. What does this setting control?
What is the main advantage of using attribute/path-based routing at the gateway to run two API versions (`/v1/orders` and `/v2/orders`) simultaneously?
Gaps to close?
Read the curated API Gateway notes — core concepts, patterns, interview prep.