KCNA Cloud Native Architecture Practice Question
You are implementing an API gateway pattern for a set of microservices. Which of the following is a typical responsibility of an API gateway?
⚠ Common exam trap
KCNA often tests the boundary between gateway responsibilities (routing, auth, rate limiting) and orchestrator responsibilities (container lifecycle, scaling), so candidates confuse the API gateway with Kubernetes control-plane functions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enforcing authentication and rate limiting
An API gateway sits in front of microservices and centralizes cross-cutting concerns such as authentication, authorization, rate limiting, request routing, and TLS termination. Enforcing authentication and rate limiting is a canonical gateway responsibility because it offloads these concerns from individual services. This lets each microservice focus on business logic while the gateway handles policy uniformly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Managing container lifecycle and scaling
Why it's wrong here
Container lifecycle and scaling belong to the orchestrator (Kubernetes), which schedules pods and adjusts replicas; an API gateway only routes, authenticates and rate-limits north-south traffic. It is tempting because gateways are deployed alongside clusters, but orchestration is the correct answer when the question asks who restarts failed pods or performs horizontal scaling.
- ✗
Directly accessing databases to serve requests
Why it's wrong here
Gateways proxy client requests to services; they hold no data-access layer, and direct database access would couple the gateway to schemas and bypass service ownership. It is tempting because gateways do aggregate responses, but direct database access is correct only for a backend-for-frontend or service that owns that data store.
- ✗
Storing application state and session data
Why it's wrong here
API gateways route requests, terminate TLS, authenticate callers and apply rate limits; they are stateless and hold no session data. State storage belongs in a dedicated data store or cache, which would be the correct component when persistence across requests is genuinely required.
- ✓
Enforcing authentication and rate limiting
Why this is correct
API gateways centralise cross-cutting concerns for microservices, including authentication, authorisation, rate limiting, and request routing. Enforcing authentication and rate limiting is a canonical gateway responsibility, offloading these tasks from individual services rather than duplicating them in each.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.