Cilium-Associate Cilium Certified AssociateCCA Questions and Answers

Technical explanation

Option D uses the correct structure for permitting egress from selected endpoints to the local host entity. The endpointSelector selects endpoints whose label env equals dev . Because the intended traffic travels from those endpoints toward the host, the policy must contain an egress rule. An egress peer is expressed through toEntities , and host is the reserved entity representing the local host, including host-networked containers on that node.

Option A is invalid because fromEntities is an ingress-oriented field and cannot express an egress destination. Option B uses nodeSelector , which selects nodes rather than workload endpoints and is only valid for node-level rules in a CiliumClusterwideNetworkPolicy ; it is not valid in the displayed namespaced CiliumNetworkPolicy . It also combines ingress with toEntities , reversing the rule direction. Option C has a valid workload selector but again uses toEntities under ingress ; ingress rules describe sources through constructs such as fromEntities .

Applying option D places the selected endpoints into egress default-deny mode and then expressly permits traffic whose destination is the host entity. Other egress traffic must be allowed separately.

Official references

Policy Enforcement and Rule Basics ; Endpoint Lifecycle policy examples .

Study Guide topic: Network Policy.

Technical explanation

The manifest specifies both interface: net1 and egressIP: 10.3.4.5 in the same egressGateway configuration. These properties are mutually exclusive. Cilium ignores an Egress Gateway policy containing both, so A correctly identifies the defect.

When interface is supplied, Cilium uses the selected interface and chooses its first suitable IPv4 and IPv6 addresses as the SNAT addresses. When egressIP is supplied, that address must already be assigned to a network device on the chosen gateway node; Cilium determines the corresponding interface through a route lookup. Administrators may also omit both fields, causing Cilium to select the default-route interface and its addresses.

Option B is incorrect because matchLabels can contain multiple label key-value pairs, as the exhibit does with app: blog and component: backend . Option C is false because the egress address need not be publicly routable; private addresses are valid when routing and upstream network design support them. Option D is false because Cilium does not restrict gateway interfaces to names beginning with eth .

Official references

Cilium Egress Gateway

Study Guide topic: Egress Gateway node selection, interface selection, and SNAT addresses.

Technical explanation

The intended answer is A because API request limiting corresponds to rate limiting, which Cilium identifies as a core Layer 7 traffic-management capability. Cilium combines its eBPF datapath with Envoy for application-layer processing. The official Service Mesh documentation expressly includes rate limiting among the functions that must understand protocols such as HTTP, REST, gRPC, and WebSocket. It is therefore not merely packet-rate policing at Layer 3 or Layer 4; it can be applied with application-protocol context.

However, this question is no longer valid as a strict single-answer item. Current Cilium documentation also describes proxy-based Layer 7 load balancing as useful for gRPC and provides an Envoy-backed implementation for Kubernetes Services. Consequently, option C is also supportable under the current product documentation, although the feature is identified as beta. API authorization and fault-delay injection are not presented as equivalent first-class Cilium Service Mesh use cases in the cited feature overview.

For certification-bank purposes, retain A as the intended answer, but revise option C or qualify it to restore a unique correct choice.

Official references

Service Mesh ; Proxy Load Balancing for Kubernetes Services .

Study Guide topic: Service Mesh.

Technical explanation

The policy attaches an HTTP Layer 7 rule to port 80 but omits protocol: TCP from the associated ports entry. HTTP policy is layered on a Layer 4 TCP rule, and the documented Cilium form explicitly identifies TCP before specifying the HTTP method and path. D therefore identifies the configuration defect intended by the question.

The cross-namespace source selection is valid. The policy resides in namespace back and selects backend pods there. Its fromEndpoints selector explicitly includes k8s:io.kubernetes.pod.namespace: blog , allowing it to select matching app-frontend endpoints in that other namespace. Option A is consequently not an error.

The k8s: source prefix in k8s:app.kubernetes.io/name is also valid Cilium label syntax and identifies the Kubernetes label source, making B false. Port 80 may be used in a Cilium policy; the privileged-port restriction concerns which processes may bind low-numbered ports under operating-system permissions, not whether a network policy can reference them.

The corrected port entry should contain port: "80" together with protocol: TCP .

Official references

Cilium Layer 7 Policies , Kubernetes Constructs in Cilium Policy

Study Guide topic: Combining Layer 4 port rules with Layer 7 HTTP policies.

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

Cilium derives an endpoint’s security identity from its security-relevant labels rather than from its current IP address. When multiple endpoints possess the same relevant label set, they receive and share the same numeric security identity. This enables policies to follow an application as pods are recreated, rescheduled, or scaled across nodes.

In Kubernetes, the Cilium agent obtains workload metadata through the Kubernetes API and associates the pod’s labels with the corresponding Cilium endpoint. Identity allocation converts the relevant label set into a cluster-wide identity. Policy enforcement then matches that identity in the eBPF datapath instead of depending exclusively on short-lived pod addresses.

