# Kubernetes Operations (KO) practice exams

> Kubernetes Operations practice exams: 290 questions in 5 timed tests covering Observability. Every answer explained, with a score for each domain.

Page: https://devopscodelab.com/exams/kubernetes-operations/

290 questions in 5 timed practice tests. Each test has about 60 questions and a 90-minute limit. The pass mark is 70%. Results are split across the 6 exam domains.

## Exam at a glance

| Setting | Value |
| --- | --- |
| Practice tests | 5 |
| Questions in total | 290 |
| Questions per test | About 60 |
| Time limit per test | 90 minutes |
| Pass mark | 70% |
| Question types | Single answer and multiple answer (28 multiple-answer questions) |
| Level | Associate |
| Category | DevOps & Cloud Native |

These are the settings of our practice tests. Check the official CNCF exam page for the current format before you book.

## Domains and weights

| Domain | Weight | Questions in our bank |
| --- | --- | --- |
| Cluster Lifecycle and Upgrades | 18% | 52 |
| Scheduling, Autoscaling and Capacity | 18% | 52 |
| Cluster Networking, CNI and DNS | 17% | 49 |
| Storage, Backup and Disaster Recovery | 15% | 44 |
| Observability and Incident Troubleshooting | 20% | 58 |
| Security Operations | 12% | 35 |

## Price and access

- KO practice exams: $12.99 for 12 months of access.
- Free mini exam: 15 questions with explanations (free account): https://devopscodelab.com/app/exams/kubernetes-operations/mini/
- All-Access subscription includes every exam: https://devopscodelab.com/pricing/
- 10 free questions with answers: https://devopscodelab.com/exams/kubernetes-operations/free-practice-questions/

## Sample questions

### Question 1 of 3

A platform team runs a self-managed kubeadm cluster on Kubernetes 1.33 with three control-plane nodes. Security policy now requires 1.35 before the end of the quarter, and the team wants to stay within the supported upgrade path. Which plan should the team follow?

- A. Build a fresh 1.35 control plane next to the old one and restore a 1.33 etcd snapshot into it, which lets the cluster skip the intermediate 1.34 release.
- B. Run kubeadm upgrade apply v1.35.x directly on the first control-plane node, because kubeadm migrates static Pod manifests across two minor versions in one pass.
- C. Upgrade every worker kubelet to 1.35 first so the nodes are ready before the API server moves, and then jump the control plane straight from 1.33 to 1.35.
- D. Upgrade the control plane to 1.34 and then to 1.35, one minor version per step, and bring kubelets up afterwards while staying inside the supported skew.

**Answer:** D

**Explanation:** Control-plane upgrades must move one minor version at a time, and kubelets follow the control plane because a kubelet may never be newer than the API server. kubeadm refuses to skip a minor version, so a direct 1.33 to 1.35 apply is not supported. Upgrading kubelets first would make them newer than the API server, which breaks the skew policy. Restoring an older etcd snapshot into a newer control plane skips the per-version storage migrations and is not a supported upgrade path.

### Question 2 of 3

A policy webhook with failurePolicy: Fail matches all pod CREATE requests. During node-pool rotation its two replicas were evicted at the same time, and now no pods, including the webhook's own replacements, can be created. Which design prevents this deadlock in future rotations?

- A. Run the webhook as a static pod on every control-plane node, so it is never drained and is always available to the API server.
- B. Exclude kube-system and the webhook's own namespace via a namespaceSelector, and run several webhook replicas under a PDB.
- C. Switch to failurePolicy: Ignore permanently so pod creation always succeeds whenever the webhook is unreachable during any type of maintenance.
- D. Raise the webhook timeoutSeconds to 30 so the API server waits longer for the replacement webhook replicas to become ready again.

**Answer:** B

**Explanation:** Excluding the webhook's own namespace and system namespaces breaks the circular dependency, and a PDB with several replicas prevents losing all instances during drains. Ignoring failures permanently disables the policy whenever the webhook is down, which defeats its purpose. A longer timeout does not help if no webhook pod can ever be created. Static pods are an unusual and hard-to-operate way to run a webhook and do not address the circular match on its own pods.

### Question 3 of 3

Cluster Autoscaler never removes a node that has been under 20% utilisation for days. Its status shows the node cannot be removed because a Deployment pod on it uses an emptyDir volume for cache data that can safely be lost. What is the MOST targeted fix?

- A. Lower --scale-down-utilization-threshold to 0.1, so that nodes with very little requested capacity become candidates for removal sooner.
- B. Assign the Deployment a low-value PriorityClass so the autoscaler treats its pods as preemptible and ignores them when evaluating scale-down.
- C. Create a PodDisruptionBudget with maxUnavailable: 1 for the Deployment so the autoscaler knows that evicting one pod is permitted.
- D. Annotate the pod template with cluster-autoscaler.kubernetes.io/safe-to-evict: "true" so the autoscaler may evict pods with local storage.

**Answer:** D

**Explanation:** Cluster Autoscaler by default will not evict pods that use local storage such as emptyDir, and the safe-to-evict annotation explicitly allows it. The node is already below the utilisation threshold, so lowering it changes nothing. A PDB governs how many pods can be disrupted but does not override the local-storage rule. Priority affects the expendable-pods cutoff only below a configured threshold and is a blunt workaround for this specific blocker.


## Study plans

### Two weeks

1. Day 1: take practice test 1 in exam mode to get a baseline.
2. Days 2 to 5: domain mode on Observability and Incident Troubleshooting and Cluster Lifecycle and Upgrades, the two most heavily weighted domains.
3. Day 6: practice test 2 in exam mode, then the mistakes quiz.
4. Days 7 to 12: practice tests 3 to 5, one every other day, each followed by its mistakes quiz.
5. Days 13 and 14: final mode. Book the exam when your readiness stays above the pass mark.

### Four weeks

1. Week 1: one practice test in practice mode, reading every explanation. Note your two lowest domains.
2. Week 2: domain mode on those two domains, then a second practice test in exam mode.
3. Week 3: practice tests 3 and 4 in exam mode, with the mistakes and flagged quizzes after each.
4. Week 4: practice test 5 and final mode until your readiness holds above the pass mark.

## Questions about the KO practice exams

**Are these real KO exam questions?**

No. We write every question ourselves and map it to the published KO exam objectives. We do not use leaked or recalled questions.

**Do the time limit and pass mark match the official exam?**

They match the settings of our practice tests. Exam providers change their format from time to time, so check the official exam page before you book.

**Can I try it before I pay?**

Yes. The free mini exam has 15 questions with full explanations and needs no account.

**How long do I keep access?**

A single-exam purchase gives you 12 months of access. All-Access includes this exam for as long as your subscription runs.

**What happens after I finish a test?**

You get a score, a pass or fail against the pass mark, a score per domain and every answer with its explanation.

Last updated November 2026.

DevOpsCode Lab is not affiliated with CNCF. KO and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
