Free lesson · CKAD Prep Program · Module 7: Full mock exams

Run Your 120 Minutes from the Developer Seat

The CKAD clock rewards finished apps, not perfect ones. This lesson budgets 120 minutes from the deploy-first habit: manifests early, observability in the middle, monsters last.

12 min reading

Objectives

Order tasks app-outward: manifests first, debugging when eyes are fresh
Cap YAML-writing tasks so they cannot eat the debugging third
Use flags per task type: authoring stalls differ from debugging stalls
Reserve verification minutes that re-apply nothing

Why this matters

Developer-seat exams punish two opposite sins: perfect YAML on five tasks with twelve abandoned, or frantic debugging of apps that were never deployed right. The order decides the score: authored apps first while hands are steady, debugging while eyes are fresh, monsters with banked confidence.

Concepts

App-outward ordering means M01-M03 tasks (manifest authoring, config, multi-container) come first: they score fast and build the cluster state later tasks may reference. Observability tasks (M05) sit in the middle: probes and log tasks need running apps and fresh pattern eyes. Monster debugging (M05 M12 plus flagged surprises) goes last with everything banked.

Cap authoring strictly: eight minutes per authoring task, then flag. Authoring stalls feel productive (typing is motion) while scoring nothing. Debugging stalls get the two-minute flag rule from the CKA lessons with one addition: state the layer verdict aloud before flagging, so the return starts warm.

Worked example

A 120-minute developer budget:

Minutes 0-5:    read all tasks, sort: authoring / config / observe / debug
Minutes 5-45:   authoring + config (M01-M03): 8-minute cap each, flag overflow
Minutes 45-75:  observability (M05): probes, logs, metrics tasks on live apps
Minutes 75-110: debugging + monsters: flagged returns first, verdicts ready
Minutes 110-120: verification only: pods ready, answers match, nothing re-applied
Rule: typing without scoring for 3 minutes means flag, always

Score it twice like the CKA lessons: points, plus minutes lost to authoring stalls. Developers almost always find the second number embarrassing the first time: that is the training working.

Exam notes

Authoring tasks reference each other: deploy the namespace and quotas before the apps that live in them. Observability tasks assume running apps: never debug logs for pods you have not confirmed running. And the verification sweep checks answers, not elegance: ugly YAML that passes beats beautiful YAML abandoned.

Quick check

A 4-question self-check. Your answers stay on your device, are never stored or sent. Only a passing score (for example 3 of 4) is saved, and only to unlock lesson progress: at least 3 correct is required before a lesson counts as complete. It never counts toward any certification assessment.

Lesson feedback

No published feedback yet.

Exercise

Rebuild a past practice set as a developer-ordered plan: task sort, per-task caps, flag rules per type, verification list. Run it and report points plus minutes-lost-to-authoring with one adjustment.

Pass criteria

Plan sorts tasks app-outward with caps; flag rules differ per type; report separates points from authoring-stall minutes and names one adjustment.