CCNA 200-301 PBQ examples and free practice

What a CCNA 200-301 PBQ actually asks for

CCNA lab items are a device console: VLANs, trunks, static routes and the show commands that prove the fix. Cisco does not publish an item count or a PBQ count.

A performance-based question is a task, not a question with options: you are handed a workspace and a deliverable, and the scoring reads the state you leave behind. On 200-301 the bank carries 8 authored scenarios across 5 formats, and a simulated sitting serves 5 of them alongside the multiple-choice section.

The formats below are the ones this exam uses. Matching pairs is the format in the free scenario further down this page, so you can try the interaction before you decide whether CCNA 200-301 is the right exam for you.

How PBQs are graded

Every scenario is scored item by item, and the total is points earned over points available. There is no penalty for a wrong item beyond the point it was worth, and no bonus for speed: the clock decides when you stop, not how much each item is worth. A blank row and a wrong row score the same, which is why leaving a workspace half-finished is the most expensive habit on this exam.

The score report lists each item, the value you gave and the value required. On 200-301 a matching item is one point, a log origin can be worth two, and a ranked field pays half when at least half the sequence is right. Partial credit is why a half-finished scenario still tells you something: it shows which line of the deliverable you actually understood.

The pass mark is graded pass or fail, with no scaled score published. CompTIA and Cisco do not publish how many PBQ points that represents, and anyone who quotes an exact PBQ weighting is guessing. What the published facts do tell you is the scale you are working against: 90 questions in 120 minutes, with the IP connectivity domain carrying 25% of the marks.

Six common mistakes

These are the six ways learners lose PBQ points that have nothing to do with knowledge. Each one is fixable in a single practice sitting.

• Starting to type before reading the deliverable. The task line, not the story, says what is graded: "allow 443 to the web tier", "mark the compromised hosts", "order the containment". On 200-301 a terminal task can look familiar and still ask for the opposite of last time. Read the deliverable twice and say it back to yourself before you touch the workspace.
• Treating a PBQ like a multiple-choice question. There is no partial guess to make. On 200-301 the terminal and config and matching formats are scored item by item, so a blank item and a wrong item cost the same, and a nearly-right answer earns more than an empty one. Fill every item, in your best order, then go back to the ones you flagged.
• Losing the whole task to one stuck item. A single stubborn row can eat the twelve minutes the rest of the scenario needed. Set a hard limit of about ninety seconds on any one item, write your best answer, flag it and move on. The IP connectivity domain is 25% of 200-301; no single PBQ item is worth failing the rest of the section for.
• Ignoring the order inside an ordered task. Firewall rules are first-match-wins and incident response has a sequence that survives an audit. If the task says order, a correct set in the wrong order is still wrong, and the config format scores position by position. Ask which step has to happen before another, then build from the constraint end.
• Never checking your own work. Every workspace can be inspected before you submit: the packet verdicts, the file permissions, the service state, the show output. Re-read the deliverable and prove each line of it in the tool. Learners lose more points to an unchecked second row than to a missing idea.
• Skipping the debrief after a miss. The score report names the item, the value you gave and the value required. That report is the study material. Copy the two or three misses into notes and open the objective page for them the same day, or the same mistake returns in the next 200-301 sitting under a different story.

Where the PBQs sit in the 200-301 sitting

Cisco does not publish where the lab items fall, and it does not publish a fixed item count either. Treat the lab block as unpredictable: rehearse the console commands until they are automatic, and read the goal line twice, because the wording is the only specification you get.

Practise the whole shape, not just the workspace: a timer, a mixed set, and a decision about what to flag. The app's timed simulations run the 90-question, 120-minute shape, and the free tier gives you three PBQs and thirty questions a day before you decide anything about paying.

A practice plan that fits a week

Day one: open the free scenario on this page and submit it without hints, even if you are unsure. Read the score report line by line. Day two: take the 200-301 practice test on this site and note which domain the misses come from. Day three and four: work the matching labs, which use the same surfaces as the PBQs but grade a job rather than a deliverable. Day five: come back to the scenario and score it again with the hints off; if the second attempt is not clean, the gap is in the IP connectivity domain, not in the workspace.

Keep a short note per miss: the item, the value you gave, the value required, and the objective id. That note is worth more than a second video course, because it is the only record of what you personally get wrong.

What the workspace looks like

Real captures from the PBQ workspaces in the app, annotated to point at the parts that decide the score. Each caption names the exam and the scenario it shows.

200-301 PBQ questions