Google IT Support exam-day guide
Google IT Support · Prepare for the day ahead.
Your checklist
Working device and charger
Most Google IT Support assessments are taken on Coursera in a web browser. Use a laptop or desktop you have tested recently, and bring the charger. Mobile apps are unreliable for long quiz sessions.
Stable internet plus a backup connection
Have a second option ready (phone hotspot, second network). Confirm with the provider whether a dropped connection pauses or submits a timed quiz before you rely on it.
Coursera login confirmed
Log in the day before and confirm you can open the course and every module. A forgotten password on quiz morning costs more time than any review session. Marked needs_review: exact identity-verification steps vary, so confirm with the provider.
Photo ID and webcam ready (if verification is required)
Some Coursera certificate flows ask for a webcam photo and a typed phrase, and in some cases a government ID. Do this before the assessment window, not during it. Marked needs_review: requirements change and are account-specific; confirm with the provider.
Updated browser with cookies and JavaScript enabled
Coursera quizzes need a current version of Chrome, Firefox, Edge, or Safari. Clear the cache and disable aggressive ad-blockers or script blockers that can break quiz submission.
Quiet, well-lit space
Even non-proctored assessments go faster without interruptions. Tell housemates you are unavailable and silence phone notifications.
Reference notes and scratch paper
Google IT Support quizzes are generally open-resource and unproctored, but academic-honesty rules still apply. Marked needs_review: confirm with the provider what reference material, if any, is permitted for your specific assessment.
Your own summary sheet of high-value facts
One page you wrote yourself: common ports (22 SSH, 23 Telnet, 25 SMTP, 53 DNS, 80 HTTP, 443 HTTPS, 445 SMB, 3389 RDP), the six-step troubleshooting process, and the commands you mix up (ipconfig, tracert, nslookup, netstat, chmod, ps, grep).
Time budget written down
Note how many questions and how much time the quiz allows, then compute minutes per question. Marked needs_review: timers differ by quiz; check the assessment instructions yourself.
A plan for retakes
Many Coursera quizzes allow multiple attempts, with the highest or last score counting depending on the quiz. Confirm with the provider what the retake rule and scoring rule are for your assessment before you start.
Plan the day
Do a full pass over the five courses' key material: hardware basics, networking (OSI and TCP/IP models, IP addressing, DNS and DHCP), operating systems (Windows and Linux file systems, permissions, package management), system administration and IT infrastructure (directory services, Active Directory, LDAP), and security (least privilege, encryption versus hashing, malware types). Rework every quiz question you missed earlier and write down why each wrong option was wrong.
Re-take any practice or ungraded quizzes cold, without notes, to find real gaps. If the certificate has a final graded assessment per course, treat the weakest course as your priority for the remaining time.
Log in, confirm access to every module and assessment, check the deadline or suggested schedule, and verify identity-verification status. Test your browser and network on the same device you will use. Pack your notes and charger. Then stop studying and sleep - recall on networking and command-line details degrades sharply when you are tired.
Skim only your one-page summary sheet. Eat, hydrate, and clear your workspace. Close every other tab and application. Log in 10–15 minutes early so a login or verification problem does not eat into the assessment.
Read each question fully and answer the ones you know first. For troubleshooting scenarios, apply the standard sequence: identify the problem and gather information, establish a theory, test the theory, create an action plan, verify full functionality, document. For command-line questions, ask what the tool is for before recalling syntax. Flag uncertain items and return to them rather than stalling.
Watch the clock at the halfway mark. If a technical problem interrupts you, capture a screenshot and note the time - that record matters for any support request or attempt reset. Marked needs_review: the exact process for reporting a technical issue and whether an attempt is restored must be confirmed with the provider.
Check the reported score and whether a retake is available. If a module did not pass, note the specific missed topics while they are fresh and schedule the retake for a day you can focus.
Rules to check
Follow the platform's academic-honesty policy in full. Do not share quiz questions, do not have another person take the assessment for you, and do not post answers in forums or study groups.
Confirm with the provider, before the assessment, whether you must present a government-issued photo ID and complete identity verification. Requirements differ by account and program, so do not assume.
Confirm with the provider what reference materials and notes are allowed for your specific assessment, and stay within those limits even if the quiz is technically unproctored.
Take breaks between modules, not during a timed assessment. If a quiz is timed, the clock generally keeps running while you are away - confirm with the provider how pausing is handled.
Understand the scoring rule before you start: whether retakes are allowed, whether the highest or the latest attempt counts, and what passing threshold applies. Where the platform does not state it clearly, ask the provider.
Report hardware, network, or submission failures immediately with a screenshot and timestamp, and do not open a second attempt while a support case is open unless the provider tells you to.
Keep your login credentials and any identity-verification data private. Do not let anyone else use your account, even to help you troubleshoot.
Treat each course's graded assessments as cumulative - a missed module can reappear in a later final assessment, so do not skip a low-weight quiz assuming it will not matter.