
CCA (Cilium Certified Associate) is the Linux Foundation and CNCF certification for Cilium, the eBPF-based networking, security and observability layer used in many Kubernetes clusters, including the default or optional networking on several managed Kubernetes services. The exam checks that you understand how Cilium routes pod traffic, enforces identity-based network policies, gives visibility with Hubble, connects clusters with Cluster Mesh, and replaces parts of a service mesh without sidecars. It suits DevOps, platform and network engineers who already know Kubernetes basics.
This guide follows the official Linux Foundation exam page: exam facts, the eight domains with weights, the ideas behind eBPF and identity-based policy, the commands to know, a 3-week plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, multiple choice |
| Duration | 90 minutes |
| Level | Beginner; no prerequisites (Kubernetes and networking basics recommended: OSI layers, TCP, UDP, DNS, HTTP) |
| Price | US$250 exam only; US$495 with an annual training subscription |
| Validity | 2 years |
| Eligibility | 12 months to schedule and take the exam; a retake is included |
Read the official CCA exam page and the Cilium documentation.
Domains and weights
| Domain | Weight | Competencies (from the Linux Foundation) |
|---|---|---|
| Architecture | 20% | Cilium's role in Kubernetes; architecture and component roles; IP address management (IPAM); datapath models |
| Network Policy | 18% | Reading policy intent; identity-based security; enforcement modes; rule structure; Kubernetes NetworkPolicy vs CiliumNetworkPolicy |
| Service Mesh | 16% | Ingress and Gateway API routing; mesh use cases; why Gateway API improves on Ingress; encryption in transit; sidecar vs sidecarless |
| Network Observability | 10% | Hubble capabilities; Layer 7 visibility; Hubble CLI and UI |
| Installation and Configuration | 10% | Installing with the Cilium CLI; querying and changing configuration; connectivity tests; status |
| Cluster Mesh | 10% | Why connect clusters; service discovery and load balancing across clusters |
| eBPF | 10% | eBPF's role in Cilium; benefits; eBPF-based vs iptables-based networking |
| BGP and External Networking | 6% | Egress requirements; connecting Cilium clusters to external networks |
Key ideas in plain words
- eBPF: small, verified programs that run inside the Linux kernel. Cilium attaches them to network hooks, so packets are handled in the kernel without long iptables chains. That scales better as the number of services grows and allows kube-proxy replacement.
- Components: the Cilium agent runs on every node (a DaemonSet) and loads eBPF programs; the Cilium operator handles cluster-wide tasks such as IPAM; Hubble collects flow data; the CLI installs and checks everything.
- Identity-based policy: Cilium gives each set of pod labels a numeric security identity and enforces policy on identities, not IP addresses, which change all the time in Kubernetes.
- Enforcement modes: default (an endpoint becomes default-deny only once a policy selects it), always (default-deny everywhere) and never.
- Datapath: encapsulation (VXLAN or Geneve overlay) or native routing, where the underlying network routes pod IPs directly.
- Encryption in transit: transparent encryption with WireGuard or IPsec between nodes, without changing applications.
A Cilium network policy
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
name: allow-frontend-get-orders
namespace: shop
spec:
endpointSelector:
matchLabels: { app: orders }
ingress:
- fromEndpoints:
- matchLabels: { app: frontend }
toPorts:
- ports: [ { port: "8080", protocol: TCP } ]
rules:
http:
- method: GET
path: "/orders.*"
A plain Kubernetes NetworkPolicy can't do the HTTP method and path rule; that L7 filtering is a CiliumNetworkPolicy feature. Also know toFQDNs (allow egress by DNS name) and CiliumClusterwideNetworkPolicy.
Commands to know
cilium install # install into the current cluster
cilium status --wait # health of agents and operator
cilium connectivity test # end-to-end tests
cilium config view # current configuration
cilium hubble enable --ui # turn on Hubble and its UI
hubble observe --namespace shop --verdict DROPPED
hubble observe --protocol http
cilium clustermesh enable
cilium clustermesh connect --destination-context cluster2
3-week study plan
| Week | Focus | Lab (kind or minikube) |
|---|---|---|
| 1 | eBPF basics, architecture, IPAM, datapath modes, installation and configuration | Install Cilium with kube-proxy replacement; run the connectivity test |
| 2 | Network policy (L3/L4/L7, DNS-based egress, enforcement modes) and Hubble | Deploy a demo app; write deny-by-default plus allow rules; watch drops in Hubble |
| 3 | Gateway API, encryption, sidecarless mesh, Cluster Mesh, BGP and egress; review | Expose an app with Gateway API; turn on WireGuard; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. What is eBPF?
A Linux kernel technology for running small, verified programs inside the kernel, safely and without kernel modules.
2. Why can eBPF networking scale better than iptables?
It uses efficient hash-map lookups instead of walking long sequential rule chains.
3. Which Cilium component runs on every node?
The Cilium agent.
4. Which component handles cluster-wide tasks such as IPAM allocation?
The Cilium operator.
5. On what does Cilium base its policy decisions?
Security identities derived from pod labels, not IP addresses.
6. In default enforcement mode, when does a pod start denying traffic?
When at least one policy selects it; then only allowed traffic passes in that direction.
7. Which policy type can allow only HTTP GET on /orders?
A CiliumNetworkPolicy with L7 HTTP rules.
8. How do you allow pods to reach api.example.com only?
An egress rule with toFQDNs (with DNS visibility enabled).
9. Which tool shows dropped flows and their reasons?
Hubble (hubble observe or the Hubble UI).
10. Which command runs Cilium's built-in end-to-end tests?
cilium connectivity test.
11. Name the two datapath modes.
Encapsulation (VXLAN or Geneve) and native routing.
12. Name two ways Cilium can encrypt traffic between nodes.
WireGuard and IPsec.
13. What advantage does a sidecarless mesh have?
No proxy container in every pod, so less resource use and simpler operations.
14. What does Cluster Mesh provide?
Pod connectivity, shared services and load balancing across multiple clusters.
15. Why would you run BGP with Cilium?
To advertise pod or service IPs to physical routers so external networks can reach them.
After CCA
- Pair it with Istio ICA, KCSA and Kyverno KCA.
- Strengthen networking basics with Network+ or CCNA.
- Learn it hands-on in our Kubernetes course; see live DevOps and platform jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches Kubernetes, cloud networking and DevSecOps with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the CCA exam?
The Linux Foundation and CNCF Cilium Certified Associate: a beginner online, proctored, multiple-choice exam on Cilium networking, security and observability.
How long is the CCA exam?
90 minutes.
Which CCA domain has the most weight?
Architecture at 20%, followed by Network Policy at 18%.
Does CCA have prerequisites?
No, but Kubernetes and basic networking knowledge (OSI layers, TCP, UDP, DNS, HTTP) are recommended.
How much does CCA cost?
US$250 for the exam only, or US$495 with an annual training subscription.
How long is CCA valid?
2 years.



