KCNA Container Orchestration Practice Question
Which TWO are characteristics of the microservices architecture that are supported by container orchestration?
⚠ Common exam trap
A common misconception tested in the KCNA exam is that microservices require a shared database or tight coupling for performance, but the correct answer emphasizes independent deployment and decomposition, which are the defining characteristics supported by container orchestration.
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
✓
Independent deployment of each service
Option B is correct because container orchestration platforms such as Kubernetes let each microservice be built, versioned, and rolled out on its own schedule, so a change to one service does not force redeployment of the others. Option C is correct because microservices architecture decomposes an application into small, independently runnable services, and orchestration supports this by scheduling, scaling, and networking each service as a separate workload. Options A, D, and E are not characteristics of microservices supported by orchestration: tight coupling, a monolithic codebase with centralized deployment, and a single shared database all describe monolithic or tightly integrated designs that contradict the independence and loose coupling that orchestration enables.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Tight coupling between services to ensure performance
Why it's wrong here
Tight coupling contradicts the independent deployability and scaling that orchestration platforms like Kubernetes provide; each microservice must be separately releasable and scalable. It is tempting because coupling services can reduce network latency in monolithic or performance-critical designs, where shared in-process calls genuinely outperform inter-service communication.
- ✓
Independent deployment of each service
Why this is correct
Container orchestration lets each microservice be built, versioned and released on its own schedule, so teams deploy independently without coordinating a monolithic release. This satisfies the stem's requirement by matching the architectural trait of decoupled, autonomous service delivery.
- ✓
Decomposition of an application into small, independent services
Why this is correct
Microservices decompose an application into small, independently deployable services, each running in its own container. Container orchestration then schedules, scales and networks these discrete units, directly satisfying the stem's requirement for decomposition into independent services rather than a single monolithic process.
- ✗
Monolithic codebase with centralized deployment
Why it's wrong here
A monolithic codebase with centralised deployment contradicts the independent, per-service deployability that container orchestration exists to support; orchestrators schedule discrete containers, not one coupled artefact. It is tempting because centralised deployment genuinely suits single-unit applications, where one build-and-release pipeline is the intended model rather than a limitation.
- ✗
Use of a single, shared database for all services
Why it's wrong here
A shared database couples services through a common schema, so independent deployment and scaling break. It is tempting because it simplifies transactions and reporting; it would suit a monolith, not the decentralised data ownership container orchestration supports.
Go deeper
Related to this question
Learn chapter
Kubernetes Networking and DNS
Key term
Microservices Architecture
Microservices architecture is a way of building software as a collection of small, independent services that each handle one specific business function and communicate over a network.
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
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 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.