300-410 Practice Question: Which statement correctly describes the default…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  BGP next-hop is always collected by default in Flexible NetFlow monitors.

  Why it's wrong here

  BGP next-hop is an optional field that must be explicitly added to a flow record; it is not part of the default key or non-key fields, so monitors do not collect it automatically. It is tempting because BGP next-hop is a recognised NetFlow field, but recognition differs from default inclusion in every monitor.

• ✗

  BGP next-hop is never collected in Flexible NetFlow, only in traditional NetFlow.

  Why it's wrong here

  Flexible NetFlow supports BGP next-hop as an optional field within a flow record, so it can be exported when explicitly configured; the claim that only traditional NetFlow collects it is false. It is tempting because BGP next-hop is not part of the default key or non-key field set, so many records omit it unless added.

• ✓

  BGP next-hop is collected only if the flow record includes the 'match routing bgp next-hop' command.

  Why this is correct

  BGP next-hop is not part of the default key or non-key fields; it must be explicitly added to the flow record via 'match routing bgp next-hop'. Without that command, the exporter omits it, so the option correctly ties collection to that record configuration.

• ✗

  BGP next-hop is collected by default only for IPv4 flows.

  Why it's wrong here

  BGP next-hop collection is not tied to IP version; it is an optional field omitted from default flow records for both IPv4 and IPv6. It is tempting because IPv4 is the common deployment, but the field's presence depends on explicit configuration within the flow record, not on the protocol version.

Go deeper

Related to this question