Exam Day — Across Formats

This course teaches nine exams — eight CNCF project associates plus the Linux Foundation's own LFCS — and they do not all hand you the same kind of exam room. Seven are pure multiple choice. One, ICA, is hybrid: real hands-on tasks mixed with multiple-choice questions in the same sitting. One, LFCS, is fully performance-based: a live terminal, a real machine, and nothing to pick from a list at all. What makes exam day genuinely plannable despite that split is that the security gate in front of all nine is nearly identical — the same system check, the same ID rule, the same webcam room scan, the same queue for a proctor — and only what happens after that gate changes. This page separates the two cleanly: the logistics that are worth rehearsing once and reusing for every one of the nine, and the format-specific differences that will actually catch you if you walk in assuming the wrong room is behind the door.

One proctoring script, three exam formats

☺ Like you're 10: The security check before the clock starts is nearly the same for all nine exams. What happens after the proctor lets you in is not — and it splits three ways, not two.

The Linux Foundation runs its entire training catalogue through a single identity-and-proctoring pipeline — currently PSI, at the time of writing. That's genuinely useful to you: booking, the ID rule, the room, the desk, check-in, and the proctor's authority over conduct are essentially identical whether you're sitting a ninety-minute knowledge-based associate like CGOA, the hybrid ICA, or the fully performance-based LFCS. What differs is everything that happens after the proctor releases the exam: the interface, the documentation you're permitted, and how the result is graded.

The week before: the system check, your ID, and the eligibility clock

☺ Like you're 10: Test your camera, microphone, and internet a week early, not on the day. And double-check your ID matches your account, letter for letter — this part is identical no matter which of the nine you're sitting.

The Linux Foundation portal offers a system-compatibility check before you ever book a slot. Run it the week before, on the exact machine, in the exact room, on the exact network you intend to use — then run it again the night before. Running it for the first time twenty minutes before your slot is how people discover their webcam driver broke in an OS update, or that a locked-down work laptop's endpoint security blocks the proctoring client outright. This matters just as much for a ninety-minute CGOA sitting as it does for a two-hour LFCS session — the check-in gate doesn't care which room you're headed into.

Raw bandwidth is rarely the problem; stability is. For the two formats with a live terminal — ICA's hands-on half and LFCS — a remote desktop is an interactive stream, so a connection that stutters for a few seconds every couple of minutes will cost you more than a slow-but-steady one. Even for the seven multiple-choice exams, where nothing is streamed back to you, a dropped connection still risks losing your proctor's video feed of you mid-sitting. These commands touch nothing exam-related; they just tell you what your own link actually does at the time of day you've booked:

# run this about a week out, then again the night before, at your actual exam time
ping -c 30 8.8.8.8

curl -o /dev/null -s -w 'dns=%{time_namelookup}s connect=%{time_connect}s tls=%{time_appconnect}s total=%{time_total}s\n' https://training.linuxfoundation.org/

# sample stability across a window as long as the exam itself, not a few seconds
for i in $(seq 1 900); do
  date +%H:%M:%S
  ping -c 1 -W 2 8.8.8.8 2>/dev/null | grep -o 'time=[0-9.]*' || echo DROPPED
  sleep 2
done | tee ~/kubestronaut-exam-link-check.log

grep -c DROPPED ~/kubestronaut-exam-link-check.log

If that drop count isn't zero, fix it before exam day: plug into ethernet, move closer to the router, or move the slot to a quieter hour. On the day itself, close every other application, pause cloud sync and OS updates, and ask your household to stay off video calls for the window.

The identity rule is the same across the whole Linux Foundation catalogue, and it's binary — there is no appeal at check-in. Your ID must be government-issued (a student card or employee badge doesn't count), must carry a photo and a signature (with one carve-out: government-issued biometric IDs without a signature are accepted), must be currently valid, and the name on your Linux Foundation profile must match it exactly — in the ID's own script. Full detail lives in the Linux Foundation's own Candidate Identification and Authentication policy.

Separately, keep two clocks straight, and don't let a busy nine-exam campaign blur them together: an eligibility window that starts the moment you purchase the exam — around twelve months for most of the seven knowledge-based associates, per each one's own blueprint page on this course — and a certification validity period that starts the day you pass, generally two years across this ladder. Field Notes names the failure mode this produces at campaign scale: spreading nine exams out at an unhurried pace routinely takes years, comfortably past the window your earliest pass opened. Confirm both figures at checkout for the specific exam you're booking rather than trusting a number from any third-party site, this one included — and for ICA and LFCS specifically, this course's own blueprint pages decline to state an eligibility-window number at all, because the Linux Foundation hasn't published one consistently for either.

The room, the desk, and the room scan

☺ Like you're 10: An empty table, a room with a door you can close, nobody else inside, and a slow camera tour — identical whether you're about to answer a quiz or drive a live terminal.

The environment rules exist to make cheating hard, and the proctor enforces them literally rather than reasonably — the good news is that they're easy to satisfy if you prepare the room the night before instead of improvising at check-in, and none of what follows depends on which of the nine exams you're sitting. Your room needs to be private, with a door you can close — not a café, not an open-plan office, not a car — and nobody else may enter for the whole session, even briefly. It needs to be well lit with your face clearly visible, and quiet, because the microphone stays live the entire time.

