GitLab Git Associate exam-day guide
GitLab Git Associate · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original, unexpired ID whose name matches your exam registration exactly. If your registration name differs from your ID (for example, a shortened first name or a maiden name), confirm with the provider before test day how to reconcile it, since mismatches can block entry.
Exam appointment confirmation and login details
Save the confirmation email and any candidate portal credentials offline (a screenshot or PDF works). You may need the appointment ID, a scheduling code, or a link to launch the proctored session. Confirm with the provider which of these is actually required for your delivery format.
System or environment requirements checked
If you are testing remotely, run any required system check in advance: browser version, webcam, microphone, and a stable connection. If testing at a center, confirm the address, arrival time, and what the center allows into the room. Requirements vary by delivery mode, so verify with the provider.
Quiet, private room with a clear desk (remote testing)
Remove papers, phones, second monitors, and anything on the walls that could be read as notes. Proctors commonly ask for a 360-degree room scan. Confirm the provider's specific room and desk rules beforehand.
Knowledge of allowed materials
Assume the exam is closed-book unless the provider states otherwise. Git commands, flags, and CI/CD keywords must come from memory. If you believe a reference sheet or on-screen notepad is permitted, confirm with the provider rather than assuming.
Review of the published exam domains and weightings
Re-read the official content outline so your final study hours go to the highest-weighted areas. Use the outline to decide what to skip in the last 72 hours; do not try to learn brand-new topics at this stage.
Hands-on practice environment ready
Have a local Git installation and, if possible, access to a GitLab instance (self-managed or a trial) so you can rehearse commands and pipelines. Practical recall of command syntax is more reliable than reading notes.
Time and break plan
Know the total exam time and whether breaks are allowed and how they affect the clock. Confirm with the provider whether unscheduled breaks are permitted, since some proctored exams treat leaving the view as a violation.
Scoring and retake policy understood
Know the passing score, question format, and whether results are immediate or delayed. Confirm retake rules and any waiting period with the provider; do not rely on secondhand accounts.
Backup plan for connectivity or technical failure
Have a phone (kept away from the desk but reachable for support), a backup internet option such as a mobile hotspot, and the provider's support contact saved. Confirm the provider's procedure for technical interruptions.
Water and a clock visible in the room
Small comforts reduce mistakes on long practical questions. Confirm whether drinks are allowed at your desk and whether a wall clock is permitted, since some proctoring rules restrict extra items.
Arrival or login buffer
Plan to arrive or log in well before the start time to absorb check-in, ID verification, and room scan. The exact buffer is provider-specific; confirm the recommended arrival window.
Plan the day
Switch from broad study to targeted review. Re-read the official domain outline and list the two or three areas where you are weakest, then spend most of your remaining time there. For a Git-focused exam this usually means command-level fluency: branching and merging, rebasing, reset versus revert, stash, tags, remotes, and how merge conflicts are resolved. Rehearse these in a terminal rather than reading about them.
Practice the GitLab-specific workflows you are likely to be tested on: creating a project, pushing and pulling over HTTPS and SSH, opening a merge request, and reading a .gitlab-ci.yml file. Be able to explain what stages, jobs, and runners do and how a pipeline is triggered. Write short summaries from memory and check them against the documentation.
Do one timed practice run under exam-like conditions to calibrate pacing. Note how long you take per question and decide a rule for when to flag and move on. Review only your wrong answers; do not restart broad reading.
Confirm logistics: appointment time in your local time zone, delivery mode, ID, room setup, and support contacts. Run any required system check one last time if testing remotely. Charge devices and test your webcam and microphone.
Do a light review of command syntax and key terminology only, then stop. Sleep is more valuable than one more hour of notes. Avoid learning a new tool or topic the night before.
Eat, hydrate, and avoid scheduling anything stressful immediately before the exam. Re-read your own one-page summary of weak areas. Log in or arrive early enough to complete ID checks and any room scan without rushing.
Close unnecessary applications, silence notifications, and put your phone out of reach unless the proctor instructs otherwise. Have your ID and confirmation details within arm's reach before the session starts.
Read each question fully before answering; practical questions often hinge on one word such as 'revert' versus 'reset' or 'merge' versus 'rebase'. Answer the questions you are sure of first, flag uncertain ones, and return to them with the remaining time.
For command questions, mentally reconstruct the command: subcommand, flags, and target. For scenario questions, identify what the user actually wants to achieve before choosing a tool. Eliminate options that would rewrite shared history or destroy work when a safer command exists.
If a technical problem occurs, stop and contact support through the provider's stated channel rather than troubleshooting silently. Note the time and what happened. Do not attempt to reopen the exam in a way the provider has not authorized.
Note which topics felt weak while they are fresh, in case you need to retake. Confirm with the provider when and how results are delivered, and do not discuss specific exam content with others, as confidentiality terms typically apply.
Rules to check
Present original, valid identification matching your registration. If your name or ID type does not match, resolve it with the provider before the exam; do not assume a workaround will be accepted at check-in.
Follow the proctor's instructions at all times. If you are unsure whether an action is allowed, ask before doing it rather than after.
Treat the exam as closed-book unless the provider explicitly states otherwise. Do not use notes, search engines, AI assistants, or a second device during the exam.
Do not share, record, or discuss exam questions or content. Most certification programs treat exam content as confidential; confirm the exact terms with the provider.
Confirm the break policy with the provider before test day. If breaks are permitted, know whether the clock keeps running and what you must do before leaving and returning.
Keep the testing environment clear and private. For remote testing, expect identity verification and a room scan, and remove anything that could be considered unauthorized material.
Understand the scoring model before you start: whether questions are weighted, whether there is a penalty for guessing, and what the passing threshold is. Confirm these details with the provider rather than relying on forums.
Report technical issues immediately through the provider's support channel and follow their instructions. Do not attempt unauthorized restarts or workarounds, which can invalidate your attempt.