NCA exam experience — what the GPU architecture section actually tests
Took the NCA exam last week after about 6 weeks of prep. Scored 82%, though the GPU architecture questions were more conceptual than I expected. I went in thinking it would be mostly spec memorization — CUDA cores, memory bandwidth, that kind of thing — but the questions pushed toward understanding data flow and parallelism principles.
The deep learning fundamentals section was actually where I felt most confident. I'd been working with PyTorch for about 18 months before sitting for this, and that hands-on experience translated well. If you're purely studying from docs without touching actual GPU workloads, you're going to find some of those application questions vague.
Spent about 90 minutes a day for 5 weeks, then pushed to 3 hours daily in the final week. The CUDA programming concepts and tensor operations sections are worth extra attention. Roughly 30% of the questions required you to trace through what would happen at the hardware level given a specific workload configuration.
What was the breakdown like between certification domains? I've heard the inference optimization section has gotten heavier in recent exam versions and I'm trying to calibrate where to spend my remaining study time.
Passed mine in February with a 76%. The key for me was actually running the NVIDIA developer labs, not just reading about them. The hands-on stuff sticks in a completely different way than documentation review.
Studying for this now and six weeks sounds like a solid timeline. I was planning four but maybe I should add some buffer given how conceptual the architecture portion sounds.
The parallelism questions got me too. I kept thinking about it from a CPU threading perspective and had to consciously reframe to the GPU execution model. Once I did that, the architecture questions started making much more sense.
I'll be honest, going in I figured the GPU architecture stuff would just be flashcards. Memorize core counts, memorize bandwidth numbers, done. It wasn't like that. The questions kept asking why something behaves a certain way, like how memory access patterns affect throughput or why occupancy isn't the whole story. I work full time and have kids, so I did most of my prep in 30 to 40 minute chunks after everyone went to bed, plus a longer Sunday morning block when the house was quiet. That schedule actually forced me to revisit concepts over and over instead of cramming, which I think helped the conceptual stuff stick.
If you're squeezing this in around a job, my advice is don't just read specs and call it studying. Pick one thing, like why coalesced memory access matters, and actually sit with it until you could explain it to a coworker. I lost a few points on the conceptual questions because I'd memorized facts without really getting the reasoning behind them. Six weeks part time was enough for me, but only because I stopped trying to memorize everything and started asking why. You've got more time than you think if you use the small gaps in your day.
Yeah this matches my experience exactly. I failed my first attempt, scored somewhere in the low 60s, and it was because I prepped like it was a hardware spec quiz. I had all the CUDA core counts and bandwidth numbers memorized cold. Didn't matter. The questions weren't asking what the numbers were, they were asking why an architecture makes a certain tradeoff, like when memory coalescing matters or why a workload would stall. I just hadn't built that intuition.
Second time around I changed how I studied completely. Instead of flashcards I'd take a concept and try to explain out loud why it exists and what problem it solves. If I couldn't, I didn't actually know it. I also spent more time on how the memory hierarchy and the scheduler actually interact, since a lot of the conceptual questions live right there. Passed comfortably the next attempt. So if you're going in thinking it's memorization, that's the trap. Understand the why behind each spec and you'll be fine.