CCNA AI and Network Operations Practice Question
Network Topology
You are connected to R1. Configure SNMP v2c with a read-only community string 'monitorRO' and a read-write community string 'controlRW', and enable SNMP traps for link status to the management server at 203.0.113.100. Additionally, configure NetFlow to export version 9 flow records to the same server on UDP port 2055, and ensure that only traffic from the 10.10.10.0/24 network is monitored. Finally, verify your configurations with the appropriate show commands.
⚠ Common exam trap
Common mistakes include mixing legacy and Flexible NetFlow commands (e.g., using the global `ip flow-export version` instead of setting it under the flow exporter), forgetting to apply the flow monitor to an interface, and enabling all SNMP traps rather than only link-status traps.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure SNMP community strings, enable link-status traps, set trap destination, configure NetFlow export version 9, and apply flow monitor to interface(s) carrying 10.10.10.0/24 traffic.
The solution correctly configures SNMP v2c with the required read-only and read-write community strings, enables only link-status traps, and sets the trap destination. For NetFlow, it uses Flexible NetFlow by defining a flow record, an exporter, and a monitor. Importantly, the export version (9) must be configured under the flow exporter, not with the legacy global `ip flow-export version 9` command. The flow monitor is applied to GigabitEthernet0/1, which carries traffic from the 10.10.10.0/24 network. Verification can be done with `show snmp` to confirm communities and trap receivers, and `show flow monitor name MONITOR-10NET cache` or `show ip cache flow` to view exported flow records.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure SNMP community strings, enable link-status traps, set trap destination, configure NetFlow export version 9, and apply flow monitor to interface(s) carrying 10.10.10.0/24 traffic.
Why this is correct
Ly includes all required steps: SNMP v2c community strings (read-only and read-write), trap enablement for link status, trap receiver configuration, NetFlow export version 9, and applying the flow monitor to the appropriate interface(s) to monitor only the 10.10.10.0/24 network.
- ✗
Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 5. Apply flow monitor to all interfaces.
Why it's wrong here
Selecting NetFlow export version 5 instead of version 9 limits the collector to fixed-format records without support for newer IPFIX-like flexible fields, which is insufficient for modern traffic analysis. More critically, applying the flow monitor to all interfaces broadens data collection beyond the 10.10.10.0/24 subnet, so the monitor would capture flows for other networks and violate the requirement to scope monitoring only to interfaces carrying that specific traffic. The SNMP components are correct, but the flow monitor must be attached only to the interfaces that actually transport 10.10.10.0/24 traffic.
- ✗
Configure SNMP community strings, enable all SNMP traps, set trap destination, and configure NetFlow export version 9. Apply flow monitor to interface with IP 10.10.10.0/24.
Why it's wrong here
It enables all SNMP traps instead of only link-status traps, and applying the flow monitor to an interface with IP 10.10.10.0/24 is not valid; the flow monitor should be applied to interfaces that carry traffic from that network.
- ✗
Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 9. Do not apply any flow monitor; NetFlow automatically monitors all traffic.
Why it's wrong here
Using NetFlow export version 9 is correct, but this option is fatally incomplete because no flow monitor is actually attached to any interface. NetFlow does not automatically monitor all traffic; a flow monitor only begins exporting data after it is applied to an interface with the 'ip flow monitor' command. Without that application step, the router will not collect or export any flow records, so the NetFlow requirement is entirely unmet even though the SNMP trap configuration is valid.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓Configure SNMP community strings, enable link-status traps, set trap destination, configure NetFlow export version 9, and apply flow monitor to interface(s) carrying 10.10.10.0/24 traffic.Correct answer▾
Why this is correct
Ly includes all required steps: SNMP v2c community strings (read-only and read-write), trap enablement for link status, trap receiver configuration, NetFlow export version 9, and applying the flow monitor to the appropriate interface(s) to monitor only the 10.10.10.0/24 network.
✗Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 5. Apply flow monitor to all interfaces.Wrong answer — click to see why▾
Why this is wrong here
The question explicitly requires NetFlow version 9, and traffic monitoring must be limited to the 10.10.10.0/24 network.
Why candidates choose this
Candidates might default to version 5 because it is the default version, and applying to all interfaces seems simpler.
✗Configure SNMP community strings, enable all SNMP traps, set trap destination, and configure NetFlow export version 9. Apply flow monitor to interface with IP 10.10.10.0/24.Wrong answer — click to see why▾
Why this is wrong here
Enabling all traps is unnecessary and may cause unwanted overhead; the flow monitor must be applied to the correct interface(s) based on traffic flow, not the network address.
Why candidates choose this
Candidates might think enabling all traps is safer, and misunderstand the interface application as needing the network IP.
✗Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 9. Do not apply any flow monitor; NetFlow automatically monitors all traffic.Wrong answer — click to see why▾
Why this is wrong here
NetFlow requires a flow monitor to be applied to an interface to capture traffic; it does not automatically monitor all traffic.
Why candidates choose this
Candidates might assume that configuring the export destination is sufficient, but the flow monitor must be explicitly applied.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Agentic AI in Network Operations
Key term
User Datagram Protocol
User Datagram Protocol (UDP) is a fast, connectionless network protocol that sends data without first checking if the receiver is ready or if the data arrived safely.
Key term
NetFlow
NetFlow is a network protocol developed by Cisco that collects and monitors IP traffic data to provide visibility into network usage, performance, and security.
About these practice questions
One of 1,389 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.