DEV Community

TiltedLunar123
TiltedLunar123

Posted on

Stop letting PBQs eat the first 15 minutes of your Security+ exam

If you ask people what scared them most going into the Security+ exam, you hear the same answer over and over: the PBQs. Performance-based questions sit at the front of SY0-701, before any of the multiple choice, and they are the closest thing the exam has to a hands-on task. You might get dropped into a firewall ruleset, a half-finished network diagram, or a wall of log output, and asked to actually fix something instead of picking a letter.

I want to break down what these questions are really grading, because once I understood that, they went from the part I dreaded to the part I felt most ready for.

The mistake happens before you read the question

CompTIA puts PBQs first. Your timer starts, you are cold, you have not settled into exam rhythm, and the hardest question format on the test is staring at you.

The single best piece of advice I got: do not solve them first. Every PBQ can be flagged and revisited. Skip them, run through the multiple choice, and come back with whatever time is left. Two things happen when you do this. You bank confidence from questions you can answer quickly, and the multiple choice often reminds you of details you will need in the PBQs anyway. A port number you blanked on at minute one is suddenly obvious at minute sixty because question 47 used it in a scenario.

The exam gives you a maximum of 90 questions in 90 minutes. A PBQ can swallow five of those minutes on its own if you let it. Be deliberate about when you pay that cost.

Each PBQ shape tests exactly one skill

PBQs look intimidating because the interface is unfamiliar. Strip away the drag-and-drop, though, and most of them collapse into a small set of shapes, and each shape grades one core skill.

Firewall or ACL ordering. You get a list of rules and some traffic that should or should not pass. The skill: rules process top down and stop at the first match. If a broad deny sits above a specific allow, that allow never fires. Almost every wrong answer here comes from ignoring rule order, not from misreading the rules.

Matching attacks to scenarios. A list of attack names, a list of descriptions, draw the lines. The skill: indicators. Phishing has a lure, smishing arrives by text, a watering hole compromises a site the victim already visits, tailgating needs a door. If you learn each attack as "what would I actually observe," these become free points.

Protocols and ports. Drag the protocol to the port, or pick the secure replacement for a legacy service. The skill: a memorized core list, plus the secure version of each old protocol. Telnet to SSH, FTP to SFTP, HTTP to HTTPS, LDAP to LDAPS. There is no trick here. It is pure recall, which means it is pure preparation.

Log and output reading. A chunk of logs with one anomaly buried in it. The skill: knowing what normal looks like. Repeated failed logins followed by one success, a workstation talking to an outside IP on a strange port at 3 a.m., an account created outside change control. You are pattern matching, and pattern matching only comes from reps.

You cannot read your way into PBQ readiness

This is the part I learned the hard way. I reread my notes on firewall rules plenty of times and still fumbled the first simulated ruleset I touched. Reading about rule order and applying rule order under a timer are different skills, the same way reading about swimming does not keep you afloat.

So practice in the format you will be tested in. Whatever resources you use, make sure some of them put an actual ruleset or log file in front of you and make you manipulate it.

That gap is honestly why I built SecPlus Mastery while studying for my own exam. It has hands-on interactive labs and PBQ-style questions alongside 1,069 practice questions and 31 reading lessons, so the first time you touch a firewall ruleset is not on exam day. There is also a free diagnostic exam if you want to see where you stand before committing to anything.

A simple PBQ drill for your last two weeks

If your exam is close, here is the loop that worked for me:

  1. Do one hands-on item per study session, before any flashcards or reading. Applied skills decay fastest under stress, so they get first priority.
  2. After every miss, write one sentence naming which of the four skills above failed. Rule order? Indicators? Port recall? Baseline reading?
  3. Drill only that skill the next day, then retry a similar item.

That one sentence of diagnosis matters more than the score. Misses cluster. Most people are not bad at PBQs, they are weak in one of the four skills, and they usually fix it within days once they can name it.

PBQs are not there to trick you. They are there to check that your knowledge actually moves when you push on it. Make sure yours does before test day, and the scariest part of SY0-701 becomes the part where you feel most at home.

Top comments (0)