← CCA hub

CCA — Cluster Mesh

10% of the CCA exam. Sample questions below; the full library has 12 questions tagged to this domain.

Sample questions on Cluster Mesh

Cluster Mesh

Q1. In a ClusterMesh, how is load balancing typically distributed across multiple clusters for a global service?

Reveal answer and explanations
  1. A Cilium directs all traffic to a single designated primary cluster

    Incorrect. Multi-cluster distribution is the whole point of global services.

  2. B Requests go to the geographically nearest cluster

    Incorrect. Proximity is not the default behavior.

  3. C Load is evenly distributed across all clusters hosting the service

    Correct. Cilium distributes load across healthy service instances in all clusters.

  4. D Requests are always served by the local cluster first, then failover to remote clusters

    Incorrect. Distribution is not strictly local-first.

Cluster Mesh

Q2. What is the difference between a 'local service' and a 'global service' in ClusterMesh?

Reveal answer and explanations
  1. A Local services are accessible only within their cluster; global services are accessible from all clusters in the mesh

    Correct. Local services exist within one cluster; global services are shared across the mesh.

  2. B Global services require higher latency; local services are optimized for speed

    Incorrect. Latency is not the distinguishing factor.

  3. C They are the same; the terms are interchangeable

    Incorrect. Local and global services have different ClusterMesh visibility scopes; they are not interchangeable.

  4. D Local services use DNS; global services use IP addresses

    Incorrect. ClusterMesh can expose both local and global services through DNS; the distinction is service visibility across clusters.

Cluster Mesh

Q3. When troubleshooting ClusterMesh connectivity, which of the following tools is most useful for verifying cluster connectivity?

Reveal answer and explanations
  1. A kubectl logs with cilium-agent errors only

    Incorrect. Logs are useful but incomplete.

  2. B cilium clustermesh status command to verify cross-cluster connections

    Correct. 'cilium clustermesh status' shows mesh connectivity and health.

  3. C ping between nodes in different clusters

    Incorrect. Node-level ping doesn't test ClusterMesh state.

  4. D Kubernetes Service DNS from remote clusters

    Incorrect. DNS is a symptom, not diagnostic.

Cluster Mesh

Q4. In a ClusterMesh, what happens when a global service instance becomes unavailable in one cluster?

Reveal answer and explanations
  1. A All pods must re-resolve DNS to discover the service

    Incorrect. DNS doesn't change; health checking is dynamic.

  2. B Traffic is automatically rerouted to remaining healthy instances in other clusters

    Correct. Cilium's load balancing removes unhealthy endpoints and reroutes to healthy ones.

  3. C The entire global service becomes unavailable

    Incorrect. Other instances remain available.

  4. D The unavailable cluster is removed from the mesh permanently

    Incorrect. Temporary unavailability doesn't remove a cluster.

Cluster Mesh

Q5. What is the primary purpose of ClusterMesh in Cilium?

Reveal answer and explanations
  1. A Provides backup redundancy within a single cluster

    Incorrect. Redundancy is within-cluster; ClusterMesh is cross-cluster.

  2. B Replaces multi-cluster networking with single-cluster abstraction

    Incorrect. It enables multi-cluster networking, not eliminates it.

  3. C Enables pod-to-pod communication and service discovery across multiple Kubernetes clusters

    Correct. ClusterMesh allows transparent pod communication and shared services across clusters.

  4. D Manages load balancing for external traffic only

    Incorrect. ClusterMesh handles pod-to-pod traffic, not just external.

Drill Cluster Mesh with the full bankDomain Drill mode targets your weak areas — paid feature

How this domain is tested

Cluster Mesh accounts for 10% of the CCA exam. Expect questions that test recall of terminology and the ability to read short scenarios — not deep configuration. Use the sample questions above as difficulty calibration; if any feel hard, the rest of our 12-question domain bank will close those gaps.