KCNA Cloud Native Architecture Practice Question
A company is adopting a multi-cloud strategy to avoid vendor lock-in. Which pattern BEST supports deploying applications across different cloud providers with minimal changes?
⚠ Common exam trap
KCNA often tests the misconception that using native cloud services or provider-detection code achieves portability — candidates miss that Kubernetes provides the abstraction layer that minimizes changes across clouds.
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
✓
Deploy applications using Kubernetes on each cloud
Deploying applications using Kubernetes on each cloud provides a consistent orchestration and API layer across providers, so workloads can be moved with minimal changes. Kubernetes abstracts compute, networking, and storage through standard primitives (Pods, Services, PVCs), reducing provider-specific coupling. This is the core pattern for portable multi-cloud deployments.
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 hybrid cloud approach with a single cloud for all workloads
Why it's wrong here
Consolidating workloads onto one cloud within a hybrid model does not distribute applications across providers, so vendor lock-in persists. Hybrid cloud is correct when the goal is connecting on-premises systems to a single provider, not avoiding dependence on any one of several.
- ✓
Deploy applications using Kubernetes on each cloud
Why this is correct
Kubernetes abstracts compute, networking and storage behind a consistent API, so the same manifests and workloads run on any conformant cluster. This directly satisfies the stem's vendor lock-in constraint: portability across providers comes from the open API surface, not from provider-specific services.
- ✗
Use each cloud provider's native services directly
Why it's wrong here
Native services tie workloads to each provider's proprietary APIs, so portability across clouds requires per-provider rewrites. It is tempting because native services give the deepest integration and lowest latency within a single cloud, which is the right choice when lock-in is accepted and one provider's features are exploited fully.
- ✗
Write application code that checks the cloud provider and adapts
Why it's wrong here
Provider-detection branches inside application code couple the workload to each cloud's APIs, so every provider added means code changes — the opposite of minimal change. It would suit a temporary bridge while porting, not a portable multi-cloud deployment pattern.
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 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.