Confluent Kafka Developer exam-day guide
Confluent Kafka Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Use the exact ID type and name you registered with; the first/last name on the ID must match your registration. If you have a legal name mismatch (e.g., a shortened first name), contact the certification provider before test day to fix it - do not assume the proctor will accept it.
Appointment confirmation and registration email
Have the confirmation email, appointment ID, and the provider portal login handy in case the proctor asks you to verify your session or you need to re-launch the exam.
Working webcam, microphone, and speakers/headset
If you are taking the exam online-proctored, you will typically be photographed and your room may be scanned. Test all three devices before exam day; built-in laptop hardware is fine if it passes the provider's system check.
Stable internet connection plus a backup
Wired ethernet is preferable to Wi-Fi. Have a phone hotspot ready as a fallback, but keep the phone out of reach and off the desk during the exam unless the proctor tells you otherwise.
Provider's secure browser or proctoring software installed and updated
Install and run the required lockdown/proctoring app ahead of time, and complete the official system compatibility test. Confirm with the provider which browser version and OS are supported.
A quiet, private, well-lit room
No other people, no interruptions, and no second monitor. Sit facing the door if possible, and make sure your face and desk area are clearly visible on camera.
Clear desk and cleared room
Remove phones, smart watches, notes, books, printed material, and any second screen from the desk. Whether a physical whiteboard or scratch paper is permitted varies - confirm with the provider and use only what they explicitly allow (often an on-screen notepad instead).
Power adapter and charged laptop
Plug in for the whole session. A mid-exam battery failure costs time you will not get back.
Water in a clear, label-free container
Many proctors allow this, but rules differ - confirm with the provider rather than assuming.
Approved accommodations confirmed in advance
If you need extra time or other accommodations, it must be requested and approved before the appointment. Do not raise it for the first time on exam day.
Refreshed on the exam format
Confirm the current question count, time limit, passing score, and question types (multiple choice vs. multiple select) on the official Confluent certification page - these details change and should not be taken from third-party summaries.
A one-page weak-topic list, reviewed before you sit down
For this exam, typical trouble spots are Kafka Streams state stores and windowing, exactly-once semantics and transactions, consumer group rebalancing and offset commits, schema evolution and compatibility modes, ksqlDB query semantics, and ACL/security configuration. Review your own list, then put it away before the exam starts.
Plan the day
Re-read the official exam guide and confirm the exam's current domain breakdown and format. Run the provider's system test on the exact machine and network you will use. Resolve any ID/name mismatch now, not later.
Do a final pass over your two or three weakest domains. Prefer writing short code sketches (a Streams topology, a producer config block, an ACL command) over re-reading notes - the exam rewards recognizing correct configuration and API behavior.
Take one timed practice set under exam-like conditions if you have access to legitimate practice material, then spend the remaining time only on the questions you got wrong. Stop adding new topics.
Confirm the appointment time and time zone in writing, note the check-in window (typically you should log in well before the start - confirm the exact allowance with the provider), and lay out your ID, charger, and water.
Prepare the room: clear the desk, remove extra screens and devices, check lighting and camera framing. Sleep a full night; do not study past the point of diminishing returns.
Eat, hydrate, and close all other applications on your computer. Disable notifications, auto-updates, and any VPN that might interfere with the proctoring connection.
Do a ten-minute skim of your weak-topic list only - no new material, no panic-driven cramming.
Log in early, complete ID verification and the room scan, and stay reachable by whatever channel the proctor uses. Have your appointment ID ready.
Read each question fully, especially multi-select items and 'which TWO' style prompts - partial credit is usually not awarded, so match the requested number of selections exactly.
Answer or flag every question. On scenario questions, eliminate options that contradict Kafka fundamentals (e.g., ordering guarantees broken by increasing partitions, consumer commits tied to the wrong offset), then choose among the survivors.
Watch the clock: divide remaining time by remaining questions and check in at roughly the one-third and two-thirds marks. If a question is eating more than about 90 seconds, flag it and move on.
Return to flagged questions, make sure nothing is left blank, and submit deliberately. Note the result or next-step instructions shown on screen before closing the window.
Rules to check
Bring a valid, unexpired government-issued photo ID whose name matches your registration exactly. If it does not match, contact the provider before the appointment - resolve this in advance, not at check-in.
The exam is closed-book. Do not use notes, phones, smart watches, second monitors, or third-party browser tabs. Use only the scratch/whiteboard facility the provider explicitly offers; confirm what is allowed with the provider beforehand.
Breaks: policies differ between online-proctored and test-center delivery, and the timer may or may not pause. Confirm the break rule with the provider before exam day and plan to sit through without one.
Stay on camera and in frame for the full session if online-proctored. Leaving the camera view, talking aloud to another person, or having someone enter the room can lead to the session being terminated and the score voided.
Report any technical failure to the proctor immediately through the designated channel. Do not attempt to restart the exam yourself unless instructed - an unreported interruption may not be honored in a later dispute.
Scoring is based only on the questions you answer correctly; unanswered questions count against you, so always guess rather than leave blanks. Passing-score and recertification details should be confirmed with the provider.
Retake and rescheduling terms, plus any waiting period between attempts, are set by the provider and change over time. Confirm the current policy in writing before you rely on it.
Do not discuss, reproduce, or share exam questions afterward - most certification programs treat this as a conduct violation that can void your result and bar future attempts.