How CKAD Weights Its Domains, and Where to Spend Your Hours

Understanding the CKAD Exam Blueprint

The Certified Kubernetes Application Developer (CKAD) exam is performance-based, testing your ability to design, build, and operate cloud-native applications on Kubernetes. The official curriculum is divided into five domains, each with a specific percentage weight that reflects its importance in the exam. Knowing these weights helps you prioritize your study time and focus on what matters most. This article provides a detailed breakdown of each domain, the sub-topics that appear most frequently, and where candidates often underestimate the difficulty.

Domain 1: Core Concepts (13%)

This domain covers the fundamental building blocks of Kubernetes. While it has the lowest weight, it lays the foundation for everything else. Expect questions on API resources, pods, and basic kubectl commands. For more on this topic, see our guide on How PL-300 Weights Its Domains, and Where to Spend Your Hours.

Frequently Tested Sub-topics

• Understanding the Kubernetes API and resource categories
• Creating and managing pods (YAML syntax, labels, annotations)
• Using kubectl for basic operations (get, describe, logs, exec)

Underestimated Sub-topics

Many candidates underestimate the importance of namespaces. You may be asked to create resources in a specific namespace or work with namespace-scoped resources. Practice using the --namespace flag and setting context to avoid mistakes.

Recommended Resource

Kubernetes documentation: Kubernetes Basics tutorial. It provides a solid introduction to pods, kubectl, and namespaces.

Domain 2: Configuration (18%)

This domain focuses on making applications configurable and managing configuration data. It's a significant chunk of the exam, so allocate ample time here.

Frequently Tested Sub-topics

• ConfigMaps and Secrets: creating, consuming, and mounting them
• Understanding SecurityContext and resource requirements
• Working with ServiceAccounts and RBAC basics

Underestimated Sub-topics

Candidates often struggle with SecurityContext settings, especially when combined with PodSecurityPolicies (though PSPs are deprecated, similar concepts apply). Understand how to set capabilities, run as non-root, and read-only root filesystems. Also, practice ResourceQuota and LimitRange to enforce resource constraints.

Recommended Resource

Kubernetes documentation: Configure a Pod to Use a ConfigMap and Secrets guides. These are comprehensive and include examples.

Domain 3: Multi-Container Pods (10%)

This domain tests your understanding of multi-container pod design patterns. Though small in weight, it's a favorite for tricky questions.

Frequently Tested Sub-topics

• Understanding the three patterns: sidecar, ambassador, and adapter
• Implementing a sidecar container for logging or proxying
• Using shared volumes between containers in a pod

Underestimated Sub-topics

The initContainers concept is often misunderstood. You should know how to use init containers to run setup tasks before the main container starts, and how they affect pod lifecycle. Also, be aware of resource sharing and communication between containers via localhost. You might also find How Google Cloud DevOps Engineer Weights Its Domains, and Where to Spend Your Hours helpful.

Recommended Resource

Kubernetes documentation: Multi-container Pods and Init Containers pages. They explain patterns and provide YAML examples.

Domain 4: Observability (18%)

This domain covers monitoring, logging, and troubleshooting. It's tied for the second-highest weight, so don't neglect it.

Frequently Tested Sub-topics

• Understanding liveness, readiness, and startup probes
• Viewing logs with kubectl logs and sidecar containers
• Using kubectl exec and debug commands

Underestimated Sub-topics

Probes are a common pain point. You need to know the exact syntax for HTTP, TCP, and command probes, and the difference between liveness and readiness. Also, practice kubectl describe to identify common issues like ImagePullBackOff or CrashLoopBackOff. Many candidates overlook the kubectl debug command, which is useful for troubleshooting ephemeral containers.

Recommended Resource

Kubernetes documentation: Configure Liveness, Readiness and Startup Probes and Application Troubleshooting guide.

Domain 5: Services & Networking (13%)

This domain focuses on exposing applications and networking between pods. It's moderate weight but can be tricky.

Frequently Tested Sub-topics

• Creating Services (ClusterIP, NodePort, LoadBalancer)
• Using Ingress resources and Ingress Controllers
• Understanding NetworkPolicies and how to enforce them

Underestimated Sub-topics

NetworkPolicies are often the most challenging part. You need to understand how to write policies that allow or deny traffic based on pod labels and namespaces. Many candidates also struggle with headless services and how they work with StatefulSets. Practice creating an Ingress with path-based routing, as it's a common exam task.

Recommended Resource

Kubernetes documentation: Services and Network Policies pages. The NetworkPolicy editor from Cilium is a great interactive tool. Looking for more detail? See How Terraform Associate Weights Its Domains, and Where to Spend Your Hours.

Domain 6: State Persistence (8%)

This domain covers persistent storage for applications. It's the lowest weight but still important.

Frequently Tested Sub-topics

• Understanding PersistentVolumes (PVs) and PersistentVolumeClaims (PVCs)
• Using StorageClasses and dynamic provisioning
• Configuring volume mounts and access modes

Underestimated Sub-topics

Many candidates underestimate the concept of StorageClass and how it relates to dynamic provisioning. You should know how to create a PVC that uses a specific StorageClass, and the difference between static and dynamic provisioning. Also, understand the reclaim policy (Retain, Recycle, Delete) and how it affects PV lifecycle.

Recommended Resource

Kubernetes documentation: Persistent Volumes and Storage Classes pages. They provide clear explanations and examples.

Allocating Your Study Hours

Based on the weights, here's a suggested allocation for a typical 100-hour study plan:

Domain	Weight	Suggested Hours
Core Concepts	13%	13
Configuration	18%	18
Multi-Container Pods	10%	10
Observability	18%	18
Services & Networking	13%	13
State Persistence	8%	8

Remember to adjust based on your strengths and weaknesses. If you're new to Kubernetes, you might need more time on Core Concepts. If you're already comfortable with networking, you can shift hours to other domains.

For a plan that adapts to your available hours and current level, use the free CKAD study plan.

Final Tips for CKAD Success

Beyond knowing the objectives, practice is essential. The CKAD is a hands-on exam, so you must be comfortable using kubectl and writing YAML quickly. Use the official Kubernetes documentation during the exam, but don't waste time searching for basic syntax. Memorize common commands and patterns. Also, practice with a timer to simulate exam conditions.

For a quick check of your weak topics after a timed run, use the free CKAD readiness check.

Remember to read the questions carefully. Often, you'll be asked to create a resource and then verify it. Make sure to test your work with kubectl get and describe commands.

Get comfortable with the question style by working through Certified Kubernetes Application Developer (CKAD) mock test questions at your own pace.