LFCS exam-day guide
LFCS · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original (not a photocopy) of a valid passport, driver's license, or national ID. The name must match your exam registration exactly - if it does not, ask the provider to correct it before exam day. Confirm which ID forms your provider accepts for your delivery method (test center vs. remote proctoring).
Appointment confirmation and correct time zone
Locate the confirmation email and the launch/check-in link in advance. Write down the start time converted to your local time zone, and note whether check-in begins earlier than the start time - confirm the check-in window with the provider.
Stable wired internet connection plus a backup
Prefer a wired Ethernet connection over Wi-Fi. Have a fallback ready (mobile hotspot or a second network) in case the primary drops mid-exam. Test upload/download speed and latency the day before.
Webcam, microphone, and speakers/headset
Required if you are taking the exam via remote proctoring; built-in laptop hardware is usually fine but test it beforehand. If you sit the exam at a physical test center, these are provided - confirm your delivery method.
Completed system/compatibility check
Run the provider's system test or secure-browser check on the exact machine you will use, ideally 48-72 hours ahead so you have time to fix problems. Re-run it the day before.
Quiet, private room with a clear desk
Remove notes, books, phones, smart watches, printers, and any second monitor from the desk and surrounding area. Tell household members not to enter the room during the exam.
Laptop power adapter and charged battery
Plug in for the whole session. A power loss mid-exam can cost you time even if your work is preserved.
Second device for support contact
Keep a phone (silenced and out of arm's reach unless the proctor instructs otherwise) so you can reach provider support if the session fails to launch.
Linux Foundation portal credentials
Know your account username and password, and how to reach the exam launch page from your training/certification dashboard. Do not rely on a browser-saved password on a different machine.
Water in a clear container (and no other food or drink unless permitted)
Some proctoring services allow only clear, unlabeled containers at the desk. Confirm the allowance with your provider before the exam.
Practice in the actual exam style
The exam is hands-on in a live Linux environment you do not provision yourself. Before exam day, rehearse solving tasks from a plain terminal with only on-system documentation (man pages, /usr/share/doc) available, and practise verifying each change with a command rather than assuming it worked.
Read the candidate handbook for your delivery method
Rules differ between remote-proctored and test-center delivery (room scans, ID checks, permitted items, break policy). Read the current handbook rather than relying on forum posts.
Plan the day
Confirm the appointment date, start time, and time zone; verify the name on your registration matches your ID. Run the provider's system test on the machine you will use and fix anything that fails. Check that your internet is stable at the time of day your exam starts.
Do timed practice runs: pick a set of hands-on tasks across the exam domains and complete them in a terminal within a clock, using only man pages and locally installed documentation. Identify your two weakest areas and drill only those - do not start new topics you cannot consolidate.
Shift your sleep schedule so you are alert at your exam start time, and clear your calendar for the exam slot plus an hour of buffer on either side.
Light review only: man page navigation, systemd/service management, networking, storage, and package management commands you already know. Verify your equipment (webcam, mic, headset, charger), clear the desk, and re-run the compatibility check. Note your provider's support phone number and the exam launch link.
Avoid cramming new material or staying up late. Prepare your ID and water in a clear container by the desk so nothing is missing in the morning.
Eat a normal meal, avoid heavy caffeine if you are jittery, and do a final 10-minute hardware and network check. Close all unnecessary applications, browser tabs, and messaging clients; disconnect second monitors if remote-proctored. Keep your ID within reach.
Join check-in earlier than the stated start time if your provider requires it - confirm the exact check-in window in the handbook, as late arrival can forfeit your slot.
Skim every task before starting so you can sequence work efficiently. Note that the environment is a live Linux system you did not build: check the distribution, installed packages, and available documentation first.
Read each task fully, including any persistence requirement (config that must survive a reboot). Make one change at a time and verify it immediately with a status command, a config test, or a service restart before moving on. Use man pages freely; do not guess at syntax you can look up in seconds.
Track elapsed time against the number of remaining tasks. If a task is consuming disproportionate time, leave it in a working (even if partial) state, move on, and return only if time allows. Do not leave a task with a broken configuration - a working simple solution beats an ambitious incomplete one.
Re-verify that services you enabled are still running and that edited configuration files parse cleanly. Finish or end the session using the provider's own end/submit control rather than closing the browser, and confirm you see the completion confirmation on screen.
Rules to check
Present one original government-issued photo ID whose name matches your registration exactly; the proctor may also require a room scan, a live photo, or a signature check depending on delivery method - confirm what applies to you with the provider.
No unauthorized materials: no notes, printed pages, second monitor, phone in reach, or communication with anyone during the exam. The documentation installed on the exam system itself (such as man pages and /usr/share/doc) is generally permitted for a hands-on Linux exam, but verify the current permitted-materials list in the handbook before exam day.
Do not attempt to reach external websites, copy tasks out of the environment, or use another machine to solve tasks. Proctors can observe your screen and surroundings and may terminate a session for a violation.
Break policy is set by the provider and may be none at all for a proctored performance exam; plan hydration and restroom visits assuming you must remain at the desk for the full duration - confirm the actual policy with the provider.
The exam is scored pass/fail on the hands-on tasks you complete, not on multiple-choice answers. The exact passing threshold and whether partial task credit is awarded are set by the Linux Foundation - confirm with the provider rather than relying on secondhand reports.
The sitting is time-limited; confirm the current duration and task count when you book, since these have changed across exam revisions.
Results and retake terms (delivery timing, included retake, waiting period) are governed by your certification agreement - confirm with the provider before you rely on any particular policy.
If your session fails to launch or disconnects, stop and contact provider support immediately using your second device; keep any session or ticket reference they give you.