KCNA Cloud Native Architecture Practice Question
A development team is containerizing a monolithic application into microservices. Which practice aligns with cloud-native architecture principles?
⚠ Common exam trap
CNCF often tests the misconception that 'shared data ensures consistency' (Option A) or that 'identical resource limits simplify management' (Option D), while the correct answer emphasizes data autonomy and API-based communication as the hallmark of cloud-native design.
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
✓
Design each microservice with its own data store and communicate via APIs.
Cloud-native architecture principles advocate for decentralized data management, where each microservice owns its private data store and exposes functionality via well-defined APIs. This ensures loose coupling, independent scalability, and resilience, as services can evolve without impacting others. The pattern aligns with the Database per Service pattern, a core tenet of microservices design.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a shared database for all microservices to ensure data consistency.
Why it's wrong here
A shared database couples services through one schema, so a change for one breaks others and blocks independent deployment; cloud-native design gives each service its own datastore. Shared databases fit monoliths or reporting replicas, not decomposed services needing autonomous release cycles.
- ✗
Use JSON Web Tokens for authentication between microservices in the same cluster.
Why it's wrong here
Using JWTs for inter-service authentication within a single cluster introduces unnecessary cryptographic overhead and key management complexity when a service mesh or platform-level mTLS (mutual TLS) already provides transparent, zero-trust transport security. This option is tempting because JWTs are a standard, stateless method for delegating identity in distributed systems, and they would be correct for authenticating external clients or cross-cluster communication where a shared trust domain does not exist.
- ✓
Design each microservice with its own data store and communicate via APIs.
Why this is correct
Decentralised data ownership lets each microservice evolve its schema independently, avoiding the shared-database coupling that would reintroduce monolith-style coordination. API-based communication enforces loose coupling and independent deployability, directly satisfying the cloud-native constraint of per-service autonomy and fault isolation.
- ✗
Ensure all microservices have identical resource requests and limits.
Why it's wrong here
Identical requests and limits prevent per-service right-sizing, so a memory-hungry service throttles while a lightweight one wastes capacity; Kubernetes schedules on each container's declared values. Uniform sizing suits homogeneous replicated workloads, not microservices with divergent profiles.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.