KCNA Cloud Native Architecture Practice Question
A team is evaluating whether their application qualifies as cloud-native. They want to identify characteristics that are central to cloud-native architecture rather than incidental implementation details. Which TWO of the following are core characteristics of cloud-native architecture? (Choose two.)
⚠ Common exam trap
The trap here is selecting operational conveniences or performance optimizations, such as reducing network calls through tight coupling, instead of the architectural principles that define cloud-native systems.
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
✓
Declarative configuration and automated management
Declarative configuration with automated management and resilience through fault tolerance and graceful degradation are core cloud-native characteristics. They shape how systems are defined, reconciled, and kept running under failure. Manual provisioning, tight coupling, and exclusive reliance on proprietary APIs work against portability, automation, and independent operation, so they are not central characteristics of cloud-native architecture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Declarative configuration and automated management
Why this is correct
Declarative configuration expresses the desired state, and automation continuously reconciles actual state to match it. This is central to cloud-native architecture because it enables reproducible deployments, self-healing, and scalable operations. Kubernetes controllers and GitOps workflows are common examples. This characteristic directly reflects how cloud-native systems are managed rather than an incidental detail.
- ✗
Manual, ticket-driven provisioning of production servers
Why it's wrong here
Manual, ticket-driven provisioning is the opposite of cloud-native practice. It is slow, error-prone, and difficult to reproduce at scale. Cloud-native architecture favors automated, declarative provisioning through APIs and infrastructure as code. This option describes a traditional operations model and does not represent a core characteristic of cloud-native systems.
- ✗
Tight coupling between services to reduce network calls
Why it's wrong here
Tight coupling makes services harder to deploy, scale, and recover independently. Cloud-native architecture favors loose coupling through well-defined interfaces, often over a network. Reducing network calls by coupling services tightly trades resilience and agility for marginal performance gains. This is not a core characteristic and contradicts the goals of independent deployability and fault isolation.
- ✓
Resilience through fault tolerance and graceful degradation
Why this is correct
Cloud-native systems are designed to expect failure and continue operating. Resilience is achieved through techniques such as replication, health checks, retries, circuit breakers, and graceful degradation. This is a core architectural characteristic because it shapes how services are designed, deployed, and operated. It is not an incidental detail but a fundamental design goal.
- ✗
Vendor-specific, proprietary APIs for all internal communication
Why it's wrong here
Cloud-native architecture generally favors open standards and portable interfaces to avoid lock-in and enable interoperability. Relying exclusively on proprietary APIs for internal communication increases coupling to a vendor and reduces flexibility. While some managed services are proprietary, making them the foundation of all internal communication is not a core cloud-native characteristic.
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.