Stop skipping PBQs and hoping for an easy draw
A surprising amount of people skip the Performance-Based Questions on their exam and hope they get lucky.
They count on passing the multiple-choice questions and pray they do not get too many PBQs.
That is a bad strategy.
The point is to learn how to slow down, read the policy, and map each requirement to the answer.
PBQs are not impossible. They just test if you can apply what you learned.
Here is a simple way to handle them.
- Do not panic when you see them.
PBQs are made to look bigger than they really are. The wall of text, dropdowns, tabs, logs, and diagrams are there to slow you down.
- Do not answer them first.
Read them quick, mark them for review, and move on. Get through the multiple-choice questions first.
- Build confidence early.
Knocking out normal questions first gets your brain moving. It also keeps you from wasting too much time at the start.
- Use the exam for clues.
Multiple-choice questions can remind you of ports, commands, acronyms, and security concepts that may help with the PBQs later.
- Write down useful hints.
If the test center gives you a whiteboard, use it. Write down anything that might help with the PBQs when you come back.
- Check your time before starting them.
If you have 20 minutes left and 4 PBQs, that is 5 minutes each. Do not spend 15 minutes on one question.
- Do the easiest one first.
Look at all the PBQs before you start working. Pick the one that looks most familiar and secure those points.
- Break the question down.
Read what they actually want you to fix or configure. Ignore the extra noise and focus on the objective.
- Fill in everything.
Security+ does not punish wrong answers. If it is drag and drop, drag something. If it is a dropdown, pick your best answer.
- Practice PBQs before exam day.
You cannot get good at PBQs by only reading notes. You need to practice realistic scenarios so the format does not shock you on the real exam.
Do not skip PBQs and hope for an easy draw.
A few points from partial credit could be the difference between failing and passing.
Thanks for reading, George