Refer to the exhibit. The DevOps team noticed missing NetFlow dataduring peak utilization times for remote branches. Which configuration allows for this issue to be minimized or resolved?

Changing the transport type from UDP to TCP for NetFlow export is generally not recommended as UDP is more efficient for this purpose, and TCP would introduce overhead for retransmissions without directly addressing missing data.

Configuring NetFlow on both the in and out directions of an interface ensures that all traffic passing through is captured, preventing gaps in data during peak utilization. This maximizes the visibility of network flows and provides a complete picture of traffic patterns.

Changing the flow monitor to IPv6 from IPv4 only changes the IP address family being monitored, which is unrelated to ensuring all traffic is captured regardless of IP version.

Configuring long byte counters in a flow record provides higher precision for traffic volume measurement but does not inherently ensure that all flows are captured in the first place.