Linux Foundation Updated Cilium-Associate Exam Questions and Answers by leonora

Technical explanation

Hubble UI and Hubble CLI are Cilium’s integrated interfaces for examining workload network flows. Hubble records source and destination identities, namespaces, workloads, addresses, ports, forwarding verdicts, and drop reasons. When Layer 7 visibility is configured, its flow output can also contain application-level information such as HTTP methods, URLs, response codes, latency, and DNS queries. Filters can narrow the results by source workload, namespace, destination, protocol, port, or verdict, making Hubble appropriate for investigating egress behavior.

Hubble CLI provides detailed event-oriented inspection, while Hubble UI presents flows and service dependencies graphically. Hubble Relay aggregates the per-node Hubble APIs so these clients can obtain cluster-wide visibility.

Load balancing directs traffic but is not an observability interface. Kubernetes NetworkPolicy expresses permitted communications but does not by itself display application-level flow records. Fluentd and Grafana are external logging and visualization components and would violate the requirement to avoid additional tooling.

Layer 7 information requires supported traffic to be redirected through Cilium’s L7 proxy. Hubble then exposes the resulting application-layer flow events through the built-in CLI or UI, making D the complete answer.

Official references

Network Observability with Hubble ; Inspecting Network Flows .

Study Guide topic: Network Observability.

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

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.