Option A incorrectly makes the IP address the source of identity and says that identities cannot be shared. Option B incorrectly identifies annotations as the identity foundation. Annotations may configure behavior, but Cilium’s security model is label-based. Option D is also incorrect because operators do not ordinarily assign each pod’s numeric security identity manually. Identity allocation and lifecycle management are automatic.

Official references

Cilium Terminology and Identities , Limiting Identity-Relevant Labels

Study Guide topic: Label-derived identities and identity-based policy enforcement.

Technical explanation

The intended answer is D, but the option contains a source-bank typographical error. The valid command is cilium sysdump , not cilium sysduwp . Read literally, none of the four displayed commands exactly answers the question.

The Cilium CLI’s sysdump operation gathers cluster-wide troubleshooting material, including Cilium configuration and endpoint state, agent and operator logs, Kubernetes workload information, routing and interface details, kernel messages, service state, policies, and selected eBPF-map output. This consolidated archive is the preferred diagnostic package when investigating Kubernetes networking or preparing a support report.

cilium status --verbose provides expanded health and deployment status, but it does not collect the comprehensive diagnostic archive requested. debuginfo is associated with the in-agent debug client—currently documented as cilium-dbg debuginfo —and produces useful local-agent API information; in Kubernetes environments it is already included as part of the system dump. cilium bugtool is not the current cluster-wide Cilium CLI command requested here.

For an exam-ready correction, option D should read cilium sysdump .

Official references

Cilium Troubleshooting and Sysdump

Study Guide topic: Cilium CLI troubleshooting, system dumps, and diagnostic collection.

Technical explanation

Option B correctly represents the Ingress as a Gateway and an attached HTTPRoute . The Gateway is named cilium , uses gatewayClassName: cilium , and exposes an HTTP listener on port 80. The HTTPRoute uses parentRefs with the same Gateway name, cilium , so the route attaches to the declared listener. Its two rules preserve the original routing behavior: /details with PathPrefix targets the details Service on port 9080, while / with PathPrefix targets productpage on port 9080.

Option A declares a Gateway named cilium but attaches its route to nginx-gateway . Because the parent reference does not identify the displayed Gateway, it is not equivalent. Options C and D use kind: Route ; the correct resource kind for HTTP path routing is HTTPRoute . They also contain malformed or altered backend and matching fields. Option D changes the details backend name, while option C contains incorrect route structure and path content.

Cilium’s official migration example uses the same conversion pattern: the Ingress class becomes the Gateway’s class, paths move into HTTPRoute.rules , and the route identifies its Gateway through parentRefs .

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

Official references

HTTP Migration Example .

Study Guide topic: Service Mesh.

Technical explanation

If a global Service has no healthy local endpoints matching its selector, every available backend can be remote. Cluster Mesh synchronizes remote service and endpoint information, allowing the local Cilium datapath to load-balance requests to backend pods in connected clusters. The absence of local endpoints therefore provides a direct explanation for the observed behavior.

If the local cluster were not part of the Cluster Mesh, its Cilium agents would not normally receive the remote endpoint state needed to route traffic through the global Service, so B does not explain successful remote-only selection. An affinity value of none is the default behavior and expresses no preference between local and remote endpoints. When both categories exist and are healthy, this permits load balancing across both; it does not require every connection to use remote backends.

Setting service.cilium.io/shared: "false" prevents the local Service’s backends from being shared with remote clusters. It does not instruct the local cluster to direct all requests toward remote endpoints.

A separate possible cause, not presented among the choices, would be service.cilium.io/affinity: "remote" . Among the supplied answers, however, A is the valid explanation.

Official references

Service Affinity ; Cluster Mesh .

Study Guide topic: Cluster Mesh.

Technical explanation

Remote service affinity directs a global Service to prefer healthy backend endpoints located in remote clusters. This can support maintenance or staged rollouts in which the local copy of an application is temporarily unavailable or intentionally removed from service. Requests originating in the local cluster continue through the same global Service but are forwarded to the preferred remote backends, matching the use case described by D.

Cilium configures this behavior through the service.cilium.io/affinity: "remote" annotation. The preference affects backend selection; it does not require clients to use a different Service address. If remote backends are available, they are marked as preferred. This provides operators with a controlled way to direct traffic away from the local deployment during an update.

Option A describes local affinity from the perspective of the cluster containing the client, not remote affinity. Option B incorrectly introduces the Egress Gateway, which provides controlled source addresses and routing for outbound traffic rather than Cluster Mesh global-Service affinity. Option C describes the normal none affinity behavior, under which Cilium has no local-or-remote preference and can load-balance across both categories.

Remote affinity therefore enables temporary cross-cluster continuity while local application instances are updated or otherwise unavailable.

