Cilium-Associate Exam Dumps - Cilium Certified AssociateCCA

Technical explanation

Cilium derives a workload’s security identity from its security-relevant labels. Network policies then refer to workload characteristics such as application, role, environment, namespace, or service account rather than depending exclusively on transient pod IP addresses. The identity is associated with traffic in the Cilium datapath and validated when policy is enforced. This makes B the accurate description.

The identity is not limited to a single pod. Endpoints that have the same set of identity-relevant labels can share the same numeric security identity, including endpoints located on different cluster nodes. This reduces policy-map growth and allows policy to scale with logical application groups rather than with the number of pod addresses. Namespace information is normally among the labels used to derive identity, but that does not make an identity inherently “tied to a single namespace” as option A states.

Options C and D invert Cilium’s design. IP addresses remain necessary for packet delivery, but they are not the primary security identifier for Cilium-managed workloads. Pods can be recreated and assigned new addresses while retaining the same relevant labels and therefore the same security intent. Decoupling identity from addressing is precisely what improves scalability and operational stability.

Official references

Cilium Terminology and Identity ; Introduction to Cilium and Hubble .

Study Guide topic: Architecture.

Technical explanation

In cluster-scope IPAM, the Cilium Operator allocates a PodCIDR to each node from the configured cluster-wide address pool. It records those allocations in each node’s CiliumNode custom resource, specifically under spec.ipam.podCIDRs . The Cilium agent waits for this allocation during startup and then performs host-local allocation of individual pod addresses from the CIDR assigned to its node.

This division of responsibility explains why C is correct. The agent consumes its assigned range and allocates endpoint addresses locally, but it does not independently choose the cluster-wide per-node PodCIDR. The Operator coordinates those ranges to prevent nodes from receiving overlapping allocations.

Options A and D describe Kubernetes host-scope IPAM rather than Cilium cluster-scope IPAM. In Kubernetes host-scope mode, the Kubernetes controller manager assigns PodCIDRs and exposes them through spec.podCIDR or spec.podCIDRs in the standard Kubernetes Node resource. Cluster-scope mode is specifically useful when Kubernetes is not configured to perform that allocation or when Cilium should control the cluster address pool.

Therefore, the managing component and resource are the Cilium Operator and CiliumNode , respectively.

Official references

Cluster-Pool IPAM ; Cluster Scope IPAM .

Study Guide topic: Installation and Configuration.

Technical explanation

Cilium uses Envoy as its userspace Layer 7 proxy. When a Cilium policy contains HTTP or another supported application-layer rule, Cilium’s eBPF datapath identifies matching traffic and redirects it to a node-local Envoy instance. Envoy evaluates the application-layer attributes—such as HTTP method, path, or headers—against the generated policy configuration and then forwards or rejects the request.

The proxy can operate in embedded mode as a separate process inside the Cilium agent pod or as the independently life-cycled cilium-envoy DaemonSet. Both deployment forms use Cilium’s optimized Envoy distribution and custom policy-enforcement filters. Communication between the agent and Envoy uses local UNIX-domain sockets for configuration, access logs, and administrative operations.

HAProxy is a capable general-purpose load balancer, but it is not Cilium’s L7 policy proxy. Squid primarily serves forward and caching proxy use cases. linkerd2-proxy belongs to the Linkerd service mesh and is not used by Cilium for network-policy enforcement. Consequently, only D identifies the proxy integrated into Cilium’s L7 datapath.

Official references

Cilium Envoy , Cilium eBPF Datapath Introduction

Study Guide topic: Envoy proxy integration and Layer 7 policy enforcement.

Technical explanation

Kubernetes host-scope IPAM can be used with both Cilium tunnel routing and native direct routing. The IPAM mechanism determines how each node receives and locally allocates pod addresses; it does not inherently require a particular packet-forwarding model. The current IPAM feature matrix explicitly marks both tunnel routing and direct routing as supported for Kubernetes host-scope mode.

In this mode, Kubernetes allocates a PodCIDR to each node and publishes it through the standard v1.Node resource, normally in spec.podCIDR or spec.podCIDRs . The Cilium agent waits for the relevant range and allocates individual pod addresses from that node-specific CIDR. The correct configuration is ipam: kubernetes or the Helm equivalent ipam.mode=kubernetes , not ipam: crd ; therefore, C is false.

The documented feature matrix does not provide multiple CIDRs per cluster or multiple CIDRs per node for this mode, eliminating A and B. Multi-pool IPAM is the Cilium mode designed for allocating per-node CIDRs from multiple configurable pools.

Because Kubernetes host-scope IPAM supports either overlay tunneling or direct routing while the other statements contradict its capabilities or configuration, D is correct.

Official references

IP Address Management ; Kubernetes Host Scope .

Study Guide topic: Installation and Configuration.

Technical explanation

Every cluster participating in a Cilium Cluster Mesh must have a unique cluster name and numeric cluster ID. The numeric ID becomes part of Cluster Mesh security identities and allows Cilium to distinguish identities originating in different clusters. Reusing an ID would create ambiguity in endpoint identity, policy enforcement, and synchronized service information. Current documentation permits IDs from 1 through 255 under the default scaling configuration.

Geographical colocation is not required. Cluster Mesh is specifically designed to extend connectivity, policy, service discovery, and load balancing across clusters that may reside in different regions, clouds, or premises, provided the documented network-connectivity requirements are satisfied. The clusters also do not need to use an identical Kubernetes distribution or exact Kubernetes version.

Option C is unnecessarily strict. Current Cilium documentation permits connected clusters to differ by no more than one minor Cilium release; exact version equality is not mandatory. Other prerequisites include unique and non-conflicting PodCIDRs, compatible datapath modes, node connectivity, and appropriate inter-cluster communication.

The supplied bank incorrectly marks A. The verified answer is D.

Official references

Setting up Cluster Mesh .

Study Guide topic: Cluster Mesh.

Technical explanation

Kubernetes kube-proxy conventionally implements Service translation and load balancing through either iptables or IPVS. With Cilium’s kube-proxy replacement enabled, eBPF programs and maps perform Kubernetes Service handling directly in the kernel, including ClusterIP, NodePort, LoadBalancer, ExternalIP, and related service translation functions. C is therefore correct.

The replacement can operate at socket hooks and packet-processing hooks. Service and backend information is stored in eBPF maps, allowing the datapath to select backends and perform address translation without traversing the kube-proxy-generated iptables or IPVS rules normally used for Kubernetes Services.

BGP is not replaced. Cilium’s BGP Control Plane is a separate feature used to advertise routes and service addresses to external routers. Routing itself is also not eliminated; Cilium can implement and accelerate routing decisions with eBPF, but packets still require a valid forwarding model. firewalld is a host firewall-management service and is not the underlying Kubernetes Service implementation replaced by kube-proxy replacement.

Relevant installations must satisfy the kernel and device requirements for Cilium’s eBPF service load-balancer functionality.

Official references

Kubernetes Without kube-proxy

Study Guide topic: kube-proxy replacement, eBPF service maps, iptables, and IPVS.

Technical explanation

Masquerading performs source network address translation for qualifying traffic that leaves the cluster. Because pod addresses are often private and not routable by the external network, Cilium replaces the pod’s source address with an address belonging to the egress node. Return traffic can then reach that node, which reverses the translation and delivers the response to the originating pod. B correctly summarizes this behavior.

Masquerading is a form of SNAT, not DNAT. DNAT modifies the destination address, commonly to direct incoming traffic toward another endpoint, so C is incorrect.

Cilium documents its eBPF-based masquerading implementation as the more efficient implementation. The iptables version is the legacy alternative, making A false. Conversely, eBPF masquerading depends on appropriate kernel eBPF capabilities and Cilium’s BPF NodePort functionality. It cannot be assumed to work on every kernel version, so D is false. The legacy iptables implementation is the mode documented as broadly working across kernel versions.

Cilium can exclude natively routable CIDRs from masquerading, and administrators may configure separate IPv4 and IPv6 masquerading behavior.

Official references

Cilium Masquerading , Cilium System Requirements

Study Guide topic: SNAT, native-routing exclusions, and eBPF versus iptables masquerading.

Technical explanation

The official IPAM documentation expressly states that the safest way to change IPAM mode is to install a fresh Kubernetes cluster using the required new IPAM configuration. A live cluster already contains allocated workload addresses, node routing state, Cilium endpoint state, service state, and potentially cloud-provider resources that depend on the active allocator. Replacing the allocator in place can invalidate these assumptions and cause persistent connectivity disruption rather than merely a short agent restart.

Updating a Kubernetes Node object does not generally convert Cilium’s IPAM mode. The responsible resource and allocation behavior depend on the selected mode: Kubernetes host-scope IPAM, cluster-pool IPAM, multi-pool IPAM, CRD-backed modes, and cloud-specific allocators manage address information differently. Restarting agents after changing a configuration value likewise does not constitute a safe migration plan, because existing endpoints and routes may retain state created under the former allocator.

Cilium advises against changing the IPAM mode of an existing cluster unless a specifically documented migration procedure applies. The currently documented exception is migration from cluster-pool IPAM to multi-pool IPAM. As the question provides no such constrained scenario, D is the unambiguously safest answer.

Official references

IP Address Management .

Study Guide topic: Installation and Configuration.