Elastic Certified Observability Engineer exam-day guide
Elastic Certified Observability Engineer · Prepare for the day ahead.
Your checklist
Confirm exam delivery format and platform requirements with the provider
This is a hands-on, performance-based certification. Before booking day, confirm with the provider (Elastic's certification partner) whether your sitting is remote-proctored or at a test center, which browser/OS versions are supported, and whether any environment check must be completed in advance. Policies change; do not rely on forum posts. Mark as needs_review until you have the current candidate handbook in hand.
Government-issued photo ID matching your registration name
Use the exact name on your registration. If your ID uses a different script or a shortened name, contact the provider support before exam day to reconcile it. Proctors typically reject mismatches, and a rejected check can consume your attempt.
Stable wired-or-strong Wi-Fi connection plus a backup tethering option
A remote-proctored hands-on exam streams a live desktop and proctor video. Test your upload speed and latency the day before. Have a phone hotspot ready as a fallback, but confirm with the provider whether switching networks mid-exam is permitted.
Working webcam, microphone, and speakers/headset
The proctor needs to see your room and hear you during the identity check. Confirm acceptable headset types with the provider; some proctors disallow certain wireless devices. Test all peripherals in the same room you will sit the exam.
Clear, private room with a door you can close
Remove notes, second monitors, printed material, and anything with writing from the desk and walls within camera view. The proctor will ask for a 360-degree room scan. Tell household members the time window so no one enters.
Review the current exam objectives and domain weightings from the provider
The Elastic Certified Observability Engineer blueprint covers areas such as data ingestion with Elastic Agent and integrations, metrics and logs pipelines, APM, synthetic monitoring, uptime, alerting, and dashboards. Confirm the exact domain list and weighting with the provider, since blueprints are revised periodically.
Hands-on practice with a running Elastic Stack cluster you built yourself
The exam is task-based on a live cluster. Practise the full loop repeatedly: enroll an Elastic Agent, add an integration, verify data in Kibana, build a dashboard, create an alert rule, and configure an APM agent. Speed comes from muscle memory in Kibana, not from reading.
Know your way around Kibana without searching the UI
Be fluent in Discover, Lens, Dashboards, the Integrations app, Fleet, Observability apps (APM, Uptime, Infrastructure, Logs), and the alerting rule editor. Practise creating a rule from a query and from an APM threshold so you can do it under time pressure.
Comfort with the Elasticsearch APIs you will likely need
Practise index templates, index lifecycle management, index mappings, and basic search/aggregation queries via the Dev Tools console. You may need to inspect or fix an index rather than click through Kibana.
Time-boxed mock run using only official documentation
Do at least one full-length practice session with a timer, working only from the official Elastic documentation you are allowed to consult. This builds realistic pacing and reveals which topics slow you down.
Confirm what reference material is allowed during the exam
Many hands-on certifications permit the vendor's official documentation but not third-party sites, notes, or AI assistants. Confirm the exact allowed-resources list with the provider and close every other tab and application before the session starts.
Water, snacks, and a plan for breaks
Confirm with the provider whether unscheduled breaks are allowed and how they affect your clock. If breaks are restricted, eat and hydrate before you start and keep water in a clear container if permitted.
Plan the day
Do a final gap analysis against the current blueprint. List every objective and rate your confidence 1-5. Spend the remaining time only on the 1s and 2s. Resist the urge to re-study what you already know; breadth of hands-on tasks beats depth on one feature.
Rebuild your practice cluster from scratch once, end to end: install, enroll an agent, add an integration, ship logs and metrics, instrument a sample app with APM, and create a dashboard and an alert. Doing the whole flow in one sitting exposes integration points that isolated tutorials hide.
Run a timed mock under exam-like conditions, using only the official documentation. Track how long each task type takes. If a single task type eats more than a quarter of your time, drill it specifically the next day.
Do a light review of your weak list and the official docs' table of contents so you know where things live. Knowing the documentation structure is worth more than memorizing syntax, because you can look things up during the exam.
Complete any provider-required system check and identity verification steps. Confirm your login credentials, the session start time in your local time zone, and the check-in window. Verify your ID name matches the registration.
Prepare the room and equipment: clear the desk, charge devices, test the webcam and mic, and confirm the network. Sleep a full night. Fatigue is the most common cause of careless errors on a timed hands-on exam.
Eat properly, hydrate, and avoid starting any heavy downloads or updates on your network. Close all applications except those the provider requires. Have your ID and any permitted materials within reach but off the desk until the proctor approves them.
Join the check-in early. Proctor queues can be long, and the identity and room scan takes time. Starting late eats into your working clock, which is the one resource you cannot recover.
Read the whole task list first if the platform allows it. Knock out the tasks you can complete quickly to bank points, then return to the harder ones. Do not leave a task blank if partial credit is possible; confirm the scoring model with the provider beforehand.
Work in the actual Kibana and Elasticsearch interfaces rather than trying to recall exact menu paths. Use the official documentation search for API syntax and configuration keys. Verify each task's result in the UI before moving on, because a half-configured pipeline often scores zero.
Watch the clock and reserve the last portion of your time for verification and for any tasks you flagged. If you get stuck on one problem, note it and move on; a single stubborn task should not consume the whole attempt.
Note which task types felt slow while it is fresh, since that is your study list if you need to retake. Confirm with the provider how and when results are delivered and what the retake policy is.
Rules to check
Bring government-issued photo ID with a name that exactly matches your registration; confirm accepted ID types with the provider before exam day.
Confirm with the provider which resources are permitted during the exam (for example, official vendor documentation versus third-party sites, personal notes, or AI tools), and close anything not permitted before check-in.
Stay within the camera's view for the entire session unless the proctor explicitly permits otherwise; confirm the break policy with the provider, since unscheduled breaks may be recorded or may not stop your clock.
Do not communicate with anyone outside the session, and do not let another person enter the room. The proctor can invalidate an attempt for a room-scan or conduct violation.
Treat all exam content as confidential. Do not copy, screenshot, record, or share tasks or environment details; doing so typically breaches the candidate agreement and can void your certification.
Confirm the scoring model and passing threshold with the provider rather than assuming partial credit; plan your time so every task gets at least an attempt and a verification pass.
If a technical failure occurs, stop and contact the proctor immediately through the platform's support channel rather than troubleshooting silently; confirm the incident-reporting procedure with the provider in advance.