KCNA Cloud Native Architecture Practice Question
A development team wants to adopt a cloud-native architecture for a new application. Which set of principles BEST describes the cloud-native approach?
⚠ Common exam trap
KCNA often tests whether candidates conflate 'cloud-hosted' with 'cloud-native', so options mixing serverless with VMs or ITIL look plausible to anyone who only skims for buzzwords.
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
✓
Microservices, containers, dynamic orchestration, and DevOps
Cloud-native is defined by the CNCF as combining containers, microservices, service meshes, immutable infrastructure, and declarative APIs — with dynamic orchestration (Kubernetes) and DevOps culture as the operational backbone. Option A bundles all four pillars correctly: microservices for decomposition, containers for packaging, dynamic orchestration for scheduling/scaling, and DevOps for the cultural/process model. These four elements reinforce each other: containers enable microservices, orchestration makes containers manageable at scale, and DevOps provides the feedback loops.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Microservices, containers, dynamic orchestration, and DevOps
Why this is correct
Microservices decompose the application into independently deployable services, containers package each with its dependencies, dynamic orchestration schedules and scales them across nodes, and DevOps automates delivery. Together these four principles satisfy the stem's cloud-native requirement, distinguishing it from monolithic or lift-and-shift approaches.
- ✗
Service-oriented architecture, bare-metal servers, static scaling, and Agile
Why it's wrong here
Bare-metal servers and static scaling contradict cloud-native design, which relies on containers, immutable infrastructure and dynamic orchestration. This set describes a traditional service-oriented deployment, appropriate when workloads cannot be containerised or demand is fixed and predictable.
- ✗
Monolithic applications, virtual machines, manual scaling, and waterfall development
Why it's wrong here
Monoliths, virtual machines, manual scaling and waterfall development each oppose the cloud-native principles of loose coupling, containers, automated elasticity and continuous delivery. It tempts because monoliths and VMs still run production workloads successfully; they simply cannot deliver the independent deployability and rapid iteration this scenario requires.
- ✗
Serverless functions, virtual machines, manual provisioning, and ITIL
Why it's wrong here
Serverless functions and virtual machines are compute models, not cloud-native principles, and manual provisioning plus ITIL change control directly contradict automated, declarative delivery. It tempts because serverless genuinely is cloud-native; however, pairing it with manual provisioning and ITIL governance defeats the reproducibility and elasticity the scenario demands.
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.