KCNA Cloud Native Architecture Practice Question
A team is designing a cloud-native application and wants to ensure that the failure of a single availability zone does not cause a full outage. They deploy the application across multiple zones and configure the orchestrator to distribute replicas evenly. Which cloud-native architecture principle does this scenario primarily demonstrate?
⚠ Common exam trap
A common mix-up: candidates confuse high availability techniques with unrelated cloud-native principles such as immutable infrastructure or declarative configuration, which do not directly explain zone-failure tolerance.
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
✓
Design for failure
The scenario describes spreading replicas across multiple availability zones so that a single zone failure does not cause a full outage. This is the essence of designing for failure, where redundancy and fault isolation are built into the architecture. While other principles like declarative configuration or loose coupling may also be present, they do not directly address surviving a zone-level failure.
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 it's wrong here
Loose coupling reduces dependencies between components so changes in one do not break another. Distributing replicas across zones is about fault isolation and availability, not about minimizing inter-service dependencies. Loose coupling is valuable but does not by itself ensure that a zone outage will not take down the application.
- ✗
Declarative configuration
Why it's wrong here
Declarative configuration describes the desired state and lets the system reconcile it. Although the team likely uses declarative manifests to specify replica counts, the core principle illustrated here is resilience to zone failure, not the method of expressing configuration. The emphasis is on surviving failure through redundancy, not on how the desired state is declared.
- ✓
Design for failure
Why this is correct
Distributing replicas across multiple availability zones ensures that if one zone fails, the application continues to run. This is a direct implementation of the design-for-failure principle, which assumes components will fail and builds redundancy to maintain availability. By spreading workloads, the system tolerates zone-level outages without manual intervention.
- ✗
Immutable infrastructure
Why it's wrong here
Immutable infrastructure means servers are never modified after deployment; instead, new instances replace old ones. While this practice improves consistency and rollback, it does not directly address spreading replicas across zones to survive an outage. The scenario focuses on fault tolerance through distribution, not on replacing rather than mutating servers.
Go deeper
Related to this question
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.