GitHub Actions exam-day guide
GitHub Actions · Prepare for the day ahead.
Your checklist
Valid government-issued photo ID
Bring the exact ID type and name spelling the test provider requires (for online proctoring, usually a passport or government ID; for a test center, often a driver's license or passport). The name must match your registration. Confirm the accepted ID types and any name-mismatch policy with the provider before booking travel.
Exam appointment confirmation and login credentials
Have your confirmation email, candidate ID, and provider account password ready. For remote delivery, test your login on the same browser and device you will use. Do not rely on autofill or a password manager that may prompt for re-authentication mid-exam.
Working webcam, microphone, and speakers/headset
Remote-proctored exams typically require a webcam that can pan the room and a microphone for the proctor check-in. Run the provider's system test at least 24 hours ahead. Keep a wired headset as a backup if wireless audio is unreliable.
Stable internet connection with a backup plan
Prefer a wired Ethernet connection or a strong Wi-Fi signal. Identify a backup: a mobile hotspot, a second device, or a nearby test center. Know the provider's policy on disconnections and whether lost time is restored - confirm with the provider.
Compatible browser and updated operating system
Many proctoring platforms require a specific browser version and block certain extensions or virtual machines. Check the provider's technical requirements page and update your browser and OS before exam day. Disable VPNs and screen-sharing tools unless the provider says otherwise.
A quiet, private, well-lit room
Clear your desk of papers, phones, and smart devices unless explicitly allowed. Tell household members not to enter during the exam. A room scan is commonly required at check-in; make sure the space is easy to show on camera.
Permitted reference materials, if any
GitHub Actions exams may or may not allow documentation, notes, or a second monitor. Do not assume. Check the provider's exam rules and the specific exam guide for what is allowed. If open-book is permitted, prepare only approved resources.
Scratch paper and pen/pencil if allowed
Some proctored exams allow blank paper that must be shown to the camera before and after. Confirm the rules; if not allowed, plan to reason on screen. For GitHub Actions questions, sketching a workflow trigger-to-job flow on paper helps, so know in advance whether you can.
Water and a light snack for scheduled breaks
Check whether breaks are permitted and whether the clock stops. If breaks are allowed, keep items within reach so you do not need to leave the camera view unexpectedly. Confirm break rules with the provider.
A watch or visible clock
Many exam interfaces include a timer, but a backup clock helps pace section timing. Do not wear a smartwatch; analog watches may also be restricted - confirm with the provider.
Review of the exam's domain weighting and question format
Before exam day, re-read the official exam guide for the domains covered (workflow syntax, triggers, runners, secrets, reusable workflows, matrix builds, caching, artifacts, security hardening) and the question types. Knowing the weighting helps you allocate time.
Emergency contact and provider support number
Save the provider's technical support contact in case of login, proctoring, or connectivity failure. Know whether support is available during your appointment window.
Plan the day
Confirm logistics: appointment time zone, delivery method (test center vs. remote), ID requirements, and permitted materials. Re-run the provider's system test on your final device and browser. Resolve any name mismatch or scheduling issue now, not on exam day.
Do a focused review of weak domains rather than re-reading everything. For GitHub Actions, practice writing workflow YAML from memory: on triggers (push, pull_request, schedule, workflow_dispatch, workflow_call), jobs, steps, uses vs. run, env scoping, matrix strategy, needs dependencies, conditional if expressions, and concurrency. Check your answers against the official documentation.
Review security and operations topics you are likely to be tested on: secrets and environments with protection rules, GITHUB_TOKEN permissions, OIDC for cloud authentication, pinned action versions, caching with actions/cache, artifacts with upload/download-artifact, and reusable workflows vs. composite actions. Note where you are unsure and flag those for a final pass.
Stop learning new material. Do a light review of your own notes and the official exam guide. Prepare your workspace: clear the desk, charge devices, test webcam and microphone, and confirm the room will be quiet at your appointment time.
Prepare your ID, confirmation email, and login credentials in one place. Set two alarms. Get a full night's sleep; avoid cramming late, which hurts recall more than it helps.
Eat a normal meal and hydrate. Log in 15–30 minutes early for remote proctoring check-in (room scan, ID check, system checks). Close all other applications and browser tabs. Keep your phone out of reach unless the proctor instructs otherwise.
Read each question fully before answering. For workflow questions, identify the trigger, the job dependency graph, and the permission/secret context before choosing. Watch for distractors that use valid-looking but incorrect syntax, wrong event names, or deprecated action versions.
Pace yourself against the number of questions and remaining time. If a question is taking too long, mark it and move on; return later. Use any review/flag feature to revisit uncertain items. Leave a few minutes at the end to check for unanswered questions.
If the connection drops or the proctor interrupts, stay calm and follow the provider's reconnect procedure. Note the time and contact support if the session does not resume. Do not open other applications while waiting.
Rules to check
Present the exact ID required by the provider; the name must match your registration. If your ID name differs from your registration, resolve it before exam day - confirm the provider's policy for name changes and ID exceptions.
Follow the proctoring rules precisely: no unauthorized people in the room, no phones or smart devices within reach, and no leaving the camera view without permission. Violations can lead to score cancellation.
Do not use unauthorized materials, notes, second monitors, virtual machines, or AI assistants. Whether documentation is allowed varies by exam and provider; confirm the specific rules in advance and treat anything not explicitly permitted as prohibited.
Understand the break policy before you start: whether breaks are allowed, whether the clock runs during them, and what you must do on camera. Confirm with the provider if the rules are unclear.
Know the scoring model: whether the exam is pass/fail with a scaled score, whether partial credit applies to multi-select questions, and whether incorrect answers are penalized. Do not guess at the passing score; check the official exam guide.
If you believe a question is defective or the environment failed, note the details and report it to the proctor or provider support. Do not attempt to fix technical issues by opening unapproved tools.
Arrive or log in early. Late arrivals may be refused entry or have time deducted, depending on provider policy - confirm the grace period with the provider.
Keep communication with the proctor professional and follow instructions immediately. If you need to speak, ask permission first, since some sessions record audio.