IBM DevOps and Software Engineering exam-day guide
IBM DevOps and Software Engineering · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact name matching your registration. Most remote proctoring vendors also accept a passport or national ID; if your only ID is a driver's license from a different region, confirm with the provider before test day rather than assuming it will be accepted.
Stable internet connection and a backup plan
Wired ethernet is safer than Wi-Fi. Have a phone hotspot or a second network ready, and know how to reconnect if the proctor session drops. Test your upload and download speed the day before using the provider's system check.
Working webcam, microphone, and speakers
Remote proctoring typically requires a 360-degree room scan at the start. Built-in laptop hardware usually works, but external webcams are often clearer. Test each device in the system check so you are not troubleshooting during check-in.
Quiet, private, well-lit room
Clear the desk of papers, books, phones, and second screens. The proctor will ask you to show the walls, desk surface, and floor. Sit facing a door that others will not open during the exam.
Provider system check completed
Run the official compatibility test on the same machine and network you will use on exam day. This catches browser, firewall, and permission issues early. Confirm with the provider which browsers are supported.
Account credentials and registration confirmation
Know your login for the certification provider's portal and have the confirmation email accessible on a device other than the one you are testing on. Do not store passwords only in a browser profile you may need to sign out of.
Review the exam guide for the current blueprint
The DevOps and Software Engineering credential is built around a multi-course professional certificate, so the assessed domains span DevOps culture, CI/CD, containers, cloud-native development, and agile/Scrum fundamentals. Confirm the current domain weightings and question count with the provider; do not rely on older third-party summaries.
Practice with hands-on tooling, not just reading
Expect scenario questions on Git branching and merge conflicts, writing a Dockerfile, Kubernetes objects such as pods and deployments, CI/CD pipeline stages, and basic test-driven development. Be able to read a short pipeline or YAML snippet and predict the outcome.
Know the difference between similar concepts cold
Common traps include continuous delivery versus continuous deployment, containers versus virtual machines, a Docker image versus a running container, and Scrum roles versus artifacts. Write one-line distinctions for each and review them the morning of the exam.
Sleep, water, and a light meal
Do not schedule a heavy meal or a late-night cram session immediately before the test. Fatigue is the most common cause of misreading a scenario question.
Provider break and timing policy confirmed
Whether scheduled or unscheduled breaks are allowed, and whether the clock stops, varies by vendor. Confirm with the provider in advance rather than planning a mid-exam break. needs_review
Scratch materials policy confirmed
Some proctors allow an erasable whiteboard or a single sheet of paper; others allow none. Confirm with the provider and clear anything unapproved from your desk before check-in. needs_review
Plan the day
Do a full timed practice run of 40 to 60 mixed questions covering all domains, then review every wrong answer against the official course material. Identify your two weakest areas and spend the remaining time there rather than re-reading what you already know.
Re-read your own one-page cheat sheet of distinctions: delivery versus deployment, image versus container, pod versus deployment, and the Scrum roles and ceremonies. Rewrite it from memory and compare.
Run the provider's system check on your final machine and network. Update the browser, grant camera and microphone permissions, and close background apps that could trigger a proctor flag.
Confirm your appointment time in your own time zone, the check-in window, and the ID requirements. Set two alarms. Tell anyone in your household not to enter the room during your slot.
Do light review only: skim your cheat sheet and the domain weightings. Stop studying at least a few hours before bed. Do not attempt new hands-on labs the night before; a broken environment adds stress without adding points.
Eat, hydrate, and do a ten-minute review of your distinction sheet. Log in early, complete the room scan calmly, and follow the proctor's instructions exactly. Have your ID out and your desk already clear.
Read the full scenario before the answer choices; many questions hinge on one qualifier such as 'least privilege' or 'fastest feedback.' Answer confident questions first, flag long scenario items, and return to them with remaining time. Eliminate obviously wrong options before guessing, and never leave a blank if there is no penalty for guessing.
Check that every question is answered, re-read flagged items once, and only change answers when you can point to a specific reason. Submit and note any score report details the provider gives you.
Rules to check
Bring the exact ID the provider requires, with a name matching your registration. If your ID name differs from your registration, resolve it with the provider before test day; proctors generally cannot admit you otherwise.
The room must be private for the entire session. No other people, no second monitors, no phones within reach, and no notes unless the provider explicitly permits them.
Remote sessions are typically recorded and monitored. Do not talk aloud to yourself, cover the camera, or leave the frame without telling the proctor first.
Breaks are governed by the provider's policy and may not stop the clock. Confirm the rules in advance and plan to finish in one sitting if breaks are not allowed. needs_review
Scoring is usually reported on a scaled range with a passing threshold set by the provider. Confirm the current passing score and whether wrong answers are penalized before you decide whether to guess. needs_review
Technical failure is not automatically a free retake. If your connection drops, follow the provider's reconnect procedure and document what happened; ask the proctor to note the incident.
Do not discuss, reproduce, or share exam content afterward. Most certification agreements prohibit disclosing question content, and doing so can void your result.
Arrive or log in before your appointment time. Late arrivals may lose their slot or have time deducted, so treat the check-in window as part of the exam.