On game day the stadium NOC needs top talkers and conversation visibility across uplinks. Which technology best supplies that Flexible NetFlow-style traffic visibility?
Select an answer to reveal the explanation.
Short Explanation
NetFlow is the stadium turnstile counter for conversations—who talked to whom, how much, how often. Point the exporter at a collector and top talkers light up on game day without SPAN’ing every uplink into a suitcase analyzer.
Full Explanation
On game day the stadium NOC needs top talkers and conversation visibility across uplinks. Flexible NetFlow exporting flow records so collectors can identify top talkers and conversation patterns best supplies that visibility. Flow records keyed by configured match fields summarize who talked to whom, over which ports/protocols, and with what volume—exactly what a stadium NOC needs when uplinks spike and operators must separate video, Wi-Fi guest bursts, and backend traffic without SPAN’ing every link.
HSRP preempt alone ranking talkers by virtual MAC priority fails because preempt controls FHRP active reclamation; it does not produce top-talker conversation analytics. IGMP snooping reports that list unicast TCP top talkers per access port fail because snooping tracks multicast receiver interest, not unicast TCP talker rankings. Static NAT one-to-one mappings used as a substitute bandwidth report fail because static NAT entries are address bindings, not flow-volume analytics.
Exam caveat: Flexible NetFlow = visibility/export of flow caches; it informs capacity and security review but does not by itself enforce policy like an ACL. Do not pick FHRP, IGMP, or NAT distractors when the stem asks for top talkers/conversations.
Operational check: confirm flow monitor/record/exporter are applied on the stadium uplinks, verify collector receipt of templates and data, and generate a known test conversation to ensure it appears among top talkers during a game-day rehearsal.