Auvik ACP exam — anyone else surprised by how much topology discovery was tested?

84% is solid. The Auvik Academy modules are genuinely the best prep material — the exam writers clearly pull from that content. Two full passes through the curriculum is the minimum I'd recommend.

The SNMP polling and topology refresh relationship was on my exam too. It helps to actually watch the topology view update in real time on a live network — seeing it beats reading about it.

I found the traffic insights and flow analysis questions harder than the setup content. If you're studying now make sure you understand how Auvik classifies unusual traffic and what triggers a traffic alert versus a connectivity alert.

I actually failed my first attempt for exactly this reason. I'd been using Auvik daily for over a year and figured that hands-on time would carry me, but the exam cares a lot about the underlying mechanics, not just knowing where to click. What changed for me the second time was spending a few days specifically on how Auvik builds its topology maps, how it determines parent-child relationships between devices, and what triggers a rediscovery. That stuff isn't obvious from just using the dashboard.

Honestly the biggest shift was treating it less like a platform certification and more like a networking exam that happens to use Auvik as the context. If you know why the topology looks the way it does, the questions become a lot more predictable. SNMP polling behavior and how layer 2 versus layer 3 discovery differs were both on there more than I expected. Don't sleep on the documentation around discovery protocols, it's drier reading but it's where the tricky questions come from.

The topology discovery stuff caught me off guard too, honestly. I'd been using Auvik daily for almost two years and figured hands-on time would carry me through — but the exam goes pretty deep on *how* the discovery process actually works under the hood, not just what it shows you on screen. Things like how Auvik uses SNMP and CDP/LLDP to build the relationship map, or what happens when devices don't support those protocols. That's not stuff you think about when you're just navigating the dashboard.

What helped me fill those gaps was the acp practice test on PracticeTestGeeks. A few of the questions specifically targeted topology and device relationship logic — the kind of "why does Auvik show this connection this way" questions that feel obvious in retrospect but trip you up if you haven't thought through the mechanics. Going through the explanations on the ones I got wrong was probably more useful than the questions themselves.

84% is a solid pass for that exam. The topology section being heavier than expected is something I've seen a few people mention — I think it's one of those areas where platform familiarity actually creates a blind spot, because you trust the map without ever questioning how it got built.

Yeah, topology discovery wrecked my first attempt too. I'd been using Auvik hands-on for over a year and figured that counted as studying. It doesn't. The exam asks about the logic behind how it maps relationships, not just what the UI looks like when it's done. Second time around I actually went through the documentation on how discovery works under the hood, and I also spent time on the acp/questions/integration and api management section because the two topics overlap more than you'd think -- integrations affect what gets discovered and how.

I passed on my second try with an 82%. Honestly the biggest change wasn't more hours, it was being more specific about what I didn't know. If you're retaking it, don't skip the API and integration material even if you're not using those features day to day. It shows up.

That topology section got me too, and I'd been using Auvik daily for over a year. What helped me most wasn't memorizing how the discovery works but really digging into why the wrong answers were wrong. Like when a practice question says Auvik "manually polls" devices for topology data, you don't just skip past that -- you stop and think through why that's incorrect at a fundamental level, what polling actually is versus what Auvik's agent-based approach does. Once you understand the mechanism, the wrong answers start sounding obviously off instead of plausibly close.

I went back through every question I missed and wrote out in plain language why each distractor was wrong, not just why the correct answer was right. It's slower but it builds a mental model that actually holds up when the exam rewords things. The topology questions specifically rely on you understanding how Auvik infers relationships, so if you're fuzzy on the "why" underneath it, a slightly reworded question will throw you. Sounds like you still crushed it at 84%, but that approach would've made those questions feel less like surprises.