Study Confluent CCAC Service Accounts and RBAC: key concepts, common traps, and exam decision cues.
This chapter is where many candidates blur identity, authentication, and authorization into one concept. CCAC rewards the operator who can keep those lanes separate and then diagnose failures in the right order.
Service account: Non-human principal used by workloads and integrations.
Role binding: The scope that tells a principal what it may do on the platform.
Confluent’s current public operator framing implies real platform administration. That means you need to know who is acting, how they authenticate, and what they are allowed to do before you touch connectors, clusters, or private networking.
| Lesson | Focus |
|---|---|
| 2.1 RBAC | Distinguish users, service accounts, API keys, and role bindings without mixing them together. |
| 2.2 Triage | Diagnose access failures and fix them with least-privilege discipline. |
| If the question is really about… | Go first to… |
|---|---|
| what a service account or API key actually does | 2.1 RBAC |
| why authentication succeeds but the action still fails | 2.2 Triage |