Courseiva

CCNA Netflow Questions

8 questions · Netflow topic · All types, answers revealed

1
Drag & Dropmedium

Drag and drop the following steps into the correct order to export traffic data with Flexible NetFlow on an IOS-XE router and then verify it.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

A flow monitor refers to a flow exporter, so the exporter is defined first. The monitor is then defined (referencing the exporter), applied to an interface with ip flow monitor, and verified last with show flow monitor. IOS rejects a monitor that references an undefined exporter, and rejects applying a monitor that does not exist.

Exam trap

Be careful not to apply a flow monitor to an interface before it is defined, and remember that telemetry configuration must precede NetFlow export setup.

2
PBQhard

You are connected to R1, a Cisco ISR 4321 running IOS-XE. Configure SNMPv2c with the read-only community 'public' and SNMPv3 with user 'admin' (in group ADMINS, authPriv) using SHA authentication and AES-128 encryption. Send SNMP traps to the management server 203.0.113.10. Also configure Flexible NetFlow to export NetFlow version 9 records to 203.0.113.20 on UDP port 2055 for traffic entering GigabitEthernet0/0. Verify with show commands.

Network Topology
G0/0192.168.1.1/24Management NetworkR1Server

Hints

  • •An SNMPv3 user must belong to a group; create 'snmp-server group ADMINS v3 priv' first, then the user with auth sha and priv aes 128.
  • •Traps need 'snmp-server enable traps' and an 'snmp-server host' receiver.
  • •Flexible NetFlow needs an exporter (destination, transport udp 2055, export-protocol netflow-v9), a monitor that uses it, and the monitor applied to the interface.
A.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 2055 export-protocol netflow-v9 flow monitor MON1 exporter EXP1 record netflow ipv4 original-input interface GigabitEthernet0/0 ip flow monitor MON1 input
B.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 9996 export-protocol ipfix flow monitor MON1 exporter EXP1 record netflow ipv4 original-input interface GigabitEthernet0/0 ip flow monitor MON1 input
C.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth md5 AuthPass123 priv des PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 2055 export-protocol netflow-v9 flow monitor MON1 exporter EXP1 record netflow ipv4 original-input interface GigabitEthernet0/0 ip flow monitor MON1 input
D.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 2055 export-protocol netflow-v9 flow monitor MON1 exporter EXP1 record netflow ipv4 original-input
AnswerA
solution
! R1
configure terminal
snmp-server community public RO
snmp-server group ADMINS v3 priv
snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123
snmp-server enable traps
snmp-server host 203.0.113.10 traps version 2c public
flow exporter EXP1
destination 203.0.113.20
transport udp 2055
export-protocol netflow-v9
exit
flow monitor MON1
exporter EXP1
record netflow ipv4 original-input
exit
interface GigabitEthernet0/0
ip flow monitor MON1 input
end

Why this answer

SNMPv3 needs a group (snmp-server group ADMINS v3 priv) and a user in that group with auth sha and priv aes 128, and passwords of sufficient length. Traps require snmp-server enable traps and an snmp-server host for 203.0.113.10 (version 2c with the community). On an ISR 4321, NetFlow v9 export uses Flexible NetFlow: a flow exporter with destination 203.0.113.20, transport udp 2055 and export-protocol netflow-v9, a flow monitor using the exporter and a record, and the monitor applied to the interface with ip flow monitor MON1 input.

Without applying the monitor to the interface, no flows are exported.

Exam trap

Forgetting to include a group name and the 'v3' keyword in the 'snmp-server user' command is a common syntax error that will cause the configuration to be rejected on real devices.

Why the other options are wrong

B

Wrong export port and protocol.

C

Wrong SNMPv3 algorithms.

D

Monitor not applied to the interface.

3
Multi-Selectmedium

Which two statements accurately describe why NetFlow is useful for operations teams?

Select 2 answers
A.It helps identify which conversations or applications contribute to link utilization.
B.It can provide more detail than simple interface counters alone.
C.It replaces the need for all routing protocols.
D.It is the main wireless encryption protocol for guest access.
E.It eliminates the usefulness of Syslog.
AnswersA, B

