How I Passed the Certified Kubernetes Administrator (CKA) Exam: My Experience

 Hi there! Recently, I took the Certified Kubernetes Administrator (CKA) exam. In this blog post, I want to share my experience and provide some tips and advice for anyone who is planning for the CKA exam.

As we know CKA certification is one of the challenging exams that tests your knowledge of Kubernetes, cluster troubleshooting, and helps improve your skills as a DevOps engineer. The CKA certification is highly respected in the industry and demonstrates a high level of expertise in managing Kubernetes clusters.

Press enter or click to view image in full size

Exam Overview

The CKA exam is a hands-on, practical exam that tests your ability to manage Kubernetes clusters. The exam lasts for 2 hours and consists of multiple tasks that you must complete using a live Kubernetes cluster. The tasks cover a wide range of topics, including cluster architecture, networking, storage, security, and troubleshooting.

Press enter or click to view image in full size

Study Tips: Here are some tips that helped me prepare for the CKA exam:

• Use multiple sources of study materials: In addition to the official Kubernetes documentation, I found the training materials from KodeKloud (Mumshad Mannambeth) to be very helpful.
• Practice, practice, practice: The CKA exam is very hands-on, so it’s important to get as much practice as possible. Set up your own Kubernetes cluster and try to complete all the tasks from the exam syllabus.
• For practicing and preparing for the CKA mock exam, I used the courses from the KodeKloud mock series and Alok Kumar. These courses provided me with valuable knowledge and hands-on experience that helped me succeed in the exam.

Links

https://kodekloud.com/courses/ultimate-certified-kubernetes-administrator-cka-mock-exam/

https://www.udemy.com/course/certified-kubernetes-administrator-cka-lab-course/

CKA study Tracker I used this to track my progress on CKA topics.

Extra Resource: I used this book to get some clarity and deep dive into topics. Kubernetes Bible

Exam Advice: Here is some advice for taking the CKA exam:

• Manage your time carefully: The CKA exam is 2 hours long, so it’s important to manage your time carefully. Make sure you leave enough time to complete all the tasks.
• Read the questions carefully: Make sure you understand what each task is asking you to do before you start working on it.
• Use the official Kubernetes documentation: During the exam, you are allowed to access the official Kubernetes documentation. Make sure you know how to quickly find the information you need.
• There are some questions on the CKA exam that follow a similar pattern and are repeated in various resources. Make sure you practice these types of questions using the courses from KodeKloud and Alok Kumar, as mentioned earlier. Avoid making mistakes on these questions, as it could be costly.

Passing the CKA exam was a challenging but rewarding experience. I hope that my tips and advice will help others who are preparing for the exam. If you have any questions or would like to connect with me, feel free to reach out on LinkedIn.

My other blog

10 Books Every DevOps Engineer Should Read

Free Terraform Quiz !! Check your Score

The 3-Week Schedule for AWS Certified CloudOps Engineer - Associate

 

The 3-Week Schedule for AWS Certified CloudOps Engineer - Associate 

Week 1 — Monitoring and Reliability (44% of the exam)

Day 1 — CloudWatch fundamentals Metrics, namespaces, dimensions, statistics vs. percentiles. Default EC2 metrics vs. what needs the CloudWatch agent (memory and disk usage are not default — this shows up constantly). Custom metrics, resolution, retention.

Day 2 — Logs and audit trail CloudWatch Logs, log groups, retention settings, metric filters, subscription filters, Logs Insights query syntax. CloudTrail: management vs. data events, organization trails, log file validation. Know when the answer is CloudTrail vs. CloudWatch Logs vs. VPC Flow Logs.

Day 3 — Alarms and auto-remediation Alarm states, missing-data treatment, composite alarms. EventBridge rules and targets. SNS. Then the remediation side: Systems Manager Automation runbooks, Lambda targets, EC2 recovery actions. This is where domain 1 gets scenario-heavy.

Day 4 — Auto Scaling and load balancing Launch templates vs. launch configs, target tracking vs. step vs. scheduled scaling, cooldowns, lifecycle hooks, warm pools. ALB vs. NLB vs. GWLB, target groups, health check tuning, stickiness, cross-zone balancing.

