Couchbase Developer exam-day guide
Couchbase Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID name that matches your registration. If you are testing online with a remote proctor, confirm with the provider which ID types are accepted and whether a secondary ID is required; do not assume a student card or expired document will pass.
Know your exam appointment details
Record the start time in your local time zone, the test center address or the remote-proctoring check-in link, and the provider's cancellation/reschedule window. Confirm whether check-in opens before the start time and how late you may arrive.
Test your remote setup the day before
If testing online, run the provider's system check for camera, microphone, browser, and bandwidth. Close background apps, disable notifications, and confirm your room can be shown on camera and is free of notes, phones, and second screens.
Charge and tether your equipment
For remote delivery, keep the laptop plugged in and have a phone with data as a backup for check-in or support calls. Have the proctor support number saved in case the session drops.
Review the exam guide and objectives
Re-read the official exam objectives list and map each topic to a Couchbase feature you can explain and use: document modeling, N1QL/SQL++ querying, indexes, SDK usage, and cluster operations. This tells you what the exam covers without relying on any third-party dump.
Practice query and SDK patterns hands-on
Run a local Couchbase instance or a free-tier cluster. Write parameterized SQL++ queries, create and EXPLAIN a secondary index, and perform CRUD plus a bulk operation through an SDK (for example Java, .NET, Node.js, or Python). Recalling syntax under time pressure is the main skill being tested.
Prepare a one-page concept sheet
Summarize items you keep forgetting: consistency levels, scan consistency options, index types (primary, secondary, adaptive, full-text, vector), document key design, TTL, and subdocument operations. Review it before check-in, then store it away during the exam.
Confirm what materials are allowed
Ask the provider whether scratch paper, a pen, a calculator, or documentation is permitted, and whether scratch paper must be destroyed or returned. Policies differ between test-center and remote delivery.
Plan arrival and buffer time
Arrive at the test center early enough to complete ID checks and locker storage. For remote delivery, be seated and logged in before the check-in window closes, with water and a bathroom break handled beforehand.
Know the scoring and retake basics
Confirm the passing score, question count, time limit, and retake policy from the official exam page before test day so you are not surprised by the result screen. Do not rely on numbers from forums.
Plan the day
Switch from reading to doing. Build a small sample application against a local Couchbase cluster: model documents for a realistic domain, write ten SQL++ queries including joins and aggregations, and add the indexes those queries need. Use EXPLAIN to check that each query uses an index rather than a primary scan, and note why each index was chosen. Then review the official objectives list and mark any topic you cannot demonstrate; spend the remaining time only on those gaps.
Do one timed practice run using the provider's sample questions or your own mixed set, then stop adding new material. Re-read your one-page concept sheet, focusing on SDK error handling and retry behavior, consistency and scan consistency, key design and document size limits, and the difference between query service and key-value access. Confirm your appointment time, ID, login link, and travel plan. Sleep on a normal schedule rather than cramming; recall of syntax and API names degrades sharply when you are tired.
Eat a normal meal and avoid starting a large new topic. Skim only your concept sheet. For remote delivery, clear your desk, silence your phone, close all other applications, and start the system check early so a camera or browser problem does not consume exam time. For a test center, leave with enough margin for traffic and check-in. Keep water nearby but follow the provider's rules on drinks.
Read each question fully before answering; many Couchbase questions hinge on one word such as 'consistency', 'atomic', or 'index'. For scenario questions, identify which service is involved (key-value, query, index, search, analytics) before choosing. Answer confident questions first and flag long scenario items to revisit. Eliminate options that describe deprecated or wrong-service behavior. If a question seems to require an exhibit or environment you do not have, use the provider's comment or flag feature rather than guessing blindly. Watch the clock at the halfway point and reserve the last few minutes to review flagged items.
Rules to check
Bring valid government-issued photo ID whose name matches your registration exactly. If you are unsure whether a specific document is accepted, confirm with the provider before test day.
Do not bring or use unauthorized materials: notes, phones, smart watches, second monitors, or any recording device. For remote delivery, keep your phone out of reach unless the proctor instructs otherwise for check-in.
Follow the proctor's instructions during check-in, including room scans and desk clearance. Refusing a requested check can result in the session being terminated.
Breaks are generally not permitted during a timed exam, and the clock typically keeps running. Confirm the provider's break policy in advance and plan hydration and bathroom visits accordingly.
Do not attempt to capture, share, or reconstruct exam questions afterward. Sharing exam content violates the provider's terms and can invalidate your result and future eligibility.
Understand the scoring model before you start: confirm the passing score, whether wrong answers are penalized, and whether questions are weighted. Do not assume unanswered questions are free; if guessing is not penalized, answer every question.
If your session disconnects or the testing software fails, stop and contact proctor support immediately rather than continuing unproctored. Follow the provider's incident process so your attempt is documented.
Report any technical or environmental problem to the proctor as it happens, not after the exam, and keep any case or ticket number the provider gives you.