That last row is worth reading twice: physical scratch paper is not permitted for any of the nine. It rarely comes up for the seven closed-book associates, since there's nothing to sketch before selecting an answer — but if your LFCS habit is to plan a partition layout on paper before typing the commands, or your ICA habit is to draft a VirtualService by hand first, break that habit before exam day. There is no equivalent at all for the seven MCQ associates, and no substitute for it on LFCS or ICA's hands-on half beyond whatever the exam interface itself provides.

Before the exam is released, the proctor asks for a slow 360° pan of the room: the desk surface and underneath it, the walls, the ceiling, and often the front and back of your monitor. Make it fast by making it boring — clear the desk the night before, take anything readable off the walls, put your phone in another room, and rehearse the pan once so you aren't fumbling live on camera.

Check-in, the queue, and the timeline

☺ Like you're 10: Start check-in about thirty minutes early. It's a queue, not a door — and none of that time counts against your exam clock, so being early is completely free, on all nine.

Check-in typically opens thirty minutes before your scheduled start, and you should use all of it: launch from the portal → the proctoring client runs a system and network check and asks for camera, microphone, and screen-share permissions → you're placed in a queue for a proctor → identity verification → the room and desk scan → the proctor confirms the rules and releases the exam → the timer starts. The queue is the part people forget about — at busy times you may wait, and that wait is on the proctor's side of the clock, not yours, which is precisely why starting at T-minus-30 rather than T-minus-5 is the difference between a calm start and a frantic one, whether the room behind the door turns out to be a quiz or a live terminal.

Plan for no scheduled breaks, and assume the clock never stops. Some exams permit a short unscheduled break, but where they do it's on your time, must be cleared with the proctor first, and typically triggers re-verification — sometimes another room scan. Handle the practicalities before check-in: use the bathroom, have your permitted drink already on the desk, and don't load up on coffee an hour beforehand.

Once you're in: three screens, one grading philosophy each

☺ Like you're 10: One screen is a quiz with four choices. One is a quiz that occasionally hands you a real terminal. One is only a real terminal, the whole time.

This is where the three formats stop resembling each other at all. Rehearse the layout you'll actually see for whichever exam is next, because fumbling the interface in the first five minutes wastes real clock time on any of the three.

For the seven knowledge-based associates, that's the entire interface: a question, four options, previous/next, a flag control, and a review screen listing every question's answered/unanswered/flagged state before you submit. There is no terminal, no live environment, and — worth repeating — no documentation of any kind. Never leave a question blank; nothing published indicates a penalty for a wrong answer, so an educated guess always beats a guaranteed zero, and every one of these seven shares the same published 75% pass mark, from the Linux Foundation's general Multiple Choice Exam FAQ rather than any cert-specific page.

For ICA, the browser gives you a mix: some screens look exactly like the knowledge-based interface above, and others drop you into a Linux remote desktop with a terminal against a real cluster, the same underlying product the hands-on Kubernetes exams use. The one detail this course's own ICA blueprint deliberately does not commit to is documentation access during the hands-on half — the Linux Foundation has never published it consistently, so treat any confident claim you read elsewhere as unverified and confirm it yourself in the current candidate handbook before you decide how much of Istio's YAML you need memorized versus merely known-where-to-find.

For LFCS, there's no multiple choice anywhere: 17–20 real tasks, solved on a live terminal, graded purely on the final state of the machine against a published 67% pass mark. Two habits are worth drilling until they're reflex, and they matter for ICA's hands-on half too. First, read exactly which host or context a task targets before you touch anything — LFCS tasks sometimes direct you to SSH to a designated host, and solving a task perfectly on the wrong machine scores zero, the same trap the sibling Kubernetes course's exam-day page describes for CKA's context switch. Second, verify before you move on — a fifteen-second check catches the typo that would otherwise silently cost you the whole task. Inside the remote desktop, clipboard shortcuts are Ctrl+Shift+C and Ctrl+Shift+V rather than the plain shortcuts your terminal already claims for something else, and you generally work as root via sudo -i once connected.

When it misbehaves

☺ Like you're 10: If your internet blips or the person watching says something, don't panic — stop, listen, and reconnect. Your progress usually isn't the thing at risk. Your time is.

It happens, and for all nine exams it's survivable if you know what to expect instead of guessing under pressure.

What's true today — and what only the official page can tell you

☺ Like you're 10: The numbers below are generally accurate right now, but this site isn't the Linux Foundation — always check the real page before you pay for anything.

This course is an independent, unofficial study resource and is not affiliated with the CNCF or the Linux Foundation. Format and rough duration are stable enough to plan around; price, exact task or question counts, and retake terms move more often and are deliberately not repeated here as fixed numbers where this course's own certification pages don't commit to one either.

One free retake has historically been bundled with each of the seven knowledge-based associates, inside a roughly twelve-month eligibility window; ICA and LFCS are the two exams on this shelf where this course's own pages decline to state a retake number, because the Linux Foundation hasn't published one consistently for either. Pass/fail results are typically emailed within a day or so of finishing — LFCS and ICA's hands-on half are graded after the fact against the machine's or environment's end state, so nothing appears on screen the moment you click finish.

None of this is the hard part — the hard part is Argo, Cilium, Kyverno, Prometheus, Istio, and the rest, and this page is the cheapest hour you'll spend protecting your preparation for any of them. Work through the readiness checklist, follow the pacing in how to study for a multi-exam marathon, drill recall with flashcards and the self-check quiz, read Field Notes for the format traps that actually catch people, and confirm every volatile number on each exam's own official page before you book.