How to configure flexible NetFlow idle timeout on Cisco switches?
Short answer
B flow monitor monitorflow
Question
Key Takeaways
The exam tests understanding of flow monitor configuration for idle timeout, with the common trap being confusion between flow record and flow monitor commands.
This question tests the configuration of flexible NetFlow idle timeout settings to prevent flow connector overload. Community consensus leans toward Option B, though some members note potential issues with immediate cache type behavior.
Common mistake: Many candidates choose options that configure flow record instead of flow monitor, missing that idle timeout settings belong under the flow monitor configuration.
Expert Analysis
Why the Answer Is Correct
Option B correctly applies the flow monitor command with idle timeout configuration. The flow monitor is responsible for managing flow cache behavior and timeout settings, making it the appropriate place for idle timeout configuration. This aligns with Cisco's flexible NetFlow architecture where monitors control cache management.
Why the Other Options Are Wrong
Options A and D incorrectly use flow record commands, which are designed for defining what data to collect rather than managing cache timeouts. Option C is incomplete as it lacks the necessary flow monitor command structure to properly configure timeout settings. The flow record defines the fields to capture, while flow monitor controls the caching and export behavior.
Community Comment Notes
Comment #2 raises a valid concern about immediate cache type behavior, noting that timeout settings may be ignored for immediate cache types according to Cisco documentation. This suggests the question may have ambiguity regarding cache type selection. Comment #4 acknowledges this complexity, noting that while permanent cache might be more appropriate, immediate cache behavior can still be configured without calculation errors.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
Focus on understanding the distinction between flow record (data collection definition) and flow monitor (cache management and export). When troubleshooting NetFlow timeout issues, always check the flow monitor configuration first.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
slacker_at_work 👍 4 Answered B- Option A is incorrect because it repeats the "record recordflow" command unnecessarily. - Option C is incorrect because it does not include the "flow monitor" command to set up the flexible NetFlow monitor. - Option D is incorrect because it does not include the necessary configuration for exporting flow records based on idle timeout.
-
Mistwalker 👍 2All of these seem wrong. Timeout settings are ignored for immediate cache type per the below doc, and answer C doesn't configure a flow record. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fnetflow/command/fnf-cr-book/fnf-c1.html#wp3880665773 "The timeout settings have no effect for the immediate cache type."
-
lukas2023 👍 1 Answered BThis is a sharp turn in the brain, immediate will be derived whether it is 20s or not, permanent is better, but immediate can not be calculated wrong
-
chiacche 👍 1 Answered Bflow record -> How do we collect data? flow monitor -> controller
-
teems5uk 👍 2 Answered BCorrect
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All 350-401 Questions
Access 218 questions with complete answers and detailed explanations.
View Full 350-401 Practice Test →