Elastic Certified Engineer exam-day guide
Elastic Certified Engineer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Use an original, unexpired ID whose name exactly matches your exam registration. The proctor will likely ask you to hold it up to the camera. Which specific ID forms are accepted is set by the provider - confirm before exam day.
Laptop that passes the proctoring system check
Webcam, microphone, speakers/headphones as permitted, and a current version of the supported browser. Run the provider's equipment/system check several days ahead, not on exam morning, so you have time to fix a driver or permission issue.
Stable internet connection with a backup option
Prefer a wired connection or a strong Wi-Fi signal dedicated to you. Have a mobile hotspot or second network available as a fallback, but do not connect it unless your primary link fails. Avoid shared or public networks.
Quiet, private, well-lit room with a clear desk
You will usually need a 360-degree room scan before starting. Remove papers, books, sticky notes, extra devices, and anything with writing on it from the desk and your immediate reach. Tell household members not to enter.
Power adapter and a charged battery
Run on mains power with the battery as backup. Disable sleep, screen dimming, and automatic updates so the machine does not interrupt the session.
Appointment confirmation and access instructions
Have the confirmation email, exam link, login credentials, and any candidate handbook open in a place you can reach without leaving the room. Double-check the start time in your local time zone.
All other applications closed
Quit chat clients, email, VPNs, sync tools, and notification pop-ups before the proctor check. Proctoring software commonly flags background windows and pop-ups.
Secondary monitors disconnected
Unplug external displays and mirror or extend settings so only the laptop screen is active. A second visible screen is a standard reason for a session to be voided.
Phone silenced and physically out of reach
Put it in another room or a drawer, not on the desk. Confirm with the proctor where it should be before the session begins.
Water in a clear, unlabeled container
Drinks are commonly allowed but the container usually must be transparent and free of labels. This varies by provider and by proctor - confirm rather than assume.
Confirmation of whether notes, scratch paper, or documentation access is permitted
Do not assume you can consult the Elastic documentation, take handwritten notes, or use scratch paper. This is a provider policy and can change - verify it in the candidate handbook before relying on it.
Hands-on fluency with the Elasticsearch REST API
Rehearse the operations you will perform under time pressure: index creation with explicit mappings and settings, _reindex, aliases, ILM policies, ingest pipelines, snapshot/restore, and compound queries plus aggregations. Know the request bodies well enough that you are typing them, not reconstructing them.
Plan the day
Do one full timed dry run under exam-like constraints: a single sitting, a blank cluster, a hard clock, and only the resources you expect to have. Score yourself and note which categories (mappings, ingest, ILM, queries/aggregations, cluster operations) cost you the most time and target those.
Run the provider's equipment and system check on the exact laptop, browser, and network you will use. Confirm the appointment date, time, and time zone, and read the candidate handbook for permitted-materials and break rules.
Make sure your practice environment resembles the real one: you should be comfortable starting/stopping Elasticsearch, editing config files (elasticsearch.yml, JVM options), and reading logs, not only running queries.
Re-test hardware, internet, and the exam login page. Charge everything and locate your ID. Set the room up as it will be: cleared desk, monitor disconnected, phone stowed. Prepare the confirmation email and credentials.
Stop learning new topics. Do light review of command syntax you use often, then sleep on a normal schedule. Fatigue is a bigger risk than a missing fact in a hands-on exam.
Eat and hydrate before the session, since you may not be able to step away. Log in 15-30 minutes early to absorb any queueing or setup delay, complete the ID check and room scan, and close every background application.
Skim the whole task set before starting so you can sequence the quick wins. Read each task twice and note exact index names, field names, and required output formats - a correct solution that uses the wrong index name still scores zero.
Budget the clock per task and keep a running tally. If a task resists for more than a few minutes, mark it and move on; come back after banking the easier points. Verify each result with a targeted _cat, _search, or _cluster/health check rather than assuming it worked.
Reserve the last portion of your time to revisit skipped tasks and to confirm that persistent state (settings, aliases, policies, templates) is actually saved. Submit before the clock runs out - confirm the submission action with the proctor or interface rather than waiting for an automatic end.
Rules to check
Present original government-issued photo ID whose name matches the registration. The proctor may also ask you to pan the camera around the room, including under the desk.
You must be alone in the room for the entire session. No talking, no coaching, no other people entering. Phones must be silenced and out of reach.
Only permitted materials may be on the desk. No secondary monitors, no handwritten notes, no reference material unless the provider explicitly allows it - confirm the permitted-materials list in the candidate handbook.
Exam content is confidential. Do not screenshot, copy, transcribe, or share any task text during or after the session.
Breaks are typically not permitted, and if one is granted the exam clock usually keeps running. Confirm the break policy with the provider before you depend on taking one.
Scoring is generally task-based, with each task graded pass or fail rather than for partial credit, against a fixed passing threshold. Confirm the exact threshold, score report timing, and retake policy with the provider.
If your connection drops or the environment misbehaves, stop and contact the proctor immediately rather than troubleshooting silently. Whether lost time is restored is at the provider's discretion - confirm in advance so you know what to expect.
Technical problems on your own equipment are generally your responsibility. That is why hardware, network, and system checks belong in the days before, not the minutes before.