Courseiva
Container Orchestration →hardMultiple Choice

KCNA Container Orchestration Practice Question

You are designing a microservices application. Which of the following is a key principle of microservices architecture?

⚠ Common exam trap

CNCF often tests the misconception that microservices require a single shared database or a single programming language, confusing microservices with a distributed monolith; the trap here is assuming that 'fast communication' (Option B) justifies tight coupling, when in reality loose coupling is prioritized for resilience and independent deployability.

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

✓

Services are loosely coupled and can be deployed independently

Microservices architecture is fundamentally defined by loose coupling and independent deployability. Each service encapsulates its own domain logic, communicates via lightweight protocols like HTTP/REST or gRPC, and can be updated, scaled, or deployed without affecting other services. This aligns with the Kubernetes-native pattern of managing each microservice as a separate Deployment or StatefulSet, enabling continuous delivery and resilience.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Services are loosely coupled and can be deployed independently

    Why this is correct

    Loose coupling means services interact through well-defined interfaces with minimal shared state, so each can be built, tested and released on its own schedule. This satisfies the independent deployability requirement, distinguishing microservices from monolithic or tightly coupled tiers.

  • ✗

    Services are tightly coupled to allow fast communication

    Why it's wrong here

    Tight coupling means a change in one service forces coordinated redeployment of others, defeating independent deployability and fault isolation. Microservices require loose coupling through stable, versioned interfaces so each service evolves autonomously. Tight coupling describes a monolithic or SOA integration style, where in-process calls made latency the priority.

  • ✗

    All services must be written in the same programming language

    Why it's wrong here

    Polyglot persistence and independent deployability mean each service may use whatever language and runtime its team prefers, communicating over language-agnostic APIs. Mandating one language couples teams' release cycles and technology choices, contradicting decentralised governance. A single-language stack is a monolith trait, not a microservices principle.

  • ✗

    All services must share a common database

    Why it's wrong here

    A shared database couples services through a common schema: any migration or write lock affects every consumer, preventing independent deployment and data ownership. Microservices give each service its own datastore, integrating via APIs or events. A shared database is the correct pattern for a modular monolith, not distributed services.

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 →

How Courseiva writes practice questions · Editorial policy

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.