The first question on my CCNA was a drag-and-drop, and I sat there for almost three minutes trying to talk myself out of the answer I already knew was right. I had walked into the Pearson VUE center that morning thinking the hard part was knowing the material. Turns out the material was the easy half. The part nobody had prepared me for was the format itself, the clock, and the fact that once I clicked Next, that drag-and-drop was gone forever and so were the points.
I failed that first attempt. Not by much, but a miss is a miss, and the score report doesn’t hand out partial credit for almost. When I went back the second time, I passed with room to spare, and the difference had almost nothing to do with knowing more about OSPF. It was about how I handled the exam as an exam. So if you have a date booked and you have been pouring everything into the content, this is the other half of the work, the part I wish someone had walked me through before I burned $300 learning it the hard way.
What is the CCNA exam actually like on test day?
You get 120 minutes. Cisco does not publish the exact number of questions, and it varies a little between people, but plan for somewhere in the neighborhood of 100. That math should worry you a bit, because it works out to a little over a minute per question on average, and some of those questions are simulations that can eat ten minutes by themselves.
The check-in is its own small ritual. You bring two forms of ID, you empty your pockets into a locker, and you get a laminated note board or a basic on-screen scratchpad depending on the center. No phone, no watch, no water bottle on the desk. I made the mistake of wearing a hoodie with a front pocket on attempt one and had to turn it inside out, which is a fun way to spike your heart rate before you have even seen question one.
Then you sit down, and the clock starts. The single most important thing to know about the CCNA, and the thing that wrecked my first attempt, is this: you cannot go back. There is no review screen at the end, no flagging a question to revisit, no changing your mind on number 12 once you are on number 13. Cisco locks each question behind you. Most exams you have ever taken let you skip and circle back. This one does not, and if you walk in with the habits from every other test in your life, it will cost you.
Why does the no-going-back rule matter so much?
Because it changes the whole strategy. On a normal exam, your instinct is to skip the brutal ones and bank the easy points first. Here, if you skip, you are skipping for good. So you have to make peace with answering every single question the moment you see it, even the ones you hate.
What this really punishes is overthinking. My first time through, I would land on the right answer, then start second-guessing, then construct an elaborate scenario in my head where the question was a trick. I talked myself out of correct answers more than once. The second time, I gave myself a rule: read it twice, commit, move. If I genuinely did not know, I would make my best guess in the time I had budgeted and let it go, because the worst outcome was not a wrong answer. The worst outcome was spending six minutes on a question I was going to miss anyway and then running out of clock on five questions I would have nailed.
Treat your time like it is the scarce thing, because it is. A wrong answer and a blank answer score exactly the same on the CCNA, which means there is never a reason to leave anything unanswered. Guess on everything you are unsure of, then keep walking.
What kinds of questions show up, and which ones cost the most?
The multiple choice questions are what you expect, though Cisco loves to write two answers that are both technically correct and ask for the best one, or to bury the real answer under a layer of irrelevant config detail. Read the last sentence of the question first sometimes. Half the time the giant paragraph of setup is noise and the actual ask is small.
Drag-and-drop and matching questions are usually quick points if you know the material, so do not let the unfamiliar format rattle you the way it rattled me. They tend to test definitions and mappings, like matching OSPF states to their descriptions or dropping protocols into the right OSI layer.
Then there are the simulations and simlets, and these are where the exam is won or lost. A sim drops you into a simplified Cisco IOS environment with a topology and a task, like configure a VLAN and verify connectivity, or troubleshoot why two routers are not forming an adjacency. A simlet shows you a working or broken network and asks several questions about it. These take real time and they are widely believed to carry more weight than a single multiple choice question, so if you have to lose time anywhere, it should not be here. My advice is to handle them when you feel sharp rather than when you are already rattled, but since you cannot navigate freely, in practice that means staying calm enough that you are always reasonably sharp.
The thing that bit me on the sims was forgetting that the show commands are right there. You can verify your work inside the sim. show running-config, show ip interface brief, show vlan brief, all of it. The first time, I configured something, assumed it was right, and moved on. The second time, I verified every change before clicking away, because the sim was telling me whether I had it right and I just had to ask.
How should you split up the 120 minutes?
I do not love rigid time charts, because the second you fall behind the chart you panic, and panic is the actual enemy here. But you do need a rough sense of pace. The honest version is to glance at the clock maybe three times during the whole exam and check it against the question number, not to stare at it.
The check I used was simple. Cisco shows you which question you are on and roughly how many remain. A little past the halfway mark on time, I wanted to be a little past the halfway mark on questions. If I was behind, I sped up on the multiple choice and stopped agonizing. If I was ahead, I let myself slow down and actually verify the sim work.
One more practical note. There is no pause. There is no bathroom break that stops the clock. Hydrate before, not during, and do not chug a large coffee twenty minutes before you walk in unless you enjoy doing OSPF math while distracted. I learned that one personally and will say no more about it.
How do you keep your head straight when a question blindsides you?
You will hit a question that looks like nothing you studied. Everybody does. The trap is letting that one question convince you that you are failing and that the whole thing is slipping away, because that story in your head will bleed into the next ten questions and turn one missed point into eleven.
When it happened to me the second time, I had a reset built in. I would take one slow breath, remind myself that I had budgeted for some misses, answer with my best guess, and physically move my eyes to the Next button. The exam is scored on a scale, and Cisco does not publish the line you need to clear, which means you have no way of knowing in the moment how you are doing. So stop trying to keep score. Your job is to answer the question in front of you as well as you can and then forget it existed.
If subnetting is the thing that rattles you, get it to the point where it is reflex before you ever sit down, because doing binary math while stressed and on the clock is a different sport than doing it at your kitchen table. I wrote up the whole method that finally made it click for me in going from binary tears to mental math, and the short version is that you want the answer to come from block sizes, not from drawing out 32 bits while a timer counts down.
What should you do in the last week before the exam?
Stop cramming new topics. The week before is for getting the format into your hands, not for finally understanding STP. Take full timed practice exams, the whole 120 minutes, sitting still, no phone, no pausing. The point is not just the score. The point is teaching your body what two hours of focus feels like so it is not a shock on the day. I ranked the practice exam options I have actually used in this breakdown if you are still deciding where to drill.
Review the official exam topics one last time and be honest about which ones you would dread seeing. You can pull the current blueprint straight from Cisco’s Learning Network, and it is worth comparing your weak spots against what Cisco actually says it will test rather than what some study guide guessed at. The official CCNA certification page is also where you confirm the current exam version, since that occasionally changes and you do not want to study an old blueprint.
The night before, do almost nothing. Light review, then close the laptop. Sleep matters more than the last forty flashcards, and I say that as someone who tried the all-night-cram approach the first time and walked in foggy. Confidence on the CCNA is mostly just being rested enough to read carefully.
And if it goes the other way?
Then you do what I did. You wait out the retake window, you look hard at the score report, which breaks down your performance by topic area, and you go fix the two or three things that actually sank you instead of restudying everything in a panic. A first failure is incredibly common and it is not a verdict on whether you belong in networking. I walked through the whole retake process, the waiting period, the cost, and how to come back from it, in what happens if you fail the CCNA.
The exam rewards a specific kind of calm that has very little to do with how much you know and a lot to do with how you behave for 120 minutes. Know the material, sure. But on the day, the version of you that passes is the one who answers every question, never looks back, and refuses to let a single ugly sim decide the whole story. That part you can practice too, and you should.
Network Engineer | CCNA | CCNP Enterprise
Allen Viola is a CCNP-certified network engineer who writes about exam prep and networking fundamentals from hard-won personal experience. He failed his first CCNA attempt, rebuilt his study approach from scratch, passed with an 875, and has kept going ever since. Everything he writes comes from that same mindset.
