Apache Cassandra Developer Associate study materials
Apache Cassandra Developer Associate study resources

Apache Cassandra Developer Associate study plan

Apache Cassandra Developer Associate · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Cassandra Architecture and Data Distribution & Data Modeling and Schema Design

  • Diagram the write path and read path end to end, labeling commitlog, memtable, SSTable, bloom filter, partition index, and cache roles

  • Compute token ownership for a given token range and partitioner using murmur3, and explain how a partition key maps to replicas

  • Distinguish simple, network topology, and rack-aware snitches and predict replica placement for a two-datacenter topology

  • Derive the first-draft table design for a chat application by listing access patterns before choosing keys

Your checkpoint

A one-page architecture diagram plus a written access-pattern list and partition-key choice for two sample use cases, with a short justification for each key decision

Week 2

Data Modeling and Schema Design

  • Model one-to-many and many-to-many relationships using clustering columns, and explain why denormalization replaces joins

  • Choose partition keys that bound partition size, and calculate row counts per partition for a given write rate and retention window

  • Design collection columns and static columns for a concrete schema, and justify when a separate table is better

  • Write the CQL DDL for three tables covering the same domain, each tuned to a different query

Your checkpoint

A schema document for a single domain with three query-specific tables, including primary keys, clustering order, and estimated partition sizes

Week 3

Data Modeling and Schema Design & CQL (Cassandra Query Language)

  • Write SELECT statements that respect partition-key restrictions and explain which WHERE clauses require ALLOW FILTERING

  • Use BATCH for same-partition writes and explain why logged batches across partitions hurt performance

  • Implement lightweight transactions with IF EXISTS and IF NOT EXISTS, and describe the Paxos round trip they trigger

  • Create and query a secondary index and a materialized view, and list the query patterns each one supports poorly

Your checkpoint

A CQL script that creates the week 2 schema, loads at least 1,000 rows, and runs eight queries, each annotated with whether it is partition-efficient and why

Week 4

CQL (Cassandra Query Language) & Performance Tuning and Query Optimization

  • Use TTL, WRITETIME, and timestamps to control data expiry and resolve conflicting writes

  • Read and interpret tracing output and the system_traces tables for a slow query

  • Compare consistency levels ONE, QUORUM, and ALL against replication factor, and compute which combinations tolerate a single node failure

  • Tune a query by changing clustering order or adding a denormalized table, then measure the difference

Your checkpoint

A performance log comparing five queries before and after optimization, with latency numbers, consistency level rationale, and the final schema changes

Week 5

Client Drivers and Application Development

  • Configure a driver session with contact points, load balancing policy, retry policy, and a token-aware policy

  • Implement prepared statements and bound parameters, and demonstrate reuse of a single prepared statement across calls

  • Set per-statement consistency and idempotence flags, and explain how speculative execution interacts with retries

  • Handle pagination of large result sets and apply backpressure with a bounded request queue

Your checkpoint

A working application module in one driver language that performs create, read, update, and delete against the schema, uses prepared statements, sets consistency per operation, and includes a short README of configuration choices

Week 6

Performance Tuning and Query Optimization

  • Read compaction strategy trade-offs for size-tiered, leveled, and time-windowed compaction, and pick one per workload

  • Interpret nodetool tablestats output for read and write latency, SSTable counts, and tombstone counts

  • Diagnose a tombstone-heavy read and propose a fix involving TTL, collection usage, or query pattern

  • Tune the bloom filter, caching, and chunk length settings for a read-heavy table and justify each change

Your checkpoint

A tuning report on one table that names the bottleneck, cites the metric that revealed it, and states the configuration change plus expected effect

Week 7

Operations, Maintenance, and Troubleshooting

  • Run nodetool status, ring, and describecluster, and interpret node states including DN, UJ, and LE

  • Explain repair, hinted handoff, and read repair, and schedule repairs for a given replication factor and window

  • Add a node to a cluster and describe the streaming and bootstrap steps, including what to monitor

  • Back up and restore using snapshots and incremental backups, and verify the restore on a scratch node

Your checkpoint

An operations runbook covering node addition, repair scheduling, snapshot and restore, and a troubleshooting decision tree for high read latency

Week 8

Cassandra Architecture and Data Distribution & Data Modeling and Schema Design & CQL (Cassandra Query Language) & Client Drivers and Application Development & Performance Tuning and Query Optimization & Operations, Maintenance, and Troubleshooting

  • Take two timed practice exams and log every missed question by domain

  • Re-derive the weakest two domain topics from memory without notes, then check against source material

  • Rewrite the week 2 schema to fix every flaw found during review

  • Write a one-page cheat sheet of consistency math, compaction rules, and CQL restrictions

Your checkpoint

A scored practice exam summary with per-domain accuracy percentages, a list of remediation items, and a final revised schema

Milestones

Week 2: Can explain without notes why a chosen partition key bounds partition size, and can draw the token-to-replica mapping for a three-node cluster

Week 4: Scores at least 70 percent on a self-made 30-question quiz covering domains 1, 2, and 3, with all CQL queries running without ALLOW FILTERING

Week 6: Application module runs end to end against a local cluster and the tuning report identifies at least one real bottleneck with supporting metrics

Week 8: Practice exam scores at or above 80 percent overall, with no single domain below 65 percent