ArcGIS Pro Professional study materials
ArcGIS Pro Professional study resources

ArcGIS Pro Professional exam-day guide

ArcGIS Pro Professional · Prepare for the day ahead.

Your checklist

Government-issued photo ID

Bring the original, unexpired ID matching the name on your registration. Confirm with the provider which ID types they accept and whether a secondary ID is required; policies vary by test center and by remote-proctor vendor.

Appointment confirmation and registration number

Have your confirmation email or candidate ID number accessible. For a remote proctored sitting, you may need to enter an exam code or launch the session from a link in that email - verify the exact launch procedure with the provider beforehand.

Know your testing format and delivery method

Confirm whether you are sitting at a test center or via remote proctoring, and which software or browser the vendor requires. Install and test any required secure browser or proctoring client at least a few days ahead.

Review the published exam blueprint

Download the official exam objectives or competency areas from the certification provider and check the current weighting of each domain. Do not rely on secondhand summaries - blueprints change between versions.

Confirm exam length, question types, and any hands-on component

Check whether the exam is multiple-choice only or includes scenario, drag-and-drop, or performance-based items, and confirm the number of questions and total time. If a hands-on or practical component exists, confirm its format with the provider; do not assume.

Confirm the score scale and passing score

Ask the provider or read the candidate handbook for the passing score and whether it is a scaled score. Do not assume a percentage-based pass mark.

Confirm retake and reschedule policy

Note the deadline and any fee for rescheduling, and how soon a retake is permitted after an unsuccessful attempt. Get these from the provider's candidate agreement, not from forums.

Practice the software, not just the theory

Spend the final days doing hands-on tasks in the current software release: project and geodatabase creation, coordinate systems, geoprocessing, editing, symbology, layout and map series, and sharing. Practical fluency is what these exams test.

Plan logistics for a test-center sitting

Confirm the address, arrival time, and parking or transit options, and build in a buffer for traffic or security screening. Arrival cut-off times are set by the provider - confirm them.

Prepare a compliant remote-testing environment

If testing remotely, clear your desk, close other applications, and check your camera, microphone, and internet stability. Room-scan and permitted-items rules are vendor-specific - confirm them in advance.

Know what personal items are permitted

Most providers restrict notes, phones, and smart watches, and some offer a whiteboard or on-screen notepad. Confirm the permitted-aids list with the provider; do not bring study notes unless explicitly allowed.

Sleep, hydration, and a light meal

Treat it like a performance day: rest well, eat something sustaining, and limit caffeine to your normal amount. Fatigue costs more points on long scenario questions than last-minute cramming gains.

Plan the day

72 hours before

Stop learning new material. Do a final pass over the official blueprint and mark any objective you cannot explain out loud. Spend remaining study time only on those gaps, using hands-on practice in the software rather than rereading notes.

72 hours before

Reconfirm the appointment: date, time, time zone, delivery method, and location or remote-session link. Check that your ID name matches the registration exactly and resolve any mismatch now, since fixes on exam day may not be possible.

72 hours before

Run a full timed practice set under exam-like conditions to calibrate pacing. Note how long you spend per question and decide a skip-and-return strategy for long scenario items. Review the errors, but do not chase trivia.

48 hours before

Do a light hands-on refresher of the highest-weight domains: coordinate systems and projections, geodatabase design, geoprocessing and ModelBuilder, editing and topology, and sharing or publishing workflows. Focus on where tools live and default behavior.

24 hours before

Do a short review only - key terminology, common tool locations, and your personal list of past mistakes. Then stop. Pack your ID and confirmation details, lay out clothing, and confirm your route or your remote-testing setup.

24 hours before

Check the vendor's site for any last-minute notices about outages, location changes, or proctoring requirements. Confirm whether you need to arrive early and what the arrival cut-off is.

Evening before

Set two alarms, charge devices, and get a full night's sleep. Avoid heavy cramming; a rested candidate reads scenario questions more accurately.

Morning of

Eat a proper meal, hydrate moderately, and arrive or log in with a comfortable buffer. For a test center, allow extra time for check-in and security. For remote testing, complete the system check and room scan before your slot.

During the test - opening minutes

Read the orientation screens carefully, note the time limit and question count, and take any permitted tutorial or practice item so you understand the interface before the clock matters. Write down your time budget if scratch materials are allowed.

During the test - first pass

Answer the straightforward items first and flag long scenario questions for review. Read each stem to the end before looking at options, and eliminate clearly wrong choices. For software-behavior questions, reason from how the tool actually works, not from what sounds plausible.

During the test - middle and review

Return to flagged items with the remaining time. Change an answer only when you can name the specific reason it is wrong - second-guessing without evidence usually hurts. Watch the clock so you leave time to answer every item; unanswered questions score as incorrect.

During the test - breaks

If breaks are permitted, keep them short and account for them in your time budget. Confirm in advance whether the clock stops during breaks; if it does not, plan accordingly.

After the test

Note how you felt about each domain while it is fresh, and record any topics that surprised you. If you did not pass, use the score report to target the weakest domains and confirm the retake waiting period with the provider before rebooking.

Rules to check

  • Bring original, valid photo ID in the exact name used at registration. If your ID name differs from your registration, contact the provider before exam day; test centers and proctoring vendors generally cannot admit a mismatched candidate.

  • Arrive or log in before the provider's stated cut-off. Late arrivals may be refused entry or marked absent, and the fee may be forfeited. Confirm the exact cut-off time with the provider.

  • Follow all proctor instructions, including any desk, pocket, or room-scan checks. Failure to comply can lead to session termination and a misconduct finding, which is more serious than a failed attempt.

  • Do not bring or use unauthorized materials or devices - notes, phones, smart watches, or secondary screens - unless the provider explicitly permits them. Confirm the permitted-aids list in advance rather than assuming.

  • Do not communicate with anyone other than the proctor during the exam, and do not screenshot, copy, or discuss specific exam content afterward. Sharing live exam items violates the candidate agreement.

  • Breaks are governed by provider policy and may not stop the clock. Confirm the rules for your delivery method before exam day so you do not lose answering time.

  • Scoring and passing standards are set by the provider and may use a scaled score rather than a simple percentage. Confirm the passing score and score-report format in the candidate handbook; do not infer them from practice-test percentages.

  • If a technical failure occurs during a remote session, stop and contact the proctor immediately rather than troubleshooting alone. Follow the vendor's incident process so the disruption can be documented and, where policy allows, remediated.