Proctoring
What do PingOne and ProctorU Guardian actually check on a WGU exam?
At a glance
Last updated
WGU proctored OAs typically run two layers: PingOne device profiling, which fingerprints and validates the device and environment before the exam, and ProctorU's Guardian Browser, a locked-down browser that controls the session itself while a live or automated proctor watches. Together they are designed so only the enrolled student, on an approved machine, in a controlled session, can sit the exam.
- PingOne profiles the device and environment before the exam
- Guardian Browser locks down the session during it
- Live or automated proctoring watches the attempt
- Ad-hoc remote setups are exactly what this stack blocks
Every full package includes the written 6-month guarantee: we finish the remaining CUs under the agreed plan, or you do not pay. Packages: Bachelor's $3,000 · Master's $3,500 · both $5,500 · single assessments from $99.
What is PingOne device profiling?
PingOne is the identity and device layer many WGU OAs run before the exam session opens. It profiles the machine and environment and checks that the device matches what the university expects for that student, instead of an unknown or ad-hoc remote setup.
This is the gate most casual help never passes: the exam does not begin until the device check does, and profiling problems end the attempt before a single question loads.
What does the ProctorU Guardian Browser do?
Guardian is ProctorU's locked browser. The exam runs inside it, and it restricts what else the machine can do during the session: other windows, screen sharing, and unapproved processes. Depending on the exam, a live proctor or an automated system watches the attempt through it.
Guardian is the reason a WGU OA is not a normal browser tab. The session is controlled end to end, from identity check to final submission.
Want this handled instead?
Send your program and remaining CUs. You get a written plan, an exact price, and a finish date before you pay anything.
Why do most remote-exam workarounds fail this stack?
Because the stack checks the environment, not just the person on camera. A second laptop running a remote desktop tool, a virtual machine, or a helper on another screen are the setups device profiling and browser lockdown exist to catch. Students usually discover this only after paying for an attempt that never starts.
Legitimate preparation looks different: a clean, approved environment, the proctoring requirements read before scheduling, and a plan for the exam itself, not for evading the room.
| Stage | What gets checked | What ends the attempt |
|---|---|---|
| Before the exam | PingOne device profiling: identity, device, environment | Unknown devices, remote-desktop tools, virtual machines |
| During the exam | Guardian Browser lockdown plus live or automated proctoring | Extra windows, unapproved processes, leaving the session |
| After the exam | Session recording and anomaly review | Flagged behavior reviewed before scores finalize |
What does a proctored WGU exam session look like?
You schedule the attempt inside ProctorU, install and check the Guardian Browser beforehand, and start with an identity and environment check: photo ID on camera, a room scan, and the device profiling pass. Only then does the exam itself load.
During the exam the browser stays locked and the proctoring layer watches the session. Bathroom breaks and questions to the proctor follow the exam's posted rules. When you submit, the session recording closes out and the score processes. The whole thing is routine when the environment is prepared, and brutal when it is not.
Does the stack change for certification exams inside a degree?
Slightly. Certification-linked courses (common in technology and cybersecurity degrees) sometimes run through the vendor's own testing channel with its own rules, on top of WGU's scheduling. The core is the same: verified identity, controlled device, watched session.
The practical difference is scheduling lead time. Vendor exams book out further, so a plan that schedules the cert attempt two weeks early beats one that discovers the calendar after finishing the prep.
How does Coursework Ninja complete proctored OAs?
Proctored exams are part of our done-for-you OA path, scoped per course at intake. We run the attempt through the required environment so profiling and the Guardian session are handled as part of the completion plan, not discovered at the login screen.
That path sits under the same written plan as everything else: weekly clear targets, a finish date, and the 6-month finish-or-do-not-pay guarantee.
Questions, answered
Most proctored WGU OAs use some combination of device profiling and a locked ProctorU browser, and the exact stack varies by course. At intake we confirm the environment for each proctored course on your plan.
Usually yes, if it meets the posted requirements: modern operating system, working webcam and microphone, admin rights to install the Guardian Browser, and no remote-access or virtual-machine software running. Work laptops locked down by an employer often fail these checks.
The session pauses or ends depending on how long the dropout lasts, and ProctorU's support process decides whether the attempt can resume or must be rescheduled. A wired connection and a quiet, controlled room remove nearly all of this risk.
Yes, when that course is in the agreed written scope. Proctored environments are a standard part of our OA completion path, confirmed at intake rather than treated as a surprise add-on.
Coursework Ninja is an independent done-for-you degree completion service and is not affiliated with, endorsed by, or sponsored by Western Governors University.
Your plan starts here
No forms
Ready to set a finish date?
Send your program and remaining CUs. We reply with pace options, exact pricing, proctoring scope, and guarantee terms, in writing, before you pay anything.
No forms. Message us directly.