KCNA Cloud Native Architecture Practice Question
A team wants to deploy a multi-cloud application that uses cloud-specific services. Which pattern is most appropriate?
⚠ Common exam trap
Watch out — candidates often think 'cloud-agnostic' means avoiding all cloud-specific services, but the correct pattern allows using them through abstraction layers, not eliminating them entirely.
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
✓
Using cloud-agnostic abstractions and infrastructure as code across providers
Using cloud-agnostic abstractions (e.g., Kubernetes for container orchestration, Terraform for infrastructure as code) allows the team to deploy across multiple clouds while still integrating cloud-specific services via provider-agnostic interfaces or abstraction layers. This pattern reduces vendor lock-in, enables consistent deployment workflows, and supports portability without sacrificing the ability to use unique services from each cloud provider.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Single-cloud vendor lock-in to reduce complexity
Why it's wrong here
Single-cloud lock-in contradicts the stated requirement to use cloud-specific services across multiple providers, since it confines the application to one vendor's service catalogue. It is tempting because consolidating on one cloud genuinely reduces operational complexity, which would be correct if the stem prioritised simplicity over multi-cloud portability.
- ✗
Manually managing each cloud separately without automation
Why it's wrong here
Manual per-cloud management without automation cannot coordinate deployments across providers, so configuration drift and inconsistent releases result. It is tempting because hands-on control suits small, stable estates, which would be correct if the question involved a single cloud with infrequent changes rather than a multi-cloud application.
- ✗
Only using serverless functions from one provider
Why it's wrong here
Restricting to one provider's serverless functions prevents the application from consuming cloud-specific services elsewhere, defeating the multi-cloud requirement. It is tempting because serverless removes server management and scales automatically, which would be correct if the stem asked for a single-provider event-driven workload rather than multi-cloud.
- ✓
Using cloud-agnostic abstractions and infrastructure as code across providers
Why this is correct
Cloud-agnostic abstractions with infrastructure as code let the team provision and manage services consistently across providers, avoiding lock-in while still integrating cloud-specific services. This satisfies the multi-cloud portability constraint better than committing to one vendor's proprietary tooling.
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 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.