GitLab CI/CD Specialist exam-day guide
GitLab CI/CD Specialist · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original, physical ID (passport or national ID card) whose name matches your registration exactly. A photocopy or a digital image on your phone is usually rejected. If your ID name differs from your registration, confirm with the provider before exam day how to resolve the mismatch.
Exam appointment confirmation
Have the confirmation email or booking reference accessible. For remote proctoring you often need the registration link or access code from that email, so keep it reachable from a second device in case the test machine is locked down.
Working webcam, microphone, and speakers
Remote-proctored exams typically require a live camera, a microphone, and audio output for the proctor to communicate with you. Test all three in the same room and on the same machine you will use. Headphones are often restricted, so confirm with the provider which audio devices are permitted.
Stable internet connection with a backup
Wired Ethernet is more reliable than Wi-Fi. Have a phone hotspot as a fallback, and know how to switch networks quickly. Run a speed and latency check the day before.
Clean, private, well-lit room
The proctor usually requires a closed door, a clear desk, and no other people present. Overhead lighting plus a desk lamp reduces the risk of a failed room scan. Remove notes, second monitors, and printed material from the desk unless the provider explicitly allows them.
System compatibility check completed
Most providers supply a browser or app compatibility test that checks the secure browser, camera, and network. Run it at least 24 hours ahead so you have time to fix driver or permission problems. Confirm with the provider whether a secure browser must be installed in advance.
Know the allowed-resources policy for this exam
Whether you may use GitLab documentation, a second screen, scratch paper, or a terminal during the test varies by provider and exam version. Do not assume; confirm with the provider in writing and note the answer. If open documentation is allowed, pre-organize bookmarks so you do not waste time searching.
Scratch paper and pen (if permitted)
Some proctors allow blank paper that must be shown on camera before and after the test. Others forbid it entirely. Confirm with the provider, and if allowed, bring a few blank sheets with nothing pre-written.
Water in a clear container
Many proctoring services allow a transparent bottle or glass but ban labeled or opaque containers. Confirm with the provider; if unsure, skip it to avoid a conduct flag.
Review of core CI/CD concepts, not just memorization
Be ready to reason about .gitlab-ci.yml structure, stages, jobs, rules and only/except, needs and DAG pipelines, caching versus artifacts, environments and deployments, protected branches and variables, runners and executors, and pipeline efficiency. Practice reading a pipeline config and predicting execution order.
Plan for time and question navigation
Note the number of questions and total time, then compute a rough per-question budget. Decide in advance how you will handle flagged questions and whether you can return to them. Confirm the review-and-flag behavior with the provider if it is not documented.
Backup power and device plan
Charge laptop and phone, and know where the charger is. If power or internet fails, you generally must contact the proctor or support immediately rather than continue offline. Confirm with the provider what the reconnect and incident process is.
Plan the day
Confirm the appointment time, time zone, and delivery format (remote proctored or test center). Re-read the provider's candidate handbook for ID, room, and allowed-resource rules, and email support with any ambiguity so you have a written answer. Run the system compatibility check once to surface problems early.
Do a focused content pass on your weakest areas rather than re-reading everything. For a GitLab CI/CD exam that usually means pipeline configuration semantics: rules versus only/except, needs and DAG behavior, cache versus artifacts scope, and how protected variables and environments gate deployments. Write a one-page summary in your own words.
Take one timed practice set under exam-like conditions to calibrate pacing. Record how long each question type takes and identify where you lose time. Do not cram new topics after this point; consolidate instead.
Re-run the compatibility check on the exact machine and network you will use. Update the browser and OS only if the check requires it, then re-test. Clear desk space, set up lighting, and confirm the room meets the privacy requirement.
Prepare logistics: ID out, confirmation email accessible, charger located, backup hotspot tested, water and permitted scratch paper ready. Get a full night of sleep; avoid last-minute studying past the evening.
Eat normally and avoid heavy caffeine if you are sensitive to it. Do a five-minute review of your own summary page only. Log in early, complete any identity verification and room scan, and keep your phone nearby but silenced and out of reach unless the proctor instructs otherwise.
Read each question fully before answering, especially scenario questions with a 'most likely' or 'best' qualifier. Answer confident questions first, flag uncertain ones, and return to them. For pipeline questions, mentally trace stage order and needs relationships before choosing.
Watch the clock at the halfway point and adjust pace. If a technical failure occurs, stop and contact the proctor or support immediately; do not attempt to fix it silently. Use any permitted break only as the rules allow, and note your remaining time afterward.
Note which topics felt weak while memory is fresh, in case a retake is needed. Confirm with the provider how and when results are delivered and what the retake policy is; do not assume a score is final until you receive official notice.
Rules to check
Bring original government-issued photo ID matching your registration name. If the names differ or your ID is expired, confirm with the provider before exam day; do not rely on a workaround at check-in.
Follow the provider's rules on allowed resources exactly. Whether documentation, a second monitor, scratch paper, or a terminal is permitted varies; get written confirmation rather than guessing, and treat any unlisted aid as prohibited.
Stay in view of the camera and in the room for the duration unless a break is explicitly permitted. Leaving the camera view or having another person enter the room is commonly treated as a conduct violation.
Do not communicate with anyone but the proctor during the test, and do not screenshot, copy, or share exam content. Reproducing questions afterward may breach the candidate agreement.
Breaks are usually limited and may not pause the timer. Confirm with the provider whether breaks are allowed, how many, and whether the clock stops; plan hydration and restroom visits accordingly.
Scoring and pass marks are set by the provider and may be scaled or criterion-referenced. Do not infer a pass from a raw count; confirm the scoring method and result timeline with the provider.
If a technical failure or rule ambiguity arises, pause and contact the proctor or support immediately and keep any reference number. Self-troubleshooting that takes you off camera can be misread as a violation.
Report any suspected exam-content leak or irregularity to the provider. Attempting to obtain live questions or answers is grounds for disqualification and undermines the value of the credential.