top of page

My First Online-Proctored Exam: Setting Up So Nothing Surprises Me

7 days ago
4 min read

Saturday flex, and a short one — but it's about the part of exam prep nobody studies for: the exam environment itself.


SC-900 on September 20 will be my first online-proctored certification exam. I'll sit it from home through OnVUE — Pearson VUE's remote proctoring — on my own machine, watched by software and a live proctor instead of test-center staff. My appointment is 3:00 PM Eastern, with check-in opening 30 minutes before. If you've followed this blog for more than a minute, you know why that particular unknown has my full attention.


Why this isn't a small detail for me


My first ISC2 CC attempt ended in an anomaly — the exam terminated at 90 questions, below the minimum, and I spent weeks on a formal inquiry to earn a retake. That happened in a test center, with staff on site.


So I go into my first at-home proctored exam with a very specific kind of respect for everything that can go sideways in an exam environment. I've already lived the version where something outside my control ends the session. This time, the environment is largely inside my control — and I'm treating that as a responsibility, not a convenience. Every variable I can lock down before exam day is one that can't surprise me on it.


That's the whole mindset of this post: I can't control the questions. I can control the room, the machine, and the setup. So those get handled early.


What I've already done


I didn't wait until exam week to find out my setup works. I've already:


  • Installed the newest OnVUE version using the access code from the "test your system" link in my confirmation email. Worth knowing: the software updates, so the version you installed weeks ago may not be current — running the system test pulls you onto the latest build ahead of time instead of on exam morning.


  • Run the full system test on my actual machine — the same laptop, connection, and setup I'll use on the 20th. And it's more than a speed check. OnVUE walked through my microphone, my speakers/sound, and my webcam one at a time, confirming each works. Then it had me record a short video clip, which it confirmed, and run a short recorded segment where you agree to the exam conditions — essentially a dry run of the real check-in, recorded the same way the exam will be.


That last part surprised me a little, and I'm glad I hit it early rather than live: seeing exactly how the mic/camera/recording check flows means none of it will be new on exam day. The whole point is that the only unfamiliar thing on the 20th should be the questions — not the software, not the check-in, not the recording.


Getting this done early does two things: it confirms my machine meets the requirements, and it means any problem surfaces now, with days to fix it, instead of thirty minutes before a timed exam.


What I'm still locking down before exam day


The system test is the technical half. The other half is the room and the rules — and reading OnVUE's actual policy, the requirements are strict enough that "I didn't know" is not a safe place to be. Here's the checklist I built straight from their rules:


  1. One screen, no extras. OnVUE allows a single display only — secondary monitors disconnected, no touchscreens, no phones/tablets/watches/earbuds. If I use my laptop with an external monitor, the laptop lid closes so only one screen is live.


  2. Restart right before check-in, and plug in. They require a fresh restart just before you start, so there are enough resources to stream and record the whole session. Laptop stays plugged into power the entire time — you're not allowed to leave the webcam view to plug in mid-exam.


  3. Connection: hardwired if I can, close to the router if I can't. OnVUE prefers a wired connection and prohibits VPNs and corporate networks, but Wi-Fi is allowed if you sit near the router. The real-life piece: ask everyone in the house not to stream or download during my window, because someone else's Netflix can tank my exam.


  4. A clean, private, single-person room. Tidy desk, no paper or writing utensils unless allowed, no clutter or spare electronics. Cover any window, doorway, or partition where someone could see the screen — and make sure nobody walks into frame, because I can't leave webcam view once I start.


  5. ID and check-in ready, bathroom first. A valid government photo ID with the name matching my booking exactly. Check-in opens 30 minutes before, at 3:00 PM Eastern. Bathroom before I open OnVUE, since I can't step away unless it's an approved break. A drink and gum are allowed; almost nothing else is.


How I'd explain this in a SOC interview


Ask me how I handle a high-stakes task in an unfamiliar environment, and this is the answer: I don't wait to discover the failure points live — I test the whole setup end-to-end ahead of time on the real equipment, read the rules of engagement before they matter, remove every controllable variable that could go wrong, and build in margin so an unexpected hiccup has room to be absorbed instead of blowing up the whole operation. That's change-readiness and operational discipline. In a SOC, you don't deploy a new tool or run a critical process by finding out live whether it works — you validate in advance, you know the runbook cold, and you control what you can so your attention is free for what you can't. Same instinct, whether it's a detection pipeline or a proctored exam.


Eight days out. Material's coming along, and now the environment is too. I'll report back from the other side of the 20th.



Storm to SOC — control what you can, then move. 💜

Comments


Let's learn this together. Have a question, a better query, or just want to say hi? Drop a line below.

© 2026 by DataSec Chronicles. Data-Inspired, Instinct-Driven.    Privacy Policy    Terms & Conditions

bottom of page