KCNA Cloud Native Architecture Practice Question
Which of the following is a core principle of cloud native architecture as defined by the CNCF?
⚠ Common exam trap
KCNA often tests the misconception that cloud native is just 'running in the cloud' — candidates may pick static infrastructure or manual scaling because they associate cloud with VMs, missing that cloud native specifically means containers, microservices, and automation.
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 packaged in containers
The CNCF defines cloud native as an approach that uses containers, service meshes, microservices, immutable infrastructure, and declarative APIs to build loosely coupled systems that are resilient, manageable, and observable. Microservices packaged in containers is the foundational pattern: each service is independently deployable, scalable, and isolated, which enables the automation and orchestration (e.g., Kubernetes) that cloud native relies on.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monolithic application design
Why it's wrong here
Cloud native architecture favours loosely coupled, independently deployable services, so monolithic design contradicts the CNCF microservices principle. It tempts because monoliths can be containerised and deployed to Kubernetes, but packaging a monolith does not make its architecture cloud native.
- ✗
Manual scaling of applications
Why it's wrong here
Cloud native architecture relies on automated, elastic scaling driven by demand signals, so manual scaling contradicts the CNCF principle of automation. It tempts because operators can still scale workloads by hand, but that is an operational fallback rather than a defining architectural principle.
- ✗
Static infrastructure provisioning
Why it's wrong here
Cloud native infrastructure is provisioned dynamically and declaratively, so static provisioning conflicts with the CNCF principle of automated, immutable infrastructure. It tempts because fixed servers remain common in legacy estates, but cloud native design assumes infrastructure defined as code and replaced rather than hand-configured.
- ✓
Microservices packaged in containers
Why this is correct
Microservices packaged in containers is a CNCF cloud native principle: loosely coupled services, each in its own container, deployed and scaled independently. This enables resilience, portability and automated orchestration, distinguishing cloud native design from monolithic deployment.
Go deeper
Related to this question
Learn chapter
Container Orchestration Essentials
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.
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.
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.