CS AO

It is delivered as multiple choice, typically single-best-answer, across the eight published domains. Some items are scenario-based and ask for the next diagnostic step or the most appropriate remediation rather than a definition. The official body publishes the current question count and any format variations on its certification site - check there, since these details change between versions.

Those figures are set by the certifying organisation and are revised periodically, so no fixed number is quoted here. Look up the current exam blueprint or candidate handbook on the official site before scheduling. Knowing the count and duration in advance matters mainly for pacing: scenario questions take longer than recall questions, so budget your time accordingly.

Candidates with a year or two of hands-on administration usually find the fundamentals and troubleshooting domains comfortable and the security and storage domains harder, because those reward precise knowledge of permissions, hardening baselines, and file-system behaviour. The exam is not designed to trick you, but distractors are plausible. If you have only read about a topic and never configured it, expect to struggle on that item.

Retake rules, waiting periods, and any additional fees are set by the certifying body and differ by region and exam version. The authoritative answer is in the official candidate handbook or policy page, not in third-party study guides. Before rebooking, get your score report if one is offered and use the domain breakdown to target the weakest areas rather than rereading everything.

Start with system administration fundamentals, since vocabulary and mental models there underpin everything else. Then do installation and deployment, followed by users and access management, which connects naturally to security and hardening. Storage and networking can follow in either order. Finish with monitoring, backup and recovery, and troubleshooting - those domains assume the earlier material and are best practised as scenarios.

A lab is close to essential. A single virtual machine or a container host lets you practise creating users and groups, setting permissions, mounting and resizing file systems, inspecting routes and firewall rules, and writing a backup and restore script. Reading produces recognition; typing commands and breaking things produces the recall the exam actually tests. Keep notes on every failure you cause and fix.

Three patterns recur: studying only the highest-weighted domains and leaving storage or networking thin; memorising commands without understanding what they change, which fails scenario questions; and misreading questions that ask for the first step or the least disruptive option. Another common slip is ignoring backup and recovery because it feels routine - restore order and verification steps are frequently tested.

It is most useful as structured proof of operational competence for people entering or formalising a sysadmin role, and as a checklist for self-taught administrators who have gaps. It is not a substitute for hands-on experience, and employers vary in how much weight they give it. Pair it with a portfolio of things you have actually built, automated, or recovered from an outage.

Fees, currency, regional pricing, and any recertification or validity period are determined by the certifying organisation and are updated over time. This page deliberately does not quote them. Confirm the current fee, validity, and renewal requirements directly on the official certification website, and check whether your employer or a training provider offers vouchers before paying.

Do practice scenarios under time pressure rather than rereading notes. Revisit your own lab runbooks for user provisioning, disk expansion, firewall changes, and restore procedures, and be able to justify each step. Review the domain weights and confirm you have covered every domain at least once. Sleep properly the night before - fatigue costs more marks on scenario items than one extra hour of revision gains.