What is missing from this Flexible NetFlow configuration to begin collecting data?
- The flow monitor is not applied to an interface
- The transport protocol should be TCP
- The exporter destination is incorrect
- The flow record does not match any traffic
Explanation: According to the sources, configuring Cisco Flexible NetFlow (FNF) is a mandatory four-step process .
The first three steps involve creating a flow record to define the data to be tracked, a flow exporter to specify the destination for the data, and a flow monitor to link the record and exporter together .
However, the final and critical step required to begin collecting data is applying the flow monitor to a specific interface in either the input or output direction .
The sources explicitly state that the ip flow monitor command must be applied "so that the newly defined flow monitor can start to gather information about traffic flows" .
Without this attachment to an interface, the configuration remains dormant and will not populate the flow cache or generate statistics .
Related exam: CCNP ENARSI v9 Course Final Exam