Official references

Cluster Mesh Service Affinity .

Study Guide topic: Cluster Mesh.

Technical explanation

The question’s “12 Announcements” wording is a source transcription error for L2 Announcements . This feature makes Kubernetes Services visible and reachable to clients on the local Layer 2 network, particularly in on-premises, office, campus, or bare-metal environments that do not use BGP-based service advertisement.

Cilium responds to ARP requests for IPv4 Service addresses and NDP requests for IPv6 addresses. A selected node advertises the LoadBalancer IP or ExternalIP using its MAC address and receives traffic for that virtual IP. Cilium then applies its service load-balancing functionality to forward the connection to an appropriate backend. Leadership is coordinated so that one node advertises a given Service at a time, and the virtual IP can move to another eligible node after failure.

The feature is not intended to provide general Layer 2 multicast, making A incorrect. DNS service discovery is handled through Kubernetes DNS and is independent of L2 announcements, eliminating C. It also does not define Layer 2 security policies, so D is incorrect.

Thus, the purpose is external Service reachability on the local area network, exactly as described by B.

Official references

L2 Announcements .

Study Guide topic: BGP and External Networking.

Technical explanation

Cilium can implement Layer 3 and Layer 4 forwarding exclusively through its eBPF datapath. IP, TCP, and UDP traffic can be routed, load-balanced, filtered, and redirected through eBPF programs attached to Linux networking hooks. These operations depend on network-layer addresses, protocols, ports, identities, and connection state; they do not require application-protocol parsing by a userspace proxy.

Application-layer operations are different. Cilium’s official Service Mesh architecture uses a proxy such as Envoy to parse HTTP, gRPC, and DNS when Layer 7 policy, observability, or traffic management requires understanding individual requests. The eBPF datapath transparently redirects selected traffic to the node-local proxy and retains identity context, while Envoy performs the protocol-aware operation.

Kafka parsing is also an application-layer activity rather than ordinary Layer 3 or Layer 4 forwarding. Moreover, current Cilium releases removed the former Envoy Go extension mechanism used for Kafka and generic proxylib rules, further reinforcing that it is not an eBPF-only forwarding case.

Therefore, D accurately identifies the scenario in which the Service Mesh datapath can remain entirely in the kernel without requiring Envoy.

Official references

Cilium Service Mesh ; eBPF Datapath Introduction .

Study Guide topic: Service Mesh.

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

Layer 7 protocol visibility redirects traffic matching the relevant L7 rules to Cilium’s node-local proxy, which is Envoy. Envoy parses supported application protocols and supplies the resulting request or response metadata to Cilium’s observability pipeline. Therefore, C correctly identifies the architectural consequence of enabling this visibility.

The feature requires L7 proxy support and an appropriate CiliumNetworkPolicy containing Layer 7 rules. A standard Kubernetes NetworkPolicy is limited to Layer 3 and Layer 4 concepts and cannot express Cilium’s HTTP, DNS, or generic application-protocol rules, so B is incorrect.

A is also incorrect. DNS policy and visibility are commonly applied to pod egress queries, and Cilium’s model is not restricted to ingress-only DNS visibility. D overstates protocol coverage. Cilium supports defined L7 parsers and policy types—most prominently HTTP, DNS, Kafka, and supported generic Envoy-based protocols—but it does not promise arbitrary visibility for every application protocol. SSH, Telnet, and FTP cannot simply be assumed to receive native semantic parsing.

An operational caveat is that L7 visibility rules also affect policy enforcement: they are not merely passive packet logging instructions.

Official references

Layer 7 Protocol Visibility , Cilium Envoy

Study Guide topic: L7 proxy redirection, CiliumNetworkPolicy, protocol parsing, and Hubble visibility.

Technical explanation

The Hubble Server is embedded in each Cilium agent and consumes the eBPF-derived visibility data produced on that node. It exposes gRPC services through which clients can retrieve flow events, node and namespace information, server status, and related observability data. Embedding the server in the agent enables high-performance collection with comparatively low overhead.

Hubble Relay has a different role. It is a standalone component that discovers and connects to the Hubble Server instances running across the cluster. Relay aggregates their individual APIs to provide multi-node or cluster-wide visibility to clients such as the Hubble CLI and Hubble UI. It is therefore not the component embedded in the agent.

The Cilium CNI plugin is invoked when Kubernetes creates or removes pods and asks the local agent to configure their networking and datapath. The Cilium Operator performs cluster-wide management duties such as selected IPAM and shared-state operations. Neither component is responsible for exposing eBPF flow visibility.

This server–relay distinction is central to understanding Hubble’s distributed architecture: Server provides node-local visibility, while Relay combines multiple servers into a cluster-wide view.

Official references

Hubble Internals , Cilium Component Overview

Study Guide topic: Hubble Server, Hubble Relay, and distributed flow observability.