CTLA

It is a multiple-choice exam. The published blueprint lists eight weighted domains rather than a single syllabus, so questions are spread across administration, scripting, networking, security, storage, services, virtualization and troubleshooting. The official body publishes the current question count, time limit and delivery options on its website; confirm there before scheduling.

Candidates with a year or two of hands-on Linux administration usually find the core domains manageable, but the breadth is the real challenge: networking, hardening and scripting all carry meaningful weight. Scenario questions that describe a symptom and ask for the cause punish memorization. If you have only studied commands without troubleshooting a broken system, expect the margin to be tight.

Retake rules, waiting periods and any fees are set by the official certification body and can change, so check its website for the current policy rather than relying on forum posts. Practically, treat a failed attempt as diagnostic: note which domain the score report flags as weak, lab that area for a few weeks, then rebook.

There is no official study-hour requirement. A realistic plan for someone with basic Linux exposure is eight to twelve weeks of part-time work: two or three focused sessions a week, each split between reading and lab practice. Candidates already administering systems daily often compress this. Use the domain weights to allocate time rather than studying every topic equally.

Start with Linux system administration, since permissions, processes and logs underpin everything else. Add shell scripting next so you can automate your own lab checks. Then take networking and security hardening together, because firewalling and SSH configuration sit at their intersection. Storage and service management follow naturally, with virtualization and troubleshooting last as synthesis.

The concepts are largely portable, but the exam is Linux-focused and many operational details differ between families. Be comfortable with systemd on a Red Hat-family or Debian-family system, and know where each keeps network configuration, unit files and logs. Understanding both families makes distribution-specific questions far less risky.

Shell scripting and command-line tools carry about 15% of the blueprint, but scripting knowledge leaks into other domains. Expect questions on exit codes, quoting, conditionals, loops, redirection and text processing with grep, sed and awk. You do not need to write long programs; you need to read a short script and predict its output or spot the bug.

Three recur: neglecting networking and security because they feel less familiar than day-to-day administration; memorizing command syntax without practising diagnosis; and ignoring exit codes, quoting and redirection, which quietly break scripts. A fourth is misreading a scenario question and answering what you would do in your own environment rather than what the question asks.

Strongly recommended. Multiple-choice questions about a failed mount, a service that will not start, or a firewall rule that blocks traffic are far easier if you have broken and fixed those things yourself. A single virtual machine plus snapshots is enough to practise users, permissions, units, journal reading, partitioning and SSH hardening.

Question count, appointment length, fee, passing score, retake policy and score-report details are all set by the official certification body. Those figures change, so consult its website directly rather than third-party summaries. This page deliberately avoids quoting numbers that may be out of date.