GitLab PM Associate study materials
GitLab PM Associate study resources

GitLab PM Associate exam-day guide

GitLab PM Associate · Prepare for the day ahead.

Your checklist

Government-issued photo ID matching your registration name

The name on your ID should match the name you registered with. If your name has changed or differs (for example, a shortened first name), confirm with the provider before test day whether additional documentation is accepted. Requirements vary by delivery method, so verify rather than assume.

Your exam appointment confirmation and login details

Keep the confirmation email, appointment time (including time zone), and any candidate ID or access link where you can reach them quickly. Double-check the time zone conversion the day before so you do not arrive an hour early or late.

Working webcam, microphone, and speakers/headset (remote proctoring)

If you are testing online with a proctor, run the provider's system check on the same machine and network you will use on exam day. Test the camera and mic, close background apps, and confirm your browser version is supported. Do this at least 24 hours ahead so you have time to fix problems.

Stable internet connection and a backup plan

Wired or strong Wi-Fi is preferable. Know how to tether to a phone or move to another room if the connection drops. Confirm with the provider what happens if you are disconnected mid-exam (whether the timer keeps running, whether you can reconnect).

A quiet, private, well-lit room with a clear desk

Remove papers, phones, smart watches, second screens, and anything a proctor could flag. Tell household members you are unavailable for the full appointment plus check-in time. For remote proctoring, expect a room scan and desk check before the timer starts.

Review the provider's allowed-materials and calculator policy

Confirm whether any notes, scratch paper, or a calculator are permitted, and whether scratch paper must be shown and destroyed afterward. Do not bring prohibited items assuming they will be stored; confirm with the provider.

Confirm break policy and plan hydration and medication accordingly

Some exams allow scheduled breaks, some allow none, and some pause the clock only for approved accommodations. Check the rule for your specific exam and plan food, water, and any medication around it. Request accommodations well before test day if you need them.

Know the scoring model and whether wrong answers penalize you

Confirm whether the exam is scored on correct answers only or applies penalties, and what the passing score is. That determines whether you should guess on unanswered items. If the provider does not publish this, treat unanswered questions as lost points and aim to answer everything.

A study sheet of key GitLab concepts for a final skim

Keep it short: the GitLab DevOps lifecycle stages, issue and merge request workflow, labels and boards, milestones, epics where relevant, CI/CD pipeline basics, and permission/role names. Skim it in the final hour rather than learning anything new.

A time-management plan for the question count

Note the total number of questions and total minutes, then compute an average pace. Plan to flag uncertain questions and return to them rather than stalling. Leave a few minutes at the end to confirm no question is left blank.

Plan the day

72 hours before the exam

Confirm logistics: appointment time in your local time zone, delivery method (test center or remote), ID requirements, and allowed materials. Re-read the provider's candidate handbook or FAQ so nothing on test day is a surprise. If you requested accommodations, confirm they are approved and attached to your appointment.

72 hours before the exam

Shift from learning to consolidating. Review your weakest two or three topic areas using your own notes, and do a short set of practice questions under timed conditions to calibrate pace. Stop cramming new material the night before; it raises anxiety more than scores.

24 hours before the exam

Run the technical system check if testing remotely, and note the proctor's check-in window and how early to log in. Prepare your ID, confirmation, and any permitted items in one place. Charge devices and confirm your backup internet option works. Sleep at your normal time.

24 hours before the exam

Do a light review only: skim your key-concepts sheet for GitLab lifecycle stages, issue and merge request flow, boards and labels, and CI/CD fundamentals. Avoid heavy new topics and avoid comparing your readiness to others online.

Morning of the exam

Eat a normal meal, hydrate, and avoid starting anything that could run long. Log in or arrive at the test center earlier than the minimum required check-in time. Do a final 10-15 minute skim of your sheet, then put it away so working memory is clear for the exam.

During the exam

Read the full question before looking at the options, especially for 'which is the best' or 'which comes first' phrasing. Answer confident questions first, flag uncertain ones, and return to them. Watch the clock at the halfway point and adjust pace. Use any permitted scratch paper to note question numbers you flagged.

During the exam

If a technical problem occurs, stay calm and follow the proctor or provider support process immediately rather than troubleshooting silently. Note the time and what happened in case you need to request a remedy afterward.

After the exam

Note which topics felt weak while memory is fresh, in case you need a retake or want to build on the credential. Confirm how and when results are delivered and what the retake policy is.

Rules to check

  • Bring the exact ID the provider requires and make sure the name matches your registration. If it does not, contact the provider before test day; do not rely on being admitted with a mismatched document.

  • Do not bring or use prohibited materials, including phones, smart watches, notes, or a second screen, unless the provider explicitly allows them. For remote proctoring, keep devices out of the room or follow the proctor's instructions for where to place them.

  • Follow all proctor instructions, including room scans, desk checks, and identity verification. Refusing a reasonable check can result in removal from the exam, and the provider's policy governs whether fees are refunded.

  • Confirm the break policy for your exam before you begin, and do not leave your seat or the camera view during the exam unless the rules permit it. Unauthorized breaks may be treated as a conduct violation.

  • Treat the exam content as confidential. Do not copy, photograph, record, or share questions or answers, and do not discuss specific exam items in a way that violates the candidate agreement you accepted.

  • Understand the scoring model before you start: confirm whether unanswered questions count against you and what the passing score is. If unsure, answer every question rather than leaving blanks.

  • If you experience a technical failure or a disruption, report it to the proctor or provider support immediately and follow their process. Ask what documentation they need and keep records; do not assume an automatic remedy.

  • Confirm all specific policies, including ID rules, allowed materials, break rules, scoring, and retake terms, with the exam provider. Requirements can change and vary by delivery method, so verify rather than assume.