A practical technical checklist for remote exams — system test, bandwidth, webcam, background apps and secure browser — done days before you sit.
A remote exam can be lost before a single question appears — by an operating-system update that reboots the machine mid-check-in, a corporate laptop whose security software blocks the secure browser, or a Wi-Fi connection that tests fine on Sunday and collapses when the whole street is on video calls Monday morning. The good news: nearly every technical failure in an online proctored exam is preventable with an hour of setup done in the days before, not the minutes before.
This is that setup, as a working checklist. It covers the official system test, hardware, internet, and the software conflicts that cause most problems. It deliberately stops at exam-day readiness — if something breaks during the exam itself, the in-the-moment fixes are in common technical problems during online exams, and the fuller picture of how the day unfolds is in what to expect during an online proctored exam.
Every major delivery platform publishes a system test, and Pearson VUE requires one before an OnVUE exam. It checks your webcam, microphone, internet speed and whether the secure browser runs on your machine. Three rules make it meaningful:
If the system test will not pass on your machine at all (common on employer-managed laptops — see step 4), that is your cue to arrange a different computer now.
Published minimums are genuinely minimal. CompTIA's online-testing requirements, a representative example, specify at least 1 Mbps upload and download and a webcam of at least 640×480 resolution at 10 frames per second. Most modern laptops and connections clear these easily — but "minimum" is the level at which the platform functions, not the level at which you stop worrying. Practical margin looks like this:
Your bandwidth is shared with everything else in the house. For the exam window:
None of this is required by any provider; all of it is cheap insurance against the dropout scenario whose consequences are serious enough to have their own article.
The secure browser wants to be the only thing running, and it will object — sometimes by refusing to launch — to software that could capture your screen, pop up messages, or interfere with monitoring. Before check-in:
A useful habit: restart the computer an hour before check-in and open nothing except what the exam requires. A fresh boot clears most lurking processes for free.
Two devices sit at the edge of the setup. Your phone must usually be reachable in case the proctor needs to contact you, but outside your workspace — CompTIA's policy phrases it as nearby but out of the work area, and the desk itself must be clear of books, paper and pens. Where every item may and may not sit is the territory of the desk rules guide. And since scratch paper is off the desk, note that some programmes (CompTIA included) provide a built-in digital whiteboard instead — worth knowing before you reach for a pen out of habit.
Run this two days out, then skim it again on the morning:
If every box ticks, the technology is done and the remaining variable is you. That part responds to rehearsal the same way the tech does: a timed run in an online practice-test simulation on the very machine you will test with doubles as both revision and a final shakedown of your setup.
Yes, treat that as fixed. The system test validates a specific combination of machine, software and network; switching computers afterwards silently invalidates the result. If you must change machines, re-run the test on the new one immediately.
Wi-Fi that comfortably passes a speed test from your exam seat is acceptable — plenty of candidates test on it. Ethernet is simply more predictable, because it is immune to interference and other devices roaming the network. If a cable is practical, use it.
Sometimes, but it is the riskiest option. Managed devices often carry VPNs, monitoring agents and admin locks that conflict with secure exam browsers, and you may be unable to change them. Run the system test early; at the first sign of trouble, plan on a personal machine.
Plan around a single laptop or desktop with one screen. Programmes such as CompTIA explicitly prohibit additional monitors and extra computers in the workspace, and secure browsers are built for desktop operating systems — check your specific programme's requirements page for supported devices.
Spread across two or three days, everything above costs perhaps an hour: one system test, one speed test, one uninstall-and-restart session, one sweep of the desk. That hour converts exam-day technology from an open question into a solved problem — which is exactly the state of mind you want when the room scan starts and the only remaining test is the one you studied for. If you are still building that side of the picture, the free sample questions for your exam are a low-stakes place to check where you stand.
Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.
Put it into practice
Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.
·7 min read
Timing, score benchmarks and review technique for CompTIA practice tests — how to turn A+, Network+ and Security+ practice scores into a genuine pass signal.
Continue reading·8 min read
How to use CISA practice tests properly — when to take them, how to benchmark scores across the five domains, and how to turn wrong answers into study priorities.
Continue reading·8 min read
A practical buyer's checklist for choosing a reliable certification practice test: objective alignment, explanations, simulation features and red flags.
Continue reading
