More study resources

About this exam

The Cassandra Admin credential certifies that a candidate can run Apache Cassandra in production rather than merely write CQL against it. It targets database administrators, SREs and platform engineers who already touch a cluster and want their operational judgment validated: reading nodetool output under pressure, sizing a compaction strategy, deciding when a repair window is safe, and knowing which consistency level actually protects a given write.

The exam is delivered as multiple-choice and scenario-based multiple-choice items. Scenarios dominate the feel of it - you are handed a symptom (read latency spikes after a node restart, a hinted-handoff backlog that will not drain, a keyspace whose partitions grew past the comfortable range) and asked for the next diagnostic step, not the textbook definition. Coverage is weighted toward architecture, data distribution and performance tuning, with meaningful shares for repair, security and day-to-day operations. Expect to reason about token ownership, replication factor versus consistency level, and the read/write path rather than to recall command syntax verbatim.

Preparation should be lab-led. Build a multi-node cluster locally or in containers, break it deliberately, and practise recovery. Pair that with the official Apache Cassandra documentation - architecture, operations and the CQL reference - and your own cluster's logs and metrics. The certifying organization publishes current administrative details such as scheduling and pricing on its own site; confirm them there before booking.

What you'll study

Common questions

About Cassandra Admin preparation

Is this an official Apache Software Foundation certification?

No. Apache Cassandra is an open-source project and the ASF does not issue administrator certifications. Cassandra Admin credentials come from independent training providers and vendors. Check the specific certifying body's site for its syllabus, its current fees and scheduling, and whether the exam maps to a particular Cassandra release.

What is the exam format like in practice?

Multiple-choice and scenario-based multiple-choice, delivered online or at a test centre depending on the provider. Scenarios typically present a cluster symptom and ask for the best next action or the most likely root cause. Distractors are usually plausible-but-wrong operational moves, so read for the qualifier words - 'first', 'most likely', 'safest'.

How hard is it for someone who already runs a cluster?

Straightforward if your experience is broad; hard if it is narrow. People who only add nodes and run repairs tend to fail on JVM and compaction questions; people who only tune JVM tend to fail on repair, security and topology. Audit your weak domains against the published weights before you book, and lab the ones you avoid at work.

In what order should I study the domains?

Start with architecture and the distributed ring, because partitioning, replication and consistency questions become easy once token ownership is intuitive. Then data modelling and performance tuning, which lean on the same mental model. Leave repair and security for last - they are more self-contained and reward memorising concrete parameters and defaults.

Can I pass on documentation reading alone?

Rarely. Documentation gives you definitions but not the diagnostic reflexes the scenarios test. You need to have watched nodetool tpstats drop blocked tasks, seen what a compaction backlog does to latency, and restored a snapshot. Reading plus a three-node lab is the realistic minimum.

What are the most common failure modes?

Confusing replication factor with consistency level; assuming QUORUM on a two-DC cluster means what it means on one; recommending nodetool repair when the real answer is fixing a tombstone or compaction problem; and forgetting that ALL availability depends on every replica being up. Also: answering the textbook fix instead of the safest first step.

What happens if I fail - can I retake it?

Providers generally allow retakes, sometimes after a waiting period and usually at a reduced or full fee. The exact retake policy, waiting window and cost are set by the certifying organization, so read its candidate handbook rather than relying on forum reports. Use the score report's domain breakdown to target the retake.

How long is the credential valid, and how do I renew?

Validity periods differ by provider - some issue lifetime credentials, others require renewal every few years as Cassandra majors advance. Check the certifying body's site for the current validity term and renewal route, which is often continuing education or sitting the current exam version rather than a separate recertification test.

Does the exam test a specific Cassandra version?

Usually it targets a recent stable major release, and the syllabus states which. Version matters: compaction, streaming and authentication defaults have changed across majors. Confirm the mapped version on the provider's site, and make sure your lab cluster runs that version before you rely on memory for defaults.

How much time should I budget for preparation?

It depends on your baseline. A working DBA with a lab habit can usually close the gaps in a few focused weeks of evenings; someone new to Cassandra should plan considerably longer, because the ring and read/write path take repetition to internalise. Track progress by domain, not by hours logged.