Performance-based questions are the part of a CompTIA exam where you stop choosing an answer and start doing the job in a simulated environment. They reward the person who reads the goal, checks the current state, changes one thing and proves it. They punish the person who clicks confidently and hopes. This guide is the long version of that sentence, with the scoring rules, the common mistakes and a two-week plan.
| Practice option | Format | Best for | Skip it if |
|---|---|---|---|
| SecLern | Browser labs and PBQs, graded end state | Doing the task on a simulated desktop or console | You want a video walkthrough |
| Dion PBQ Practice Pack | 100 PBQ-style questions in sets of five | Exam wording and guided solutions | You need to operate a real interface |
| CompTIA Labs (CertMaster) | Vendor virtual environments with lab guides | Maximum alignment with the vendor | Budget is tight or you study several certs |
| Messer practice exams | Paid exam-style questions | A second check on recall | You have not learned the material yet |
| YouTube walkthroughs | Video demonstrations | Seeing an unfamiliar interface once | You want graded practice |
What a PBQ is, and what CompTIA actually says about scoring
CompTIA defines a performance-based question as a task or problem solved in a simulated environment. Both PBQs and multiple-choice questions are scored in real time by the testing provider, and CompTIA keeps the scoring method confidential.
Two details matter more than any forum rumour. First, CompTIA says some PBQs may offer partial credit while others may not, and some may carry higher point values than others. Second, it will not tell you which is which. So the safe strategy is to attempt every scored element you can identify, while never assuming that a half-finished task is worth half the marks. The official PBQ overview and the PBQ FAQ are the only sources worth quoting on this.
The five shapes you will meet
CompTIA does not publish a taxonomy, but across Security+, Network+, A+ and CySA+ the tasks fall into five practical shapes. Naming them helps you rehearse the right reflex.
Drag-and-drop and matching. Move terms, logs or steps into the right order. The cheap points are the pairs you know cold; do those first, then reason the remainder.
Configuration. A firewall rule table, an access control list, a Group Policy setting, a user account. The goal line tells you which flows or people must work; the rule order decides whether you succeed.
Log and alert analysis. A SIEM queue, a packet capture, an event log. You are looking for the first anomaly in time, then the thread that follows it.
Topology and cabling. Place a device, choose a link, fix a VLAN or a trunk. The diagram is the answer sheet; if the drawing is wrong, the configuration will be too.
Command line and console. A Linux shell, a Cisco-style device, a Windows prompt. Read-only commands first, one change, then verify with the same command.
Why the first minutes decide the section
Plan to meet the performance-based questions first: that is the usual order on these exams, and the tutorial screens show you how to flag a question and return to it. If your delivery differs, the strategy still holds. What does not change is the arithmetic: Security+ gives you 90 minutes for a maximum of 90 questions, Network+ and A+ the same, and CySA+ gives 165 minutes for 85 questions. If you spend 15 minutes perfecting one firewall, you have spent the time budget of a dozen multiple-choice questions. The SY0-701 exam page carries the current count for your version.
The practical rule: read every PBQ title before you start one, do the quickest first, and flag anything that needs more than four minutes. The flag is not an admission of defeat; it is how you buy information about the rest of the exam.
What the interface is telling you before you start
The chrome carries information that candidates discover too late. On a task screen, look for four things in the first ten seconds: whether the question can be skipped, whether your work saves when you move away, whether partial credit exists, and what the clock is counting. In our full simulation the labels read "skippable, work saves on move" and "partial credit available", and the timer is the sitting clock, not a per-question timer. The real exam's tutorial is the authority for its own interface, so read it, then look for the same four labels.
Two mechanical habits pay for themselves immediately. First, find the scrolling region before you drag anything: a bin or a drop target that is half out of view reads as an unanswered element, and you will not notice until the review screen. Second, treat the flag as a bookmark rather than a verdict, and check the navigator before you submit, because a flagged question you never returned to scores the same as a blank one.
The clock is the part people misread. One clock for the section means a task you abandon still spent its minutes, and a task you finish early does not bank time for the next question. That is why the order matters more than the speed: two easy tasks finished in six minutes buy you the right to spend eight on a firewall.
How to read a graded breakdown
A breakdown is more useful than a score, and most people read it backwards. Read it in three passes: elements that were correct, elements that were wrong, and elements you never attempted. The third list is the one people skip, and it is usually the longest, because time ran out before they reached the bottom of the page.
Then compare your route with the one the grader describes. A task can end in the right state by the wrong route: you blocked the scanner by shutting the port, which passes the check and fails the objective. If your route differs, redo the task and write the difference in one sentence. That sentence is what you will recall under exam pressure; the click sequence will not survive the week.
The last pass separates "I did not know" from "I knew and ran out of time". They need different fixes. Unknown material goes into the plan as a topic, and the study plan tells you which week it belongs in. Time pressure goes into the next drill as a budget, not as more content. The ports reference is the usual fix for the first kind on a log task: a queue is unreadable until service-to-port mapping is instant.
If you want a task list to work through rather than a single example, the SY0-701 lab catalogue names every performance task in the pack, with the objective each one checks.
The six mistakes that cost points
One: reading every exhibit before the goal. Exhibits are where time disappears. Read the goal line, then open only the exhibit that answers it.
Two: changing before checking. In a terminal or console task, run the read-only commands first: address, route, listening ports, service state. You cannot fix a problem you have not located.
Three: stacking changes. Make one change, verify it, then make the next. Three untested changes turn a small fault into a mystery, and you cannot tell which one broke it.
Four: chasing the hardest task. A perfect answer to the hardest PBQ is worth the same as a complete easy one, and it costs more time. Bank the easy points first.
Five: leaving elements blank. Because some PBQs may offer partial credit, a filled field or a matched pair is more likely to score than an empty one. Because others may not, never rely on partial credit as a plan. Attempt, then move.
Six: skipping the proof step. The task is not finished when the change is made; it is finished when the check passes. Ping the port, reload the page, run the show command, reopen the ticket. Graders read the end state, not your intention.
A firewall task, annotated
A typical SecLern firewall lab asks you to let an approved scanner reach the web servers and nothing else. The goal names two things: the scanner's address and the web ports. The mistake is to write a broad allow for the scanner subnet because it is easier. The pass is narrower: allow the scanner host to the web ports, deny the rest to that subnet, and let the implicit deny handle everything else. Then verify from a second host that the port is closed.
That pattern repeats on every CompTIA exam that has a firewall task: read the goal, write specific before general, verify both the allowed and the denied path. The firewall walkthrough shows the same logic with a full rule table, and the PBQ strategy guide covers the shorter tactical version.
A log task, annotated
A log or SIEM task gives you a queue and asks what happened, or which alert is real. Do not read every line. Sort by time, find the first event that should not be there, then follow that entity across the other sources. Answer what the evidence proves, not what the scenario implies. If two alerts are ambiguous, the one with corroboration in a second log source wins.
The log triage walkthrough walks through a queue with a false positive and a true positive, which is the pairing most exams use. For the time budget itself, see PBQ time management.
Time management that survives contact
Give the PBQ block 20 to 25 minutes on the first pass. Read the titles, do the two you can finish fastest, flag the rest, and move to multiple-choice. Multiple-choice is faster per point, and answering it calms the panic that makes a firewall task look impossible.
When you return, start with the task that has the most certain elements. Fill those first, then reason the rest. If two minutes are left, submit what you have rather than losing the whole task to a half-written rule.
Where to practise PBQs
We make SecLern, so it is first here. It is also the only option on this list that puts a graded desktop, console or SIEM queue in a browser with no install. The SY0-701 path has 56 PBQs and 47 labs; the tasks are original and mapped to the published objectives. The free tier includes three labs, and Pro unlocks the full set. The labs hub shows the same model on Network+, A+ and CySA+.
Dion's PBQ Practice Pack is the best pure question alternative: a bank of 100 PBQ-style questions in five-question sets with guided solutions. It is cheaper than a lab platform and useful for exam wording, but you are still choosing and typing into a question, not working a desktop.
CompTIA Labs, sold within the CertMaster family, is the vendor's hands-on option: virtual environments with lab guides aligned to the objectives. They are excellent for fidelity and expensive for a single exam.
Messer's practice exams include performance-style items, and his free videos explain the underlying concepts well. Use them as a check, not as your only rehearsal.
YouTube walkthroughs are free and can be useful for seeing an interface for the first time. They are the weakest form of practice because you watch someone else do the task. If you use them, pause before each step and say what you would do next.
A two-week PBQ drill plan
Days 1-3: one shape per day. Day one is matching and ordering. Day two is configuration, ideally a firewall or ACL. Day three is logs. Do one task, read the graded breakdown, then redo the same task from scratch. The second attempt is where the learning happens.
Days 4-5: terminals and topology. Run read-only commands before every change. Draw the topology on paper before you touch the device. Two tasks a day is enough.
Day 6: mixed set under time. Four tasks in 25 minutes, no hints, flag anything stuck. Review the breakdown the same day.
Day 7: rest or flashcards. Do not add a new task type on a rest day.
Week two: exam conditions. Two mixed sets of five tasks in 30 minutes, three days apart, with a full multiple-choice set after each. Track three numbers: tasks finished, elements correct, and minutes per task. The trend matters more than any single score.
What to do on exam day
Read the tutorial. Read every PBQ title. Do the fastest task first. Flag the rest. Write one sentence in your head for each goal before touching a control. Verify before submitting. When you return, fill the certain elements first and submit partial work rather than nothing.
That is the whole method. It is not glamorous, and it does not require a trick. It requires you to behave like a technician instead of a test-taker, which is exactly what the task is measuring. If you want the surrounding plan, the Security+ study plan and the exam-day checklist cover the rest.