KCNA Cloud Native Architecture Practice Question
Which TWO of the following are key characteristics of cloud-native applications? (Select two.)
⚠ Common exam trap
KCNA often tests the misconception that 'cloud-native' simply means 'running in the cloud', tricking candidates into selecting options like long-lived VMs or manual scaling that describe traditional cloud-hosted rather than cloud-native architectures.
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 architecture
Option B is correct because cloud-native applications are built as microservices architecture, decomposing functionality into small, independently deployable services that communicate over lightweight APIs (e.g., REST/gRPC), enabling independent scaling and resilience. Option C is correct because cloud-native apps are typically packaged and deployed in containers (e.g., Docker images orchestrated by Kubernetes), which provide portability, immutable artifacts, and fast, consistent deployment across environments. Option A is incorrect because monolithic architecture is the opposite of the loosely coupled, independently deployable services that characterize cloud-native design. Option D is incorrect because cloud-native applications rely on automated/elastic scaling (e.g., Horizontal Pod Autoscaler, auto-scaling groups) rather than manual scaling. Option E is incorrect because long-lived virtual machines reflect traditional, pet-style infrastructure, whereas cloud-native workloads favor ephemeral, disposable instances and containers managed declaratively.
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 architecture
Why it's wrong here
Monolithic architecture packages all functionality into one deployable unit, preventing the independent scaling and release that cloud-native design demands. It is tempting because many legacy systems are monolithic, but that is precisely the anti-pattern the question contrasts against; microservices, not monoliths, satisfy the cloud-native criteria.
- ✓
Microservices architecture
Why this is correct
Microservices architecture decomposes an application into independently deployable services, each owning its own data and lifecycle. This satisfies the stem's characteristic criterion by enabling independent scaling, fault isolation, and rapid iteration, which monolithic designs cannot match.
- ✓
Containerized deployment
Why this is correct
Containerised deployment packages each service with its dependencies, giving the portability and consistent runtime behaviour cloud-native applications require. This satisfies the stem's characteristic criterion by enabling rapid, repeatable scaling and deployment across environments independent of underlying host configuration.
- ✗
Manual scaling
Why it's wrong here
Manual scaling contradicts cloud-native elasticity, where workloads scale automatically via orchestrators such as Kubernetes in response to demand. It is tempting because operators do sometimes adjust replica counts by hand, but that is an operational workaround, not a defining characteristic; automatic, declarative scaling is what the stem requires.
- ✗
Long-lived virtual machines
Why it's wrong here
Long-lived virtual machines treat servers as pets to be maintained indefinitely, whereas cloud-native workloads run as ephemeral, replaceable containers. It is tempting because VMs still host some cloud-native components, but that is infrastructure, not the application characteristic sought; immutable, short-lived instances are what the stem requires.
Go deeper
Related to this question
Learn chapter
Services and Network Connectivity
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.