Every A+ instructor eventually meets the student this post is about. They memorized every port number, they can recite the laser printing steps in order, they pass every practice exam, and in a mock interview, asked how they would handle a user who cannot log in, they freeze. Not because they lack the knowledge. Because they have never once been asked to use it on a person.
The A+ is worth teaching, let me say that clearly before the critique. It gets resumes through filters and it forces a broad, honest survey of the field. But the exam objectives are a list of things to know, and the job is a sequence of things to do, and a course that only teaches the list produces exactly the student above: certified and unready, holding a ticket to an interview they will lose.
The two finish lines
It helps to name the two goals separately, because they need different practice. Passing the exam requires recall: definitions, acronyms, port numbers, the content of the objectives. Question banks and practice exams train this well, and nothing else trains it better. Keep them.
Being ready for the job requires something recall does not provide: the reflex of walking into an unknown problem and narrowing it down. The exam gestures at this with performance-based questions, but a simulated question about a scenario is still a question. The reflex only comes from reps, from being the person a problem happens to, repeatedly, until the troubleshooting method stops being a list of six steps and becomes what your hands do.
Attach doing to every domain
The fix is structural rather than heroic: for each domain you teach, pair the content with an activity where students perform it. Cover accounts and security, then hand them lockout and password tickets with a user attached who needs to be working again. Cover networking, then give them an office that lost its connection and a caller who wants to know why. Cover malware, then let them meet a machine that acts infected and work it to clean.
The pairing does something subtle to retention as well. A port number studied for an exam decays in weeks; the DNS misconfiguration a student personally chased for twenty minutes stays. Objectives that show up as causes inside real problems get filed by the memory as things that matter, because they demonstrably did.
Any hands-on format can carry this, and I have written about the tradeoffs of each. The simulator’s classroom version is our contribution: a live helpdesk whose tickets cover the A+ troubleshooting ground, operating systems, accounts, networking, hardware, so the week’s lab is always “resolve tickets from the domain we just covered.” Students get a queue and working tools. You get a dashboard of who resolved what, which grades the lab for you while you teach.
The interview is a scenario question
Here is the argument I would make to a skeptical curriculum committee. Entry-level interviews are dominated by scenario prompts: walk me through a user who cannot print, what would you check first, what do you ask the caller. These are predictable questions, and a student with a few hundred resolved tickets behind them answers from memory of doing, in the specific, confident detail interviewers are listening for. A student with only the objectives answers in generalities, and interviewers hear that too.
Both students hold the same cert. Only one of them gets the callback, and it is the one whose course made them do the job before anyone paid them for it.
If you want the ticket-practice half without building it yourself, the classroom simulator sets up in one lesson, runs in the browser on whatever machines you have, and comes with a 7-day classroom trial, offered with your quote, no card. Keep the practice exams for the recall. Let the queue teach the reflexes.