Question 1
- A.OpenVPN
- B.IPsec
- C.SSL
- D.SSH tunneling
Correct answer: B
By Ibrahim Yesilay · Published · Updated
Here are 20 free CCA sample questions with answers, taken from the GoldenKube question bank and grouped by exam domain. Every question has the correct answer marked and a written explanation, so you can check what you know and see why the wrong options fail. Cilium Certified Associate is a multiple-choice exam; this set is independent practice and not affiliated with the Linux Foundation.
Work through the 20 CCA sample questions in one sitting without looking anything up. For each question, decide on an answer first, then open the answer and read the explanation, including when you were right, because a correct guess and a correct line of reasoning look identical until the exam rewords the question. Mark every question as right, wrong or guessed, and count a guess as wrong when you score yourself. Give the set about 30 minutes, which is the average time per question on the real exam multiplied by twenty. The aim is to find out which exam domains are already solid and which ones need study before you buy the exam.
The official exam format is 60 questions in 90 minutes, with a passing score of 75%, according to the Linux Foundation documentation checked on 2026-10-23.
With JavaScript enabled, each answer starts collapsed behind a Show answer button so you can test yourself. Without JavaScript, and for any crawler or screen reader that reads the raw page, every answer and explanation is already visible below its question.
These questions were written for GoldenKube practice. They are not copied from the real exam, and nothing on this page tells you what the real exam will ask.
Question 1
Correct answer: B
Question 2
Correct answer: C
Question 3
Correct answer: C
Question 4
Correct answer: E
Question 5
Correct answer: C
Question 6
Correct answer: B
Question 7
Correct answer: A
Question 8
toDNStoFQDNtoDomainstoHostnamesCorrect answer: B
toFQDN field in a CiliumNetworkPolicy allows restricting traffic based on specific DNS names. This enables policies based on domain names rather than IP addresses, which is particularly useful for external services with changing IPs.Question 9
apiVersion: gateway.networking.k8s.io/v1beta1
kind: Gateway
metadata:
name: example-gateway
spec:
gatewayClassName: cilium
listeners:
- name: http
protocol: HTTP
port: 80
allowedRoutes:
namespaces:
from: SameapiVersion: gateway.networking.k8s.io/v1beta1
kind: Gateway
metadata:
name: example-gateway
spec:
className: cilium
listeners:
- name: http
protocol: HTTP
port: 80
routes:
namespaces:
from: SameapiVersion: gateway.networking.k8s.io/v1beta1
kind: Gateway
metadata:
name: example-gateway
spec:
gatewayClassName: cilium
ports:
- name: http
protocol: HTTP
number: 80
routes:
namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: defaultapiVersion: gateway.networking.k8s.io/v1beta1
kind: GatewayClass
metadata:
name: example-gateway
spec:
controllerName: io.cilium/gateway-controller
listeners:
- name: http
protocol: HTTP
port: 80Correct answer: A
gatewayClassName, listeners with appropriate protocol and port, and allowedRoutes to specify which routes can attach to this gateway.Question 10
cilium status --ingresskubectl get ingresscontrollers -n kube-systemcilium ingress listkubectl get pods -n kube-system -l k8s-app=cilium -o jsonpath='{.items[0].status.conditions}'Correct answer: D
Question 11
Correct answer: B
Question 12
hubble observe --http-status 404hubble observe --type http --http-status 404hubble observe --protocol http --status-code 404hubble observe --filter "http.status == 404"Correct answer: B
Question 13
kubectl exec -n kube-system cilium-xxxx -- cilium monitorcilium hubble uihubble observe --followkubectl logs -n kube-system hubble-xxxCorrect answer: C
Question 14
cilium upgrade --version 1.13.0helm upgrade cilium cilium/cilium --version 1.13.0kubectl patch cilium -n kube-system --type merge -p '{"version":"1.13.0"}'cilium update 1.13.0Correct answer: A
Question 15
cilium-preflight-checkcilium-system-validatorcilium-kernel-checkcilium-sysdumpCorrect answer: A
cilium-preflight-check tool can be used to validate Cilium and eBPF requirements on a node before installation. It verifies kernel version, required features, and other prerequisites to ensure Cilium will function correctly on the node.Question 16
Correct answer: A
Question 17
cilium.io/global: "true"clustermesh.cilium.io/global-service: "true"io.cilium/global-service: "true"io.cilium/shared-service: "true"Correct answer: C
Question 18
Correct answer: B
Question 19
Correct answer: A
Question 20
Correct answer: B
The Linux Foundation lists a passing score of 75% for CCA. On a set of 20 questions that is 15 correct. Reaching 15 here is a useful signal and not a prediction: 20 questions is a small sample, and the real exam covers every domain in its published weights. Use the table below to decide what to do next. Count only the questions you answered correctly without help, and be strict about it: a question you got right for the wrong reason belongs in the missed pile. Then repeat the exercise a few days later with a different set from the full bank so that you are measuring understanding and not memory of these specific questions.
Count your misses per domain, using the headings above. One missed question in a domain is noise; three misses in one domain is a study plan. The practice mode on GoldenKube does this sorting for you by sending you back to the domains where you are weakest.
| Correct out of 20 | What it suggests | What to do next |
|---|---|---|
| 18 to 20 | The basics are solid in the domains sampled. | Move to harder mixed practice and check the domains this set did not cover. |
| 15 to 17 | Close to the benchmark, with some gaps. | Review every missed explanation, then practise the domains where you missed questions. |
| 11 to 14 | Several domains need real study. | Read the official curriculum for those domains, then return to practice. |
| 0 to 10 | You are early in your preparation. | Start from the curriculum and the project documentation, then retry this set. |
Architecture covers how Cilium is put together and why it works the way it does. Expect the agent that runs on every node, the operator, the CNI plugin, the datapath, identity-based networking where security identities replace IP addresses, and how Cilium relates to kube-proxy and to the rest of the cluster. Questions ask which component performs a task or why identity-based policy scales better than address-based rules. A common trap is attributing cluster-wide tasks to the per-node agent when they belong to the operator, or the reverse, so learn the split of responsibilities clearly. Reading a description of a traffic flow and naming each component that touches it is the usual shape of the question.
Draw the components on one node and one control-plane view, and mark where state is stored and where policy is enforced. Architecture questions are lookups in that drawing.
Network Policy covers how Cilium decides what traffic is allowed. Expect Kubernetes NetworkPolicy and the Cilium-specific policy resources, selection by identity and labels, rules at layers 3, 4 and 7, DNS-based and entity-based rules, default-deny behaviour and the policy enforcement modes. Questions give a policy and ask whether a flow is allowed, or ask for the rule that achieves a goal. The traps are default-deny semantics, where selecting a workload for ingress changes what is allowed for it, and the difference between a layer 4 port rule and a layer 7 rule that inspects the request. Remember that policy is evaluated per direction, so check ingress and egress separately before deciding that a connection works.
Work through five small policies and decide for each flow whether it is allowed, then check your reasoning against the explanation. Policy evaluation is a skill that improves with repetition.
Service Mesh covers what Cilium offers for service-to-service traffic. Expect ingress and the Gateway API, mutual authentication between workloads, traffic management such as routing and load balancing, the role of Envoy in layer 7 handling, and how Cilium's approach differs from a sidecar-based mesh. Questions ask which feature provides which capability and how traffic flows through the components. The trap is assuming that every mesh feature needs a sidecar in each Pod, when the point of the Cilium design is to avoid that, so be ready to explain where the proxy runs. Questions in this area usually ask where a capability is implemented, so pay attention to whether the answer involves the node agent or a proxy.
Compare a sidecar mesh with the Cilium approach in three bullet points: where the proxy runs, what it costs, and what it can see. Those three points cover most comparisons.
Network Observability covers seeing what is happening in the network. Expect Hubble, its relay, command line client and user interface, flow records with identities and verdicts, metrics exported for monitoring, and how flow data helps debug a dropped connection or verify a policy. Questions ask which tool shows a given piece of information or how to find out why traffic was denied. A common trap is treating Hubble as a separate product, when it is built on the same datapath data, so it can show policy verdicts that ordinary packet captures cannot attribute to a rule. The exam tends to describe a symptom and ask which view reveals its cause, so link each symptom to the data that exposes it.
For three failure stories, such as a blocked connection, a DNS failure and a misrouted request, write which Hubble view you would open first and what you expect to see.
Installation and Configuration covers getting Cilium running and tuning it. Expect installing with the command line tool or Helm, choosing an IP address management mode, enabling features through configuration, checking status and connectivity, and upgrading safely. Questions ask which command or setting does a task, or what to check when an installation looks unhealthy. The trap is mixing the configuration surface: some options live in Helm values and the ConfigMap, others in the CLI flags used during installation. Knowing the verification steps that follow an installation is as valuable as knowing the installation steps. Pay attention to which options can be changed after installation and which require a reinstall or a careful upgrade.
Go through an install, a status check and a connectivity test in order, noting which command prints which result. The exam asks about each step, usually in a short scenario.
Cluster Mesh covers connecting several Kubernetes clusters with Cilium. Expect the requirements for connecting clusters such as unique cluster names and identifiers and non-overlapping address ranges, the API server that shares state between clusters, global services and load balancing across clusters, and policy that spans clusters. Questions ask what must be true before clusters can be joined or how a global service behaves. The common trap is overlooking the preconditions, since an overlapping address range or a duplicated cluster identifier is a typical reason a mesh fails to form. Pay attention to which behaviours depend on shared state across the clusters and which stay local to each cluster, because the questions often separate the two.
Make a short checklist of prerequisites and the symptom each missing item causes. Troubleshooting questions in this domain nearly always reduce to one item on that list.
eBPF covers the kernel technology underneath Cilium. Expect what eBPF is, how programs are loaded and checked by the verifier, attachment points in the networking stack, maps that share state between kernel and user space, and why running in the kernel gives performance and visibility advantages. Questions are conceptual and ask what eBPF makes possible or why Cilium uses it. The trap is treating eBPF as only a networking feature, when it is a general mechanism that Cilium applies to networking, observability and security, so the exam may ask about benefits that go beyond packet forwarding. Expect short conceptual questions where one option overstates what the kernel technology does by itself, so favour the careful statement over the dramatic one.
Explain eBPF in four sentences to an imaginary colleague: what runs, where it runs, who checks it and how it talks to user space. If the explanation holds together, the questions will too.
BGP and External Networking covers connecting a cluster to the networks outside it. Expect the BGP control plane in Cilium, advertising Pod address ranges and service addresses to routers, peering configuration, load balancer address handling, and egress controls for traffic leaving the cluster. Questions ask what is advertised, to whom and why. The trap is mixing the direction of information: BGP here lets the cluster announce its own routes to the network so that external clients can reach services, which differs from the cluster learning every external route. The domain is small but its terms are distinct from the rest of the exam.
Learn the handful of BGP terms the domain uses, such as peer, advertisement and autonomous system, and attach each to one sentence about what it does in a cluster.
A set of 20 questions is a screening test, not a measurement. With only a few questions per domain, one lucky guess or one unlucky wording moves your result by five percentage points, and a domain with only two questions behind it says almost nothing about that domain's true strength. The set is also fixed, so after one read-through it measures your memory of these items and not your command of CCA. Use it to choose where to start studying, not to decide whether you are ready, and then rely on the larger bank, where questions repeat only after a gap and the app tracks which domains stay weak.
A second limit is style. Written practice questions share one author voice, while a real exam draws on many writers and reads differently. Treat any practice score, here or elsewhere, as one input next to the official curriculum, hands-on experience with the technology, and the documentation of the project itself.
After the sample set, spend a week turning the result into a plan. Start with the domains where you missed questions and read the matching part of the official curriculum before you try more questions, because practice is far more useful once you can explain the topic. Return to practice in short daily sessions, review every missed question the next day, and leave the last day for a fresh mixed set. Keep a simple note of which concepts caused misses; the same three or four ideas usually explain most of them, and naming them is what turns practice into progress.
The largest CCA domain is Architecture, at 20% of the published weights. If two domains tie for weakest in your tally, start with the heavier one, and keep the other 7 domains ticking over with short reviews.
Adjust the pace to your calendar. If you have more time, spread the same steps over two or three weeks and add a second mixed session at the end of each week. If you have less, keep days 1 to 3 and day 6 and accept a rougher picture. What matters is that every study session starts from a specific weak domain and ends with a check, not that the plan is followed to the letter.
| Day | Task |
|---|---|
| 1 | Tally misses per domain and rank the domains from weakest to strongest. |
| 2 | Read the official curriculum and documentation for the weakest domain. |
| 3 | Practise that domain in the app and read every explanation. |
| 4 | Repeat the exercise for the second weakest domain. |
| 5 | Review the questions you missed on days 3 and 4 without looking at notes. |
| 6 | Do a mixed session across all domains and compare the result with this page. |
| 7 | Rest, then retake the 20 questions on this page and note which misses persist. |
These 20 questions are a small slice of the GoldenKube CCA bank, which holds more than 100 questions. In practice mode the app serves the questions you are due to review first, then the domain where you are weakest, and it brings missed questions back after a gap until you answer them correctly. You can answer 10 questions as a guest without an account; after that a free account keeps your progress, and no credit card is asked for at any point. Each answer comes with the same kind of written explanation you saw on this page, so a wrong answer is always followed by the reasoning that fixes it.
Practice mode shows one question at a time and gives the verdict and explanation as soon as you answer. A focus option lets you stay inside a single domain until it feels solid, which is the natural next step after finding your weakest domain on this page. There is no timer and no exam simulation in practice mode; the goal is learning, not performance under pressure.
No. They are practice questions written for GoldenKube to cover the published CCA domains. GoldenKube does not have the real exam, does not claim any overlap with it, and does not sell or share exam content. Use them to find gaps in your understanding, not to predict what you will be asked.
The CCA bank holds more than 100 questions as of 2026-10-23. This page shows 20 of them. The full bank is available in practice mode, where the app chooses what to show you next based on what you have already answered and what you got wrong.
Yes. Every question on this page has the correct answer marked and a written explanation of why it is correct and, where useful, why the other options are not. Only questions that have an explanation are published on public pages, and where a question carries references they are listed under the explanation.
Yes. Reading this page needs no account. In the practice app you can answer 10 questions as a guest, and then you create a free account to continue. No credit card is requested at any point.
A script picks them with a fixed seed, so the set does not change between visits. It considers only questions that have a written explanation and tries to follow the published domain weights. The domain labels in the bank do not always match the official wording, so a domain can be thinly represented in a single set of 20; the full bank is the better measure of coverage.
The exam facts and the domain list were last checked against the Linux Foundation pages on 2026-10-23, and the page shows its update date at the top. When the curriculum changes or questions are added, corrected or removed in the bank, the page is reviewed again.
Independent community project, not affiliated with or endorsed by CNCF or The Linux Foundation.