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

Finish a Full Mock Inside 120 Minutes

A mock is a rehearsal of decisions, not just commands. This lesson sets the time budget, the skip discipline, and the closing sweep that turn knowledge into a passing score.

12 min reading

Objectives

Budget the 120 minutes across tasks by domain weight before starting
Skip and return with flags instead of bleeding time on one task
Bank easy points first so pressure drops for the hard third
Close the session with a verification sweep instead of early exit

Why this matters

Most failed mocks are not failed knowledge: candidates knew enough and still ran out of clock on task three of seventeen. The exam allots roughly seven minutes per task with weights wobbling by domain. A plan converts that arithmetic into behavior: which tasks first, when to abandon, how to finish.

Concepts

Budget by weight before the timer starts. Troubleshooting carries 30 percent, so it earns the biggest block; storage at 10 percent earns the smallest. Write the per-task minutes on paper: clusters of small tasks get strict caps, monsters get generous ones. The plan is visible during the exam, which matters when judgment fades.

Skip discipline is the highest-value skill. Two minutes without progress means flag and move: flagged tasks return with fresh eyes and banked confidence. Easy points first is the same principle at session scale: storage plus workloads questions answer fast and fund the clock for troubleshooting monsters.

The closing sweep spends the last ten minutes verifying, not earning: re-read each solved task, confirm the object exists with the right fields, and check nothing was left half-applied. Early exits donate points nobody can afford.

Worked example

A 120-minute budget for a 17-task mock shaped like the blueprint:

Minutes 0-5:    read all tasks, flag the 3 monsters, order the rest
Minutes 5-35:   storage (10%) + workloads (15%): fast points first
Minutes 35-60:  architecture (25%): installs, RBAC, upgrades
Minutes 60-85:  networking (20%): services, ingress, policies, DNS
Minutes 85-115: troubleshooting (30%): the flagged monsters, fresh
Minutes 115-120: verification sweep, no new work
Rule: 2 minutes stuck means flag and move, no exceptions

Run the mock with this sheet visible. Score it twice: points earned, and minutes lost to tasks that deserved flags earlier. The second number is the training target.

Exam notes

Reading all tasks first feels slow and saves the most time: surprises scheduled beat surprises discovered. Never spend the sweep starting new work; a half-applied change risks breaking a solved task. And flags need a return order: hardest-flagged first while the mind is freshest, not last in panic.

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

Take any past practice set and rebuild it as a timed plan: per-task minutes from domain weights, flag rules, return order, sweep checklist. Run it once and report points plus minutes-lost-to-stubbornness with one adjustment for next time.

Pass criteria

Plan derives minutes from weights with visible caps; flag rule stated with a number; report separates points from lost minutes and names one concrete adjustment.