KCNA Cloud Native Architecture Practice Question
A development team is designing a new microservices application to run on a Kubernetes cluster. They want to ensure that each microservice can be developed, deployed, and scaled independently. Which cloud native architecture principle are they primarily applying?
⚠ Common exam trap
Many candidates confuse 'statelessness' with 'loose coupling' because both enable scaling, but statelessness is about session data management, not the architectural independence of service development and deployment.
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
The principle of loose coupling ensures that each microservice can be developed, deployed, and scaled independently by minimizing dependencies between services. In Kubernetes, this is achieved through well-defined APIs and service boundaries, allowing teams to update or scale one service without affecting others. This directly supports the team's goal of independent lifecycle management for each microservice.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Loose coupling
Why this is correct
Loose coupling lets each microservice be changed, deployed and scaled without coordinating with others, since services interact through well-defined interfaces rather than tight dependencies. That directly satisfies the team's requirement for independent development, deployment and scaling.
- ✗
Immutable infrastructure
Why it's wrong here
Immutable infrastructure means replacing rather than mutating running instances, which aids consistent rollouts but does not by itself give each microservice independent development and scaling. It is tempting because containers are rebuilt, yet the stem describes loose coupling between services.
- ✗
Statelessness
Why it's wrong here
Statelessness concerns storing no client session data between requests, enabling any replica to serve any call. It is tempting because stateless services scale horizontally, but independent development, deployment and scaling of each service is the decentralised, service-oriented principle of loose coupling.
- ✗
Service discovery
Why it's wrong here
Service discovery addresses how running instances locate each other's network endpoints, not how teams decouple release cycles. It is genuinely used when pods scale dynamically and clients need current addresses via DNS or a registry, but it does not itself enable independent development, deployment and scaling of each microservice.
Go deeper
Related to this question
Learn chapter
Services and Network Connectivity
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
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.