I'm trying to move from several years of Tier 2 break/fix work into sysadmin or DevOps roles. Since I work for the government, certifications are often required just to qualify for the jobs I'm interested in. I've taken several Red Hat exams and recently passed one on a retake, but the remote exam environment was extremely frustrating. Latency caused repeated keystrokes, inserted typos, and sometimes deleted entire command lines when I backspaced. I passed the second time partly because I already knew the tasks and didn't need to spend as much time reading the exam instructions.
Because I'm paying for these exams myself, I'm hesitant to continue with Red Hat certifications if the environment can make a knowledgeable candidate fail. I'm considering Kubernetes certifications such as CKA, CKAD, or CKS, but I've heard that the PSI browser and remote-proctoring process can also be unreliable. For anyone who has taken them, is the experience generally manageable, or should I expect similar problems with lag, keyboard input, and proctors? I know studying only for an exam isn't ideal, but certifications are important for getting past job-screening requirements.
5 Answers
Pay attention to your display setup. A standard 1080p monitor with a normal 16:9 or 4:3 aspect ratio is safer than an ultrawide or unusual high-resolution display. Some people have lost several minutes fixing browser scaling and screen-mapping problems. If you use a laptop, keep the charger connected throughout the exam; the remote-proctoring software can drain a full battery surprisingly quickly.
The Kubernetes exams are generally manageable, though the check-in process can be tedious. Expect a room scan, ID checks, and sometimes a long wait before the exam starts. Once you’re in, the browser may feel a little slow, but it usually doesn’t behave like the Red Hat terminal where lag causes repeated keys or eats backspaces. A reliable internet connection, a decent-sized screen, and familiarity with the browser tools make a big difference.
My experiences with these exams were mostly smooth, aside from a slow check-in and occasional lag. The main difference from the Red Hat setup is that the delay usually doesn’t corrupt your command-line input. There are no guarantees because the proctor and connection can still cause problems, but if you rehearse the workflow and use a compatible setup, the exam environment shouldn’t prevent someone who knows the material from passing.
Practice in an environment that resembles the real exam. The official practice labs are especially useful because they include similar latency and let you get comfortable with the terminal, browser, and allowed documentation. Learn how copying and pasting works in the exam interface, and practice quickly locating the exact Kubernetes documentation or YAML examples you need instead of trying to memorize every option.
Proctor quality seems to vary a lot. Some exams are completely uneventful, while others involve repeated interruptions to show the desk, room, or webcam. I’ve heard of candidates losing several minutes while waiting for a proctor to respond, and occasional issues like a proctor suddenly deciding the room is too dark. It’s possible to pass, but start early and be prepared for the process to be unpredictable.
One check-in took nearly an hour for me. I’d use a personal Windows laptop or desktop if possible, rather than depending on a work machine with security software that might interfere. Other operating systems can work, but compatibility issues are harder to troubleshoot during check-in.