Confluent CCAAK 30-, 60-, and 90-day study plan with topic order, review loops, and final-week priorities.
This page answers the real prep question for CCAAK: how do I organize Kafka admin review so durability, safety, and troubleshooting stay connected instead of becoming a pile of isolated settings?
Use the plan that matches your available time, but tie it to one repeatable admin lab. Each week should include one controlled config change, one health-check pass, one diagnosis drill, and one miss-log review. The loop is: official scope -> lab repetition -> scenario drills -> miss log -> mixed sets.
| Your starting point | Typical total study time | Best-fit timeline |
|---|---|---|
| You operate Kafka weekly (configs, topics, troubleshooting) | 30–50 hours | 30–60 days |
| You’ve supported Kafka but not as a primary owner | 50–80 hours | 60–90 days |
| You’re new to Kafka administration | 80–120+ hours | 90 days |
Choose a plan based on hours per week:
| Time you can commit | Recommended plan | What it feels like |
|---|---|---|
| 10–12 hrs/week | 30‑day intensive | Fast learning + lots of scenario practice |
| 6–8 hrs/week | 60‑day balanced | Steady progress + remediation time |
| 3–5 hrs/week | 90‑day part‑time | Slow-and-solid with repetition |
You do not need a large production-like cluster, but you do need enough surface area to practice safe admin thinking:
Confluent does not publish a public weighted domain table for CCAAK, so use this review order:
Target pace: ~10–12 hours/week. Goal: cover the official scope quickly, then harden instincts through drills and mixed sets.
| Week | Focus | What to do | Links |
|---|---|---|---|
| 1 | Architecture + durability | Master partitions, replication, ISR, acks, and how leader or follower problems surface. | Resources • Cheat Sheet |
| 2 | Config + topic behavior | Learn listeners, storage, safe broker changes, topic configs, retention, compaction, and quotas. | Cheat Sheet • Glossary |
| 3 | Security + connectivity + observability | Drill TLS, SASL, ACLs, listener maps, URP, offline partitions, and controller churn signals. | Resources • Glossary |
| 4 | Troubleshooting + maintenance | Rolling restarts, upgrades, reassignment, lag, disk pressure, and platform-component awareness. Finish with mixed runs and remediation. | FAQ • Glossary |
Target pace: ~6–8 hours/week.
| Weeks | Focus | What to do |
|---|---|---|
| 1–2 | Architecture + health indicators | Build the ISR, leader-election, controller, and replication mental model until healthy vs unhealthy is obvious. |
| 3–4 | Config + topic lifecycle | Broker configs, listener patterns, storage planning, partitions, retention, compaction, and safe changes. |
| 5–6 | Security + connectivity | TLS, SASL, ACLs, inter-broker paths, client endpoints, and least privilege. |
| 7–8 | Troubleshooting + maintenance | Lag, URP, offline partitions, rolling changes, reassignments, upgrades, and mixed scenario review. |
Target pace: ~3–5 hours/week.
| Month | Focus | What to do |
|---|---|---|
| 1 | Fundamentals | Learn partitions, replication, ISR, acks, and core admin health checks; do weekly drills. |
| 2 | Operating Kafka | Broker config patterns, topic management, listener and security basics; practice diagnosis scenarios. |
| 3 | Reliability | Troubleshooting deep dives, maintenance safety, platform components, and final mixed review. |
flowchart LR
A["Read one lesson"] --> B["Run one focused lab action"]
B --> C["Write 3 admin rules"]
C --> D["Do one short scenario set"]
D --> E["Log misses by durability, security, config, or troubleshooting lane"]
Strong admin rules look like this:
protect ISR before optimizing writescheck advertised.listeners before blaming clientsrestore cluster safety before tuning throughput