Courseiva
Cloud Native Architecture →mediumMultiple Choice

KCNA Cloud Native Architecture Practice Question

In a multi-cloud architecture, what is a common use case for a service mesh?

⚠ Common exam trap

CNCF often tests the misconception that a service mesh is a general-purpose tool for all cross-cloud operations, when in reality it is specifically designed for service-to-service communication (east-west traffic) and does not handle resource synchronization, storage, or ingress gateway functions.

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

✓

To enable secure service-to-service communication across clusters

A service mesh, such as Istio or Linkerd, provides a dedicated infrastructure layer for handling service-to-service communication. In a multi-cloud architecture, its common use case is to enable secure, observable, and resilient communication between services running in different Kubernetes clusters across clouds, using mutual TLS (mTLS) for encryption and traffic policies for routing.

Answer analysis

Option-by-option breakdown

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

  • ✓

    To enable secure service-to-service communication across clusters

    Why this is correct

    A service mesh provides mutual TLS, identity-based authorisation and traffic policy between workloads, extending these controls across Kubernetes clusters on different providers. That directly satisfies the multi-cloud constraint, where native cluster networking cannot span providers, so cross-cluster service-to-service communication needs a consistent, encrypted data plane.

  • ✗

    To synchronize Kubernetes resources across clouds

    Why it's wrong here

    Synchronising Kubernetes resources across clusters is performed by GitOps tooling such as Argo CD or by multi-cluster management platforms, which reconcile desired state. A service mesh operates at the data plane, handling service-to-service communication, mTLS and traffic policy; it does not reconcile Kubernetes objects between clusters.

  • ✗

    To provide cloud-agnostic block storage

    Why it's wrong here

    A service mesh manages east-west traffic between workloads—mTLS, retries, observability—and does not provision block storage volumes. It is tempting because service meshes do abstract infrastructure across clusters, but cloud-agnostic persistent storage is delivered by CSI drivers or storage orchestrators such as Portworx.

  • ✗

    To provide a single ingress gateway for all clouds

    Why it's wrong here

    A single ingress gateway is provided by a load balancer or ingress controller, which route north-south traffic into each cluster; a service mesh governs east-west service-to-service traffic within and across clusters. It is tempting because meshes do offer ingress gateways, but that role is peripheral, not the multi-cloud use case.

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 →

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.