KCNA Cloud Native Architecture Practice Question
What is the primary purpose of the sidecar container in a service mesh?
⚠ Common exam trap
CNCF often tests the misconception that the sidecar's primary role is logging and monitoring, but the correct answer is always traffic interception and management, as that is the core architectural purpose of a service mesh sidecar.
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
✓
To intercept and manage network traffic for the main container
In a service mesh, the sidecar container (typically an Envoy or Linkerd proxy) is injected alongside the main application container to intercept and manage all inbound and outbound network traffic. This allows the service mesh to enforce traffic policies, handle service discovery, implement retries and circuit breaking, and collect telemetry without modifying the application code. The sidecar operates at the network layer (L4/L7), decoupling communication concerns from business logic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To run application business logic
Why it's wrong here
Business logic belongs in the main application container; the sidecar runs alongside it in the same pod to handle cross-cutting concerns such as mTLS, traffic routing and telemetry. Running business logic in a sidecar would be correct only when extracting a separate concern from the primary service.
- ✗
To handle logging and monitoring of the main container
Why it's wrong here
Logging and monitoring are sidecar responsibilities, but the primary purpose is intercepting and securing all inbound and outbound traffic via mTLS, policy enforcement and traffic shaping. Logging alone would be correct for a dedicated logging agent, not a service-mesh sidecar proxy.
- ✗
To provide persistent storage for the main container
Why it's wrong here
Sidecars intercept network traffic to enforce mTLS, retries and telemetry; they do not attach volumes to the main container. Persistent storage is provided by Kubernetes volumes or PersistentVolumeClaims, which would be the correct mechanism when an application needs durable data across pod restarts.
- ✓
To intercept and manage network traffic for the main container
Why this is correct
The sidecar proxy runs alongside the main container and transparently intercepts inbound and outbound network traffic, enforcing mTLS, routing, retries and telemetry policies. This offloads service-mesh networking concerns from application code without modifying the main container.
Go deeper
Related to this question
Learn chapter
Cloud Native Application Design Principles
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
Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.