KCNA Cloud Native Architecture Practice Question
A team is designing a cloud-native system that must remain available even if an entire availability zone fails. They want to distribute workloads across multiple zones and automatically recover from failures. Which cloud-native architectural approach BEST addresses this requirement?
⚠ Common exam trap
The trap here is thinking that a load balancer or vertical scaling alone provides zone-level fault tolerance; without distributing replicas across zones, a single zone outage still takes down the application.
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
✓
Use a multi-zone cluster with anti-affinity rules and health checks
Spreading workloads across multiple availability zones with anti-affinity and health checks enables the system to tolerate a zone failure. Kubernetes can reschedule pods from a failed zone onto nodes in healthy zones, maintaining service. This design is a standard cloud-native pattern for high availability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Rely on vertical scaling of a single large node
Why it's wrong here
Vertical scaling increases resources on one node but does not address zone-level failures. If that node or its zone fails, the application becomes unavailable. This approach also has limits and does not provide the distributed fault tolerance required for surviving an availability zone outage.
- ✗
Store all state in a single-zone database
Why it's wrong here
A single-zone database is a single point of failure. If that zone becomes unavailable, the application loses access to its data, causing an outage. This contradicts the goal of surviving a zone failure. State must be replicated across zones or use a multi-zone database service to achieve the required availability.
- ✗
Deploy all replicas in a single zone with a load balancer
Why it's wrong here
Placing all replicas in one zone means a zone failure takes down the entire application, regardless of load balancing. A load balancer distributes traffic but cannot mitigate a zone-wide outage. This design lacks the fault isolation needed for high availability across zones, so it does not meet the requirement.
- ✓
Use a multi-zone cluster with anti-affinity rules and health checks
Why this is correct
A multi-zone cluster spreads nodes and pods across zones. Anti-affinity rules ensure replicas are not co-located, and health checks trigger rescheduling if a zone fails. This provides fault tolerance and automatic recovery, directly satisfying the requirement for availability during a zone outage.
Go deeper
Related to this question
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 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.