GitLab CI/CD Associate exam-day guide
GitLab CI/CD Associate · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID document whose name matches your registration. If your registered name differs in any way (middle name, transliteration, married name), resolve it with the provider before test day rather than at check-in. Confirm with the provider which ID types are accepted for your delivery format (in-person test center versus remote proctored).
Appointment confirmation and test-taker ID number
Have your confirmation email, order number, and any candidate ID ready. For remote delivery you may be asked for a registration or exam access code; confirm with the provider exactly which identifiers appear on your admission notice.
Know your delivery format and its technical requirements
GitLab's associate-level exams are typically delivered as proctored online exams, but delivery arrangements can change. Confirm with the provider whether yours is remote-proctored or at a test center, and read the system requirements (supported browser, webcam, microphone, bandwidth, operating system) in advance.
Run the system or equipment check ahead of time
If remote-proctored, install any required secure browser or proctoring extension and complete the equipment test at least a day early. Test your webcam, microphone, and upload speed from the room you will actually use. A failed check on test morning is hard to fix under time pressure.
Prepare a compliant testing space
Use a private, quiet room with a closed door, a clear desk, and good lighting. Remove secondary monitors, phones, smart watches, notes, and printed material from reach. Confirm with the provider what is allowed on the desk (often nothing but your ID and a transparent water container).
Review the exam's published scope and question format
Re-read the official exam handbook or objectives page for the GitLab CI/CD Associate exam: domains covered, number of questions, time limit, passing score, and whether question types include multiple-choice, multiple-select, or scenario-based items. Do not rely on third-party summaries for these numbers; confirm with the provider.
Know the scoring and retake policy
Understand pass/fail thresholds, when results are released, and whether a retake is permitted and at what cost or waiting period. These terms are set by the provider and can change, so confirm with the provider and note the terms in your confirmation email.
Plan identity and environment verification time
Remote proctoring usually includes ID capture, a room pan, and sometimes a photo of your workspace. Budget 15-30 minutes before your start time so verification does not eat into exam time. Confirm with the provider how early you should launch the session.
Prepare allowed reference material only if explicitly permitted
Most proctored certification exams are closed-book. Do not assume documentation access is allowed just because the exam is about a real product. Confirm with the provider whether any reference material, scratch paper, or calculator is permitted, and in what form.
Stable internet and a backup plan
For remote delivery, have a wired or strong Wi-Fi connection and a phone with a hotspot as backup, kept out of reach unless the proctor directs you to use it. Know the provider's support number or chat in case the session drops.
Water, medication, and accessibility accommodations
If you need breaks, medication, or accommodations (extra time, screen reader, etc.), request them through the provider's formal process well before test day; approvals are rarely granted on the day. Confirm with the provider what is permitted in the room.
A calm review plan, not new topics
In the last day, review your own notes on pipeline structure, .gitlab-ci.yml keywords, runners, and job execution order rather than starting unfamiliar material. Bring a one-page personal summary only if the provider allows notes; otherwise use it before the session starts.
Plan the day
Re-read the official exam objectives and map each domain to your own experience. List the two or three areas where you are weakest, such as rules versus only/except, caching versus artifacts, or runner executor types, and spend focused time there. Rehearse writing a small .gitlab-ci.yml from memory: stages, a job using script, an image, and a rules clause. Confirm your appointment time, time zone, and delivery format in the confirmation email.
Do a full timed practice run under exam-like conditions: closed book, no tab switching, single sitting. Review the questions you got wrong and write a one-line reason for each. If remote-proctored, install and test the proctoring software now, not later. Check that your ID matches your registration name exactly.
Stop learning new material. Skim your own summary of core concepts: pipeline stages, needs and DAG behavior, variables and precedence, predefined variables, cache keys, artifacts and dependencies, environments, and includes. Verify your room setup, charger, webcam, and internet. Confirm the launch window and any check-in instructions. Get a normal night's sleep; sleep is worth more than one more hour of review.
Eat, hydrate, and set up the room early. Close unnecessary applications, silence notifications, and put your phone away unless the proctor instructs otherwise. Have your ID and confirmation details within reach. Log in at the time the provider specifies, complete identity and room verification patiently, and read the instructions screen fully before starting.
Read the exam instructions and note the time limit and question count so you can pace yourself. If the format allows navigation, answer confident questions first and flag uncertain ones. Watch for multiple-select items that ask for all correct answers and for wording like 'which are true' versus 'which is true'.
Pace by dividing remaining time by remaining questions and check your pace at the halfway mark. Read each stem fully, eliminate obviously wrong options, and be careful with keywords such as always, only, and never. For scenario items, identify what the pipeline would actually do at runtime rather than what looks syntactically tidy. If a technical problem occurs, pause and contact the proctor or support immediately rather than troubleshooting alone.
If review is permitted, revisit flagged questions and check that multi-select answers are complete. Do not change answers on a hunch; change only when you can name the reason. Submit before the time limit, confirm the submission screen, and note any instructions about when and how results will be released.
Rules to check
Bring the ID document that matches your registration exactly and present it when asked. If your name or document type is uncertain, confirm with the provider before test day; do not improvise at check-in.
Treat the exam as closed-book unless the provider explicitly states otherwise. Do not use notes, second screens, phones, smart devices, browser tabs, or AI assistants during the session, and do not attempt to capture or share questions.
Stay in view of the camera and in the room for the whole session in remote delivery. Leaving the frame, talking to others, or having another person present is typically treated as a violation; confirm with the provider what movement is permitted for breaks or stretches.
Breaks are usually not allowed during a timed certification exam, and the clock generally keeps running if one is granted. If you need a break for medical or accessibility reasons, arrange an approved accommodation in advance; confirm with the provider.
Scoring is set by the provider, not by GitLab or this guide. Do not assume a passing mark, a result release time, or a retake window; confirm these with the provider and keep your result notice.
Technical failures are handled through the provider's support or proctoring channel. Report the problem immediately, follow their instructions, and keep any case or ticket reference; do not restart the exam on your own initiative without direction.
Do not discuss, publish, or reconstruct exam content afterward, including in study groups or online forums. Respect the confidentiality terms you accept at the start of the session.
Arrive or log in at the time the provider specifies. Late entry may forfeit your appointment or reduce your available time, and rescheduling terms are provider-specific, so confirm with the provider if you anticipate a conflict.