KCNA Cloud Native Architecture Practice Question
A team is designing a cloud-native application that requires each microservice to have its own database. This pattern is known as:
⚠ Common exam trap
CNCF often tests the misconception that the Saga pattern defines database ownership, when in fact it is a transaction coordination pattern, not a data isolation strategy.
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
✓
Database-per-service pattern
The Database-per-service pattern is the correct answer because it ensures each microservice owns and manages its own database, enforcing loose coupling and data encapsulation. This aligns with the cloud-native principle of decentralized data management, where services communicate only via APIs and never access each other's databases directly. It prevents tight coupling at the data layer, which is critical for independent scaling, deployment, and resilience in a microservices 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.
- ✗
Saga pattern
Why it's wrong here
The Saga pattern coordinates distributed transactions across services using compensating actions; it does not assign each microservice its own database. It is tempting because it addresses data consistency in microservices, but it is the correct choice when a business transaction spans several services, not when defining database ownership.
- ✓
Database-per-service pattern
Why this is correct
Database-per-service gives each microservice a private datastore, accessed only through its own API. This enforces loose coupling and independent schema evolution, avoiding the shared-database integration that would couple services and undermine the autonomy the stem's design requires.
- ✗
Shared database pattern
Why it's wrong here
The shared database pattern has multiple services reading and writing one schema, which couples them and contradicts the per-service database requirement. It is tempting because it is a recognised microservices data pattern, but it suits small systems where transactional consistency across services outweighs independent deployability and scaling.
- ✗
CQRS pattern
Why it's wrong here
CQRS separates read and write models within a service; it does not require each microservice to own a distinct database. It is tempting because it is a microservices data pattern, but it is the correct choice when read and write workloads need independent scaling or differing schemas, not for database-per-service isolation.
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.