KCNA Container Orchestration Practice Question
Which of the following is a key principle of microservices architecture?
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
✓
Loose coupling and independent deployability
Microservices architecture emphasizes breaking an application into small, independently deployable services that communicate over well-defined APIs. The correct answer is C: Loose coupling and independent deployability are key principles. Option A (shared database) contradicts the principle of service autonomy. Option B (tight coupling) is the opposite of what microservices aim for. Option D (monolithic codebase) is what microservices avoid.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Shared database schema for all services
Why it's wrong here
A shared database schema couples services through common tables, so a change to one service's data model forces coordinated redeployment of others, defeating independent deployability. It is tempting because a single schema suits monolithic applications, where all modules legitimately share one tightly coupled data store.
- ✗
Tight coupling between services
Why it's wrong here
Tight coupling binds services so changes in one force changes in others, contradicting microservices' independent deployability and bounded contexts. It is tempting because coupling exists in every architecture, but microservices deliberately pursue loose coupling through well-defined APIs so each service can evolve and scale autonomously.
- ✓
Loose coupling and independent deployability
Why this is correct
Loose coupling lets each microservice evolve, scale and be deployed without coordinated releases of other services, since communication occurs through well-defined APIs rather than shared internal state. Independent deployability is the operational outcome that enables frequent, low-risk releases.
- ✗
Building a large, monolithic codebase
Why it's wrong here
A large monolithic codebase means every change requires rebuilding and redeploying the whole application, so services cannot scale or release independently. It is tempting because monoliths are the correct starting point for small teams and simple domains where operational overhead must stay low.
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 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.