KCNA Cloud Native Architecture Practice Question
Which of the following is a benefit of using a service mesh?
⚠ Common exam trap
KCNA often tests whether candidates attribute application-level concerns (scaling, storage, database access) to the service mesh, so options like 'automatic scaling' look plausible because the mesh does expose metrics that *feed* autoscalers.
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
✓
Enhanced observability and traffic control
A service mesh (Istio, Linkerd, Consul Connect) injects sidecar proxies alongside application pods to intercept all service-to-service traffic, providing uniform mTLS, traffic shifting, retries, circuit breaking, and rich telemetry (latency, error rates, request tracing) without application code changes. Option C correctly identifies the two headline benefits: enhanced observability and traffic control. These capabilities are delivered at the infrastructure layer, transparently to the application.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Simplified storage management
Why it's wrong here
Storage management concerns persistent volumes, claims and CSI drivers, which a service mesh does not touch; it handles east-west traffic through sidecar proxies. It is tempting because a mesh reduces the networking code each service must implement, but provisioning and attaching storage remains the orchestrator's and storage provider's responsibility.
- ✗
Automatic scaling of applications
Why it's wrong here
Automatic scaling is performed by the Kubernetes Horizontal Pod Autoscaler or cluster autoscaler, which act on metrics and node capacity; a service mesh only routes and secures traffic between existing pods. It is tempting because meshes expose traffic metrics that can feed scaling decisions, but they do not themselves add or remove replicas.
- ✓
Enhanced observability and traffic control
Why this is correct
A service mesh provides mutual TLS, traffic routing and telemetry at the sidecar proxy layer, giving consistent observability and fine-grained traffic control across services without changing application code. That combination of visibility and control is the benefit the question asks for.
- ✗
Direct database access
Why it's wrong here
Direct database access is not a service mesh function; a mesh operates at the network layer, mediating service-to-service traffic via sidecar proxies for mTLS, retries and observability, and does not grant or manage database connectivity. It is tempting because meshes do simplify some backend communication concerns, but data-store access is handled by application drivers and connection pools.
Go deeper
Related to this question
Learn chapter
Observability: Monitoring, Logging, and Tracing
Key term
Service Mesh
A service mesh is a dedicated infrastructure layer that manages communication between microservices, handling tasks like service discovery, load balancing, encryption, and observability without requiring changes to application code.
About these practice questions
One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.