NetFlow samples or captures packet metadata into flow records that identify source/destination IP, ports, and protocol, allowing engineers to rank traffic by conversation or application. This visibility pinpoints which specific flows (e.g., a video-streaming host or an application server) are responsible for congestion, transforming raw link utilization into actionable per-flow intelligence.

Why this answer

NetFlow is useful because it helps teams move beyond simple interface utilization and see which traffic conversations are responsible for usage. In practical terms, it can reveal which hosts, protocols, or applications are contributing to the traffic profile, making it valuable for troubleshooting, capacity planning, and security investigations. Option E is incorrect because NetFlow does not eliminate the usefulness of Syslog; Syslog provides device event logging while NetFlow provides traffic flow data, and both tools complement each other in network operations.

Exam trap

A frequent exam trap is mistaking NetFlow for a routing protocol, a security mechanism, or a replacement for Syslog.

Why the other options are wrong

C

Option C is incorrect because NetFlow does not replace routing protocols; it is a monitoring technology that provides visibility into traffic flows but does not perform routing functions or influence path selection.

D

Option D is incorrect as NetFlow is unrelated to wireless encryption protocols. Wireless encryption standards like WPA2 or WPA3 handle security, whereas NetFlow focuses on traffic flow monitoring.

E

Option E is incorrect because NetFlow does not eliminate the usefulness of Syslog. Syslog provides event logging and system messages, which complement NetFlow’s traffic flow data for comprehensive network monitoring.

4
PBQhard

You are connected to R1. R1 must send SNMPv2c traps (community public) to the management server at 203.0.113.10, provide SNMPv3 access for user admin in group MyGroup (SHA authentication and AES-128 privacy, password cisco123 for both), and export NetFlow records to the collector at 203.0.113.20 using NetFlow version 9. The exhibit shows what is currently configured. Apply the missing configuration.

Network Topology
G0/0203.0.113.1/24203.0.113.10linkR1Management Server

Hints

  • •Use the 'snmp-server host' command to specify the trap destination and community.
  • •For SNMPv3, you must first create a group with the appropriate security level before creating the user.
  • •NetFlow export version is configured globally with 'ip flow-export version'.
A.snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public snmp-server group MyGroup v3 priv snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123 ip flow-export version 9
B.snmp-server host 203.0.113.10 traps version 2c public snmp-server group MyGroup v3 priv snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123 ip flow-export version 9
C.snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public ip flow-export version 9
D.snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public snmp-server group MyGroup v3 priv snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123 ip flow-export destination 203.0.113.20 2055
AnswerA
solution
! R1
snmp-server enable traps
snmp-server host 203.0.113.10 traps version 2c public
snmp-server group MyGroup v3 priv
snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123
ip flow-export version 9

Why this answer

Traps require both a trap destination (snmp-server host ... traps version 2c public) and the global snmp-server enable traps command. SNMPv3 needs a group at the required security level (priv) and a user bound to it with SHA authentication and AES-128 privacy. NetFlow export already has a destination but runs the default version 1, so ip flow-export version 9 must be added.

Exam trap

Watch out for the SNMPv3 group keyword: 'priv' is required when using encryption (AES 128), not just 'auth'. Also, remember that the 'snmp-server user' command requires a group name. For NetFlow, the version is set with 'ip flow-export version 9', not 'ip flow-export destination'.

How to eliminate wrong answers

Option A is correct because it includes all required commands with proper syntax. Option B is wrong because the group uses 'auth' instead of 'priv', which is needed for AES encryption. Option C is wrong because it omits the group configuration entirely.

Option D is wrong because it uses 'ip flow-export destination' instead of 'ip flow-export version 9'.

5
Multi-Selectmedium

A network team wants to collect flow-level traffic statistics from routers to identify top talkers and bandwidth consumers. Which two statements about NetFlow are correct?

Select 2 answers
A.It summarizes traffic into flows instead of capturing every packet payload
B.It is primarily used to distribute time from an authoritative clock
C.It can help identify which conversations consume the most bandwidth
D.It replaces routing protocols by advertising reachability information
AnswersA, C

NetFlow operates by grouping packets that share common attributes—like IP addresses, port numbers, protocol, and ToS—into unidirectional flows, then exporting a summary record containing counters and timestamps. This avoids the storage and processing overhead of capturing every packet's full payload, making it efficient for long-term traffic analysis. Unlike deep packet inspection, NetFlow does not reconstruct or retain the application data itself, only the flow metadata.

Why this answer

NetFlow provides visibility into who is talking to whom, with what protocols and volume, making it valuable for capacity planning, troubleshooting, and security analysis.

Exam trap

A frequent exam trap is mistaking NetFlow for protocols that distribute time or routing information. For example, option B incorrectly associates NetFlow with NTP, which synchronizes clocks, and option D wrongly suggests NetFlow replaces routing protocols by advertising reachability. These misconceptions arise because candidates may not clearly differentiate between monitoring technologies and control plane protocols.

Remember, NetFlow only summarizes traffic flows for analysis and does not participate in routing or time synchronization. Confusing these roles can lead to selecting incorrect answers under exam pressure.

Why the other options are wrong

B

Option B is incorrect because distributing time from an authoritative clock is the function of NTP, not NetFlow, which is a traffic monitoring protocol.

D

Option D is incorrect because NetFlow does not replace routing protocols or advertise reachability information; it only monitors traffic flows.

6
PBQhard

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.

Network Topology
G0/010.0.0.1/30G0/010.0.0.2/30linkG0/110.10.10.1/2410.10.10.0/24linkR1R2Internal Network

Hints

  • •Remember to specify the SNMP version when configuring the trap receiver host.
  • •NetFlow version 9 must be explicitly configured; otherwise, version 5 is used by default.
  • •Apply the flow monitor to the interface that connects to the network you want to monitor (G0/1).
A.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.
B.Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 5. Apply flow monitor to all interfaces.
C.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.
D.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.
AnswerA
solution
! R1
snmp-server community monitorRO RO
snmp-server community controlRW RW
snmp-server enable traps snmp linkdown linkup
snmp-server host 203.0.113.100 version 2c monitorRO
flow exporter EXPORTER-TO-SERVER
destination 203.0.113.100
transport udp 2055
source Loopback0
export-protocol netflow-v9
exit
flow monitor MONITOR-10NET
record netflow ipv4 original-input
exporter EXPORTER-TO-SERVER
exit
interface GigabitEthernet0/1
ip flow monitor MONITOR-10NET input
end

Why this answer

SNMP is configured with the two communities, link up/down traps, and the trap host 203.0.113.100 using version 2c. NetFlow version 9 is configured with Flexible NetFlow: an exporter (destination 203.0.113.100, UDP 2055, export-protocol netflow-v9), a flow monitor using a predefined record, and the monitor applied inbound on G0/1, the interface where traffic from 10.10.10.0/24 enters R1. Verify with show snmp, show flow exporter and show flow monitor MONITOR-10NET cache.

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.

Why the other options are wrong

B

The question explicitly requires NetFlow version 9, and traffic monitoring must be limited to the 10.10.10.0/24 network.

C

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.

D

NetFlow requires a flow monitor to be applied to an interface to capture traffic; it does not automatically monitor all traffic.

7
PBQhard

You are connected to R1 via the console. SNMP v2c community strings (public RO, private RW) are already configured. The network has a management server at 10.1.1.100 and a NetFlow collector at 10.1.1.200. Configure SNMP traps to the management server for link status changes. Also configure NetFlow on interface GigabitEthernet0/0 to export version 9 to the collector, with a source interface of Loopback0 (10.255.255.1/32).

Network Topology
G0/0G0/010.1.1.10010.1.1.200R210.0.0.1/30R1MGMT_ServerNMS_Collector

Hints

  • •SNMP traps require both a host command and enabling specific trap types.
  • •NetFlow export needs destination, version, and source interface, plus flow ingress on the interface.
  • •Use 'show running-config | section snmp|flow' to verify your changes.
A.snmp-server host 10.1.1.100 version 2c public snmp-server enable traps snmp linkdown linkup ip flow-export destination 10.1.1.200 2055 ip flow-export version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress
B.snmp-server host 10.1.1.200 version 2c private snmp-server enable traps ip flow-export destination 10.1.1.100 2055 version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow egress
C.snmp-server host 10.1.1.100 version 2c private snmp-server enable traps ip flow-export destination 10.1.1.200 2055 version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress
D.snmp-server host 10.1.1.100 version 2c public snmp-server enable traps snmp linkdown linkup ip flow-export destination 10.1.1.200 2055 version 5 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress
AnswerA
solution
! R1
snmp-server host 10.1.1.100 version 2c public
snmp-server enable traps snmp linkdown linkup
ip flow-export destination 10.1.1.200 2055
ip flow-export version 9
ip flow-export source Loopback0
interface GigabitEthernet0/0
ip flow ingress

Why this answer

The current configuration has SNMP community strings but lacks trap destinations and NetFlow export. To fix, you must configure snmp-server host 10.1.1.100 version 2c public to send traps, and snmp-server enable traps snmp linkdown linkup is required to send link status changes. For NetFlow, you need ip flow-export destination 10.1.1.200 2055 and then ip flow-export version 9 to set the export version.

Also configure ip flow-export source Loopback0 and apply ip flow ingress on GigabitEthernet0/0. Verification commands confirm the settings.

Exam trap

Pay close attention to the IP addresses: the management server (10.1.1.100) is for SNMP traps, and the collector (10.1.1.200) is for NetFlow. Also, remember that SNMP traps use the read-only community, and NetFlow version must match the requirement (version 9).

Why the other options are wrong

B

The specific factual error: The SNMP trap destination and NetFlow export destination are swapped, and the flow direction is egress instead of ingress.

C

Enables every trap type instead of linkdown/linkup, and uses invalid NetFlow export syntax.

D

The specific factual error: NetFlow export version is set to 5, but the requirement is version 9.

8
MCQhard

A network administrator notices that syslog messages from a core router are arriving at the syslog server with timestamps that are hours behind other devices. The router’s NetFlow exports also show incorrect start and end times for flows, making traffic analysis unreliable. The administrator verifies that all router interfaces are up and that the SNMP community strings on the router match the NMS.

A.The logging trap level is set to informational, so only high-severity messages are sent with correct timestamps.
B.The router’s NTP client is configured with an incorrect authentication key.
C.The SNMP v3 user’s privacy password is incorrect, causing the NMS to reject syslog traps.
D.The IP flow cache timeout is set too low, causing NetFlow timestamps to appear skewed.
AnswerB

NTP can use authentication keys to verify server identity. If the client key does not match the server’s key, the router will not trust the time updates and will fail to synchronize. This leaves the router’s clock uncorrected, causing incorrect timestamps in syslog and NetFlow records.

Why this answer

The router's timestamps are incorrect for both syslog messages and NetFlow exports, which points to a system-wide time synchronization issue. NTP (Network Time Protocol) is responsible for maintaining accurate time on network devices, and if the NTP client is configured with an incorrect authentication key, it will fail to synchronize with the NTP server, causing the router's clock to drift. This explains why all time-stamped data (syslog and NetFlow) is consistently behind.

Exam trap

Cisco often tests the distinction between time synchronization issues (NTP) and logging/SNMP configuration issues, so candidates may incorrectly attribute timestamp problems to syslog or SNMP settings rather than the underlying system clock.

Why the other options are wrong

A

Logging trap level controls which severity messages are forwarded, not the accuracy of the timestamps.

C

SNMP v3 misconfiguration impacts SNMP traps, not syslog messages, which are sent independently via a different transport.

D

Cache timeout affects flow export frequency, not the accuracy of the timestamps inside the flow data.

Ready to test yourself?

Try a timed practice session using only Netflow questions.