Istio Certified Associate exam-day guide
Istio Certified Associate · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID name you registered with; mismatches are the most common cause of admission problems. For online proctoring, use the original document, not a photocopy or phone image. Confirm with the provider which ID types are accepted for your delivery mode.
Exam appointment confirmation and provider login
Know your appointment time in local time, your candidate ID, and the portal URL. Verify your login works 24h ahead so you are not resetting a password minutes before start.
Stable internet connection with a wired fallback
For remote-proctored delivery, a wired Ethernet connection or a strong dedicated Wi-Fi network is safer than shared or mobile hotspot connections. Run the provider's system test on the same machine and network you will use on exam day.
Working webcam, microphone, and speakers/headset
Remote proctoring typically requires a webcam pan of the room and an audio check. Test all three devices in the provider's system check. Exact device requirements: confirm with the provider.
Clean, quiet, private room
Clear your desk of papers, books, phones, and second screens unless the provider explicitly permits specific items. Tell household members not to enter. Wall posters or notes within camera view may need to be removed or covered; confirm the provider's room rules.
Second screen and extra devices disconnected or powered off
Unplug external monitors and put phones out of reach, not just face down. Proctors commonly flag visible extra devices even when unused.
Remote-desktop, VPN, and screen-sharing software disabled
Proctoring tools often block or flag these. Close them before launching the exam and confirm whether a VPN is permitted; if unsure, confirm with the provider.
Allowed materials list verified in advance
Istio certification exams are generally closed-book with no notes or documentation, but do not assume: check the provider's candidate handbook for the exact allowed-items list. If the exam permits a whiteboard or blank paper, have it ready and show it to the proctor when asked.
Water in a clear container and any permitted comfort items
Policies on drinks, snacks, and medication vary. Check the handbook; if your situation is not covered (for example, medical accommodation), request it well before exam day and confirm with the provider.
Knowledge of the break policy before you start
Know whether breaks are allowed, whether the clock stops, and how to request one. Do not leave the camera view without proctor permission. Exact break rules: confirm with the provider.
Scratch strategy for Kubernetes and Istio command syntax
You cannot rely on notes, so rehearse from memory the commands you use most: kubectl get/describe/logs/exec, istioctl analyze, istioctl proxy-status, istioctl proxy-config, and istioctl x describe. Practice typing them quickly in a plain terminal.
Plan for a technical failure
Know the provider's support contact and reconnect procedure before you begin. If the session drops, do not start a second attempt on your own; contact support so the incident is logged. Refund and reschedule rules: confirm with the provider.
Plan the day
Re-read the official exam objectives and map each domain to what you can actually do without notes. For Istio, that means traffic management (VirtualService, DestinationRule, Gateway), security (PeerAuthentication, RequestAuthentication, AuthorizationPolicy, mTLS), observability (telemetry, access logs, Kiali, Prometheus/Grafana), and installation/configuration with istioctl and the operator. List weak areas and spend the remaining time there, not on material you already know.
Do hands-on drills on a local cluster (kind or minikube with the Istio addon or a manual install). Practice installing Istio with a specific profile, enabling strict mTLS, splitting traffic between two versions with weights, adding a retry or timeout, injecting faults, and reading the result with istioctl and Kiali. Practical recall of manifests and CLI flags is worth more than reading.
Run the provider's system check on your exam machine, update the proctoring browser extension if required, and confirm your appointment time in your own time zone. Fix any camera, microphone, or network issue now rather than on exam morning.
Do one light review pass over your own summary of manifests and commands. Stop heavy study in the evening. Sleep is the highest-return preparation for a scenario-based exam.
Prepare your workspace: clear the desk, remove or cover notes in camera view, charge devices, and locate your ID. Confirm the room will be private at your appointment time and tell household members the schedule.
Re-check the provider portal for any change to your appointment, the launch link, and support contact details. Note the exact check-in time; many providers require you to start check-in before the appointment time. Confirm with the provider how early to log in.
Eat, hydrate, and use the restroom before check-in, since breaks may be limited. Avoid starting any large downloads or updates on your network.
Close all other applications, disable notifications, disconnect extra monitors, and restart the machine if you have time. Launch the exam through the provider's official link only.
Complete ID verification and the room scan exactly as the proctor instructs. If the proctor asks you to adjust the camera or show the desk, do it calmly and fully; delays here eat into your time.
Read each question fully before answering, especially multi-select items that ask for two or three correct options. Note whether the exam penalizes wrong answers on multi-select; if that is unclear, confirm with the provider, and otherwise answer only what you are confident in.
For scenario questions, identify the Istio resource that owns the behavior. Traffic routing and retries belong in VirtualService; subsets, load balancing, and connection pool settings belong in DestinationRule; workload identity and mTLS belong in PeerAuthentication; request-level allow/deny belongs in AuthorizationPolicy. Reason from ownership before recalling syntax.
Manage the clock: note the number of questions and total time at the start, set a per-question budget, and flag long scenario items to revisit. Never leave a single-select question blank unless the exam explicitly penalizes guessing.
If a question seems to depend on a version-specific default (for example, default profile behavior or sidecar injection settings), answer from the behavior described in the question rather than from an assumed version. If a scenario is genuinely ambiguous, choose the most standard, least surprising Istio behavior.
If the session freezes or disconnects, stay calm, do not open new browser tabs, and contact proctor support through the official channel. Note the time and what you were doing so the incident can be documented.
Rules to check
Follow the provider's candidate agreement exactly; it governs conduct, and violations can void your result. Read it before exam day rather than skimming it at check-in.
Present valid government-issued photo ID matching your registration. If your ID name differs from your registration, resolve it with the provider before the appointment; do not attempt the exam with mismatched details.
Keep the camera on and remain in view for the entire session unless the proctor explicitly permits otherwise. Do not leave the room, cover the camera, or let another person enter.
Do not use unauthorized materials, notes, second screens, phones, or communication tools, and do not attempt to capture, record, or share exam content. Istio certification exams are generally closed-book; verify the allowed-items list with the provider.
Request breaks only through the proctor and follow the stated policy on whether the timer continues. Exact break rules vary; confirm with the provider.
Scoring is typically criterion-referenced against a passing score set by the certification body, and results are usually reported by domain. Do not assume partial credit on multi-select items; confirm the scoring and retake policy with the provider.
Report technical problems immediately through the official support channel and keep any case or ticket reference. Self-initiated restarts or second attempts can complicate your result.
Do not disclose exam content afterward. Treat question wording and scenarios as confidential, and rely on the published exam objectives for study planning instead.