Cilium-Associate Cilium Certified AssociateCCA Questions and Answers

Technical explanation

The policy’s endpointSelector selects the ship workload in the namespace containing the CiliumNetworkPolicy , which is ns-cca . It also explicitly includes io.cilium.k8s.policy.cluster: cluster1 , confirming that the selected source endpoint belongs to cluster1.

The egress rule authorizes communication to an endpoint carrying name: base and the cluster label io.cilium.k8s.policy.cluster: cluster2 . Because the namespaced policy does not specify a different destination namespace through k8s:io.kubernetes.pod.namespace , the intended destination is the corresponding base workload in ns-cca on cluster2. Therefore, A matches the policy.

Options C and D incorrectly describe the rule as a deny rule. Cilium policy rules use an allow-list model unless an explicit egressDeny or ingressDeny section is present. The exhibit contains an ordinary egress rule, so matching traffic is authorized. Option B incorrectly places the destination in default .

Current Cilium versions require explicit cluster targeting for remote endpoints, which this policy provides through the cluster label.

Official references

Cluster Mesh Network Policy , Namespaces in Cilium Policy

Study Guide topic: Cluster Mesh labels, namespaced policies, and cross-cluster endpoint selection.

Technical explanation

Hubble obtains its visibility from Cilium’s eBPF datapath, and the Hubble Server is embedded in the Cilium agent. Hubble therefore cannot provide its normal flow-observability capabilities as a standalone installation without Cilium, eliminating B.

CNI chaining allows Cilium to coexist with a supported existing CNI. The original plugin continues to supply base connectivity and IP address management, while Cilium attaches eBPF programs to the created network devices. Those programs provide visibility, policy enforcement, and other Cilium functionality. Hubble can then be enabled on top of the chained Cilium deployment. This approach avoids an immediate, disruptive replacement of the production cluster’s networking layer and is consequently the best answer.

Options C and D could be appropriate in broader migration projects, particularly when a current CNI is incompatible with chaining or when full native-Cilium functionality is required. However, both imply substantially more workload movement or cutover activity than the stated objective of minimizing downtime.

Compatibility, chaining mode, current CNI behavior, kernel requirements, and feature limitations must still be validated before production rollout.

Official references

Cilium CNI Chaining , Hubble Internals , Troubleshooting Hubble

Study Guide topic: Hubble prerequisites, CNI chaining, and production adoption.

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

SPIRE supplies workload identities as SPIFFE Verifiable Identity Documents, including X.509 key material used for mutual authentication. SPIFFE’s identity model supports automatic issuance, rotation, and revocation, allowing short-lived certificates to be renewed without manually distributing static credentials. This makes D the correct statement.

Option A reverses the documented default. Cilium’s default SPIRE installation requires persistent-volume support. In-memory storage can be selected for laboratory environments by disabling server data storage, but that setting causes SPIRE data to be recreated if the server pod restarts. Option B also reverses the relationship between the projects: SPIFFE defines the identity standards and APIs, while SPIRE is a production-ready implementation of SPIFFE. Cilium’s mutual-authentication integration has been validated with SPIRE.

Option C overstates the operational requirement. A SPIRE server is involved, but Cilium’s Helm chart can deploy and configure the supported SPIRE server and per-node agents. Administrators may provide their own deployment, yet a completely manual installation is not mandatory.

Current documentation classifies this mutual-authentication implementation as beta and notes limitations, including incompatibility with Cluster Mesh trust domains. Those maturity constraints do not change the certificate-management behavior described in D.

Official references

Cilium Mutual Authentication .

Study Guide topic: Service Mesh.

Technical explanation

BIG TCP permits the Linux networking stack to process packets larger than the traditional approximately 64-KiB limit represented by the IP length field while the packets remain inside the host. IPv6 BIG TCP uses a temporary Hop-by-Hop header carrying the larger internal length, while IPv4 BIG TCP sets tot_len to zero and uses the socket buffer length internally. Before transmission, packets are segmented into sizes suitable for the physical network. C therefore identifies the problem BIG TCP addresses.

Option A is false because Cilium’s documentation explicitly states that BIG TCP does not require network-interface MTU changes. The larger objects exist inside the software networking stack and are segmented before appearing on the wire.

Option B reverses the intended performance effect. Larger internal GSO and GRO packets reduce repeated stack traversal, lowering CPU utilization and generally improving throughput and latency. Option D is also false: Generic Segmentation Offload and Generic Receive Offload are fundamental to BIG TCP’s operation. Cilium increases their maximum sizes when BIG TCP is enabled. The source mentions TSO, but the documented mechanism is principally described through GSO and GRO.

Official references

Cilium Performance Tuning and BIG TCP

Study Guide topic: BIG TCP, GSO/GRO, packet-length limits, and performance.

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 primarily improves Kubernetes network security through identity-aware policy enforcement across Layers 3 through 7. Standard Kubernetes NetworkPolicy resources provide Layer 3 and Layer 4 controls, while CiliumNetworkPolicy extends enforcement to application-layer rules. Policies can select workloads by labels and identity, restrict protocols and destination ports, control communication with CIDRs or entities, apply DNS/FQDN rules, and authorize supported HTTP or gRPC operations. This multi-layer enforcement is the capability described by D.

API Gateway and Gateway API configurations can contribute to controlling north-south traffic, but they are not Cilium’s primary or comprehensive security mechanism. Database encryption is implemented by database, storage, or encryption-management systems rather than being a general function of Cilium. Persistent-volume backup is similarly outside Cilium’s CNI, network-policy, and observability responsibilities.

Cilium’s identity model is especially important in dynamic Kubernetes environments. Security policy follows workload identities derived from labels instead of depending exclusively on changing pod IP addresses. At Layer 7, traffic is redirected to Envoy when protocol-aware inspection or enforcement is required, while eBPF supplies the efficient kernel datapath for lower-layer processing.

Official references

Introduction to Cilium and Hubble ; Network Policy ; Layer 7 Policies .

Study Guide topic: Network Policy.

Technical explanation

A is clearly the intended answer because its filters correspond to the displayed source namespace ( endor ), destination port ( 443 ), and verdict ( DROPPED ). However, it contains example.con , whereas the observed flow names example.com . Therefore, none of the options would literally return this exact flow if the FQDN filter is matched as written. The corrected command is:

hubble observe --to-fqdn example.com --from-namespace endor --to-port 443 --verdict DROPPED

Option B is malformed in two additional places and filters port 80 rather than 443. Option C selects the wrong FQDN and source namespace. Option D requests forwarded flows, directly contradicting the Policy denied DROPPED verdict; its wildcard also does not repair the verdict mismatch.

Hubble’s observe filters are cumulative: a returned flow must satisfy the specified destination FQDN, originating namespace, destination port, and verdict. Layer 7 visibility is enabled with a Cilium network policy containing the relevant L7 rules, which redirects selected traffic through the proxy so that application-level details can be reported.

Official references

Inspecting Network Flows with the Hubble CLI , Layer 7 Protocol Visibility

Study Guide topic: Hubble flow filtering, FQDN visibility, namespaces, ports, and verdicts.

Technical explanation

Ingress provides a comparatively simple API for exposing HTTP and HTTPS applications through host- and path-based routing. Gateway API is a broader, extensible family of resources that separates infrastructure configuration from application routing. Resources such as GatewayClass , Gateway , HTTPRoute , GRPCRoute , TLSRoute , TCPRoute , and UDPRoute model listeners, routes, protocols, ownership, and attachment relationships explicitly.

Gateway API was designed around operational roles. An infrastructure provider can manage the GatewayClass , a cluster operator can provision a Gateway , and an application team can own a route attached to that Gateway. This offers clearer delegation than the single Ingress resource and supports protocols and traffic-management functions beyond the original Ingress model.

The two APIs are not simply different names for identical functionality, so A is false. Option C is also inaccurate because Cilium’s implementations of both Ingress and Gateway API integrate with its eBPF datapath and Envoy; Ingress is not inherently an iptables-only implementation. Option D incorrectly limits Gateway API to internal routing. It can expose internet-facing applications through generated LoadBalancer or NodePort Services or through host-network listeners.

Official references

Migrating from Ingress to Gateway ; Gateway API Support .

Study Guide topic: Service Mesh.

Technical explanation

Hubble provides network and security flow observability derived from Cilium’s datapath. Its flow records include source and destination workloads, namespaces, identities, ports, protocols, forwarding verdicts, and drop reasons. Hubble can therefore identify services or workloads whose connections were rejected by network policy. The Hubble CLI supports filtering by verdict, such as --verdict DROPPED , and official examples show events labeled Policy denied DROPPED . These capabilities directly answer the question posed in option D.

Option B, which is marked as correct in the supplied bank, is not supported by the stated functionality. Hubble may expose network-layer or supported application-layer metadata, including DNS and HTTP information when Layer 7 visibility is configured, but it is not a database query profiler and cannot determine which internal SQL statement ran longest merely from ordinary Hubble flows. Similarly, CPU utilization is a workload-resource metric normally obtained through Kubernetes metrics, Prometheus, or another monitoring system. Cilium BGP configuration is examined through Cilium configuration and BGP status commands rather than inferred from Hubble network flows.

The supplied answer key should therefore be corrected from B to D.

Official references

Inspecting Network Flows with the Hubble CLI ; Hubble internals .

Study Guide topic: Network Observability.

Technical explanation

The status output shows Envoy DaemonSet: disabled (using embedded mode) . In embedded mode, Cilium starts Envoy as a separate process inside the Cilium agent pod when a feature requiring Layer 7 processing—such as an L7 network policy, protocol visibility, Ingress, or Gateway API—is used. This is precisely the behavior described in option B.

The remaining choices contradict the exhibit. The Cilium DaemonSet has a desired count of three, which ordinarily indicates three schedulable nodes running Cilium, not four. Hubble Relay: OK means the aggregation component is healthy. Hubble Relay connects to the Hubble instances associated with Cilium agents and presents a multi-node API to clients such as Hubble CLI and Hubble UI. Finally, ClusterMesh: disabled rules out the claim that the installation is currently configured for Cilium Cluster Mesh service discovery and cross-cluster load balancing.

Cilium can alternatively run Envoy through the independently life-cycled cilium-envoy DaemonSet. That is not the deployment displayed here because the DaemonSet is explicitly disabled and embedded mode is reported.

Official references

Envoy deployment modes ; Hubble internals .

Study Guide topic: Architecture.

Technical explanation

cilium config set debug true follows the supported Cilium CLI configuration syntax and sets the debug configuration key to true . The cilium config set command accepts a key/value pair and, by default, restarts the Cilium pods so that the changed configuration is applied. The Cilium configuration documentation defines debug as the setting that enables full debug mode. This increases agent logging verbosity and causes eBPF programs to emit additional visibility events for diagnostic use.

Options A, B, and D do not match documented Cilium CLI command structures. There is no cilium log level --set=debug command in the Cilium CLI hierarchy, and neither cilium logging.level=debug nor cilium logging debug is valid configuration syntax. A Helm-managed installation may also enable debugging through the chart value debug.enabled=true , but that does not make any of the alternative commands correct.

Debug mode should be enabled deliberately because it increases log volume and may generate additional datapath visibility information. After troubleshooting, operators should normally restore the previous setting to avoid unnecessary operational overhead.

The supplied answer key incorrectly identifies B. The verified answer is C.

Official references

Cilium configuration ; Cilium CLI `config set` ; Helm values .

Study Guide topic: Installation and Configuration.

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

The host entity represents the local node on which the selected Cilium endpoint resides. It also includes processes and containers using the local host network namespace. Therefore, A reproduces the official entity definition accurately.

The remote-node entity does not represent arbitrary unmanaged endpoints. It represents hosts other than the local node across the local cluster and connected clusters, including host-networked containers on those nodes. Unmanaged endpoints instead have the reserved unmanaged identity.

Option C gives the definition of the separate kube-apiserver entity, not cluster . The cluster entity is the logical collection of endpoints and reserved identities inside the local cluster, including Cilium-managed endpoints, unmanaged local endpoints, hosts, remote nodes, health, ingress, initialization, and kube-apiserver identities. Current documentation separately provides a cluster-mesh entity for endpoints in connected clusters.

Option D confuses all with world . world represents endpoints outside the cluster. all covers all identities and is not simply equivalent to the IPv4 CIDR 0.0.0.0/0 , particularly in identity-aware, node, and IPv6 contexts.

Official references

Cilium Layer 3 Policy Entities , Cilium Reserved Identities

Study Guide topic: Reserved entities and identity-based Layer 3 policies.

Technical explanation

The status output reports Operator: OK , followed by Deployment cilium-operator Desired: 1, Ready: 1/1, Available: 1/1 . This establishes that the Cilium Operator is deployed and healthy, making B the intended answer. Cilium uses Kubernetes CustomResourceDefinitions as its default mechanism for storing and propagating cluster state, while the operator performs cluster-wide duties that should be handled once centrally rather than independently on every node.

Option A is contradicted by the exhibit: both hubble-ui and hubble-relay appear as ready deployments and running containers. Option C is incorrect because the resource is explicitly identified as a Deployment ; the cilium agents, by contrast, are shown as a DaemonSet . Option D incorrectly treats the displayed desired replica count as a permanent restriction. A desired count of one describes this installation’s current configuration, not a universal maximum.

The exhibit also shows embedded Envoy mode and three healthy Cilium agent instances, but neither detail changes the operator conclusion.

Official references

Cilium Component Overview , Setting up Hubble Observability

Study Guide topic: Cilium components, Cilium Operator, CRD-backed state, and status interpretation.