Day 5 — High availability Multi-AZ vs. multi-Region. RDS Multi-AZ vs. read replicas (different purposes — the exam checks that you know which). Aurora failover. S3 Cross-Region Replication. Route 53 health checks and failover routing.

Day 6 — Backup and recovery AWS Backup plans and vaults, EBS snapshots and the incremental model, AMI lifecycle, Data Lifecycle Manager. RTO/RPO and matching the four DR strategies to them. S3 versioning, lifecycle policies, Object Lock.

Day 7 — Consolidate No new material. 50–60 practice questions on domains 1 and 2 only, then re-read the docs for everything you got wrong.

Week 2 — Automation, Security, Networking (56%)

Day 8 — CloudFormation Template anatomy, intrinsic functions (Ref, GetAtt, Sub, FindInMap), parameters and mappings, conditions. Then the operational parts the exam loves: change sets, drift detection, DeletionPolicy, UpdateReplacePolicy, nested stacks, StackSets across accounts and Regions, and which update types cause replacement.

Day 9 — Systems Manager The single densest service on this exam. Parameter Store (Standard vs. Advanced, SecureString), Session Manager and why it beats bastion hosts, Patch Manager and patch baselines, Run Command, State Manager, Automation runbooks, Inventory. Know the SSM Agent prerequisites and the IAM instance profile it needs.

Day 10 — Deployment and containers Rolling, blue/green, canary, immutable. Elastic Beanstalk deployment policies. Then the SOA-C03 additions: ECR basics, EKS operational concepts, and where CDK and Terraform fit relative to CloudFormation.

Day 11 — IAM Policy evaluation logic and explicit deny. Identity vs. resource policies. Roles and cross-account access. Permission boundaries. SCPs and how they interact with IAM policies. IAM Identity Center. Practise reading a policy document and saying exactly what it allows.

Day 12 — Security services and cost KMS key types, rotation, grants. Secrets Manager vs. Parameter Store. GuardDuty, AWS Config with conformance packs and remediation, Inspector, Security Hub, Trusted Advisor — know which one answers which question. Then cost: Cost Explorer, Budgets, Savings Plans vs. Reserved Instances, S3 storage classes and Intelligent-Tiering, Compute Optimizer.

Day 13 — VPC Subnets and route tables, IGW vs. NAT Gateway, Security Groups vs. NACLs (stateful vs. stateless — reliably tested), VPC endpoints gateway vs. interface, peering and its limits, Transit Gateway, VPC Flow Logs and reading a rejected-traffic line. Expect multi-step troubleshooting scenarios here.

Day 14 — DNS and edge, then consolidate Route 53 routing policies — simple, weighted, latency, failover, geolocation, geoproximity, multivalue — and alias vs. CNAME. CloudFront behaviours, OAC, cache invalidation. Finish with 50–60 questions across domains 3, 4 and 5.

Week 3 — Mocks and repair

No new content this week. The whole point is finding your gaps while there's still time to close them.

Day 15 — Mock exam 1. Full 130 minutes, timed, no pausing, no looking anything up. Score it and note the per-domain breakdown.

Day 16 — Review every single wrong answer. Not just the right option — why each distractor is wrong. For anything you don't fully follow, read the actual AWS documentation page. Slower than it sounds; budget the full two hours.

Day 17 — Mock exam 2.

Day 18 — Review, then drill your weakest domain. By now a pattern is obvious. Mine was CloudFormation update behaviour and Route 53 routing policies.

Day 19 — Mock exam 3. You want to be consistently above 80% here. The real exam pass mark is 72%, but mock scores tend to run a little optimistic relative to it.

Day 20 — Read the official exam guide task statements end to end. Every bullet AWS lists is fair game. Anything you can't explain in a sentence, go look up. Flashcards for service limits and defaults.

Day 21 — Light review and stop. Skim your notes, confirm your Pearson VUE booking and ID, and finish early. Cramming the night before buys nothing on a scenario exam.