Passive Monitoring and Probe-Free Performance Monitoring Quiz

<p>TCP traffic (D)</p> Signup and view all the answers

<p>Target servers and protocols (C)</p> Signup and view all the answers

<p>Configuring multiple health checks and members (B)</p> Signup and view all the answers

<p>Members are always alive (B)</p> Signup and view all the answers

<p>Only measuring TCP traffic (B)</p> Signup and view all the answers

<p>It uses probes for each health check (D)</p> Signup and view all the answers

<p>Doesn't provide accurate performance metrics (A)</p> Signup and view all the answers

<p>RTT of TCP connection setup and teardown (B)</p> Signup and view all the answers

<p>Jitter and packet loss (B)</p> Signup and view all the answers

<p>Dead members (C)</p> Signup and view all the answers

<p>Passive-wan-health-measurement (C)</p> Signup and view all the answers

<p>Auto-asic-offload (C)</p> Signup and view all the answers

<p>Actual traffic passing through the members (A)</p> Signup and view all the answers

<p>Lack of granularity (B)</p> Signup and view all the answers

<p>Measure the member quality based on the performance of applications (A)</p> Signup and view all the answers

<p>Averages the metrics measured for all applications (C)</p> Signup and view all the answers

<p>Passive-measurement (B)</p> Signup and view all the answers

Passive monitoring measures network member performance based on actual traffic passing through them, without sending out probes.

Active monitoring sends probes to network members to check their health and performance.

Passive monitoring is more accurate because it uses real network traffic to assess member performance.

Passive monitoring simplifies configuration and reduces network traffic by not sending probes.

Passive monitoring measures key network metrics such as packet loss, latency, and jitter using TCP traffic.

Active monitoring needs you to specify target servers and protocols to send health checks.

Active monitoring can become complex when you need to configure multiple health checks for different network members.

Passive monitoring is disabled for hardware acceleration because members are considered always active in this scenario.

Passive monitoring has limitations as it can only measure TCP traffic, neglecting other protocols.

Active monitoring generates more network traffic than passive monitoring because it sends probes for each health check.

Using a ping probe for traffic, for example, web traffic, doesn't accurately reflect the actual performance of the web application.

Passive monitoring calculates latency from the Round Trip Time (RTT) of TCP connection setup and teardown.

Passive monitoring uses TCP header information to measure jitter and packet loss.

Passive monitoring cannot detect dead members because it only measures traffic from active members.

Enabling "passive-wan-health-measurement" in firewall policies allows passive monitoring to function.

Enabling "passive-wan-health-measurement" automatically disables "Auto-asic-offload" for better accuracy.

Passive monitoring provides more precise member metrics by analyzing actual traffic flowing through them.

Lack of granular information in passive monitoring may affect the decisions made by FortiGate for SD-WAN rules configured for specific applications.

Per-application passive monitoring instructs FortiGate to measure member quality based on the performance of specific applications.

In per-application passive monitoring, if multiple applications use the same member, FortiGate averages the metrics measured for all applications.

To enable per-application passive monitoring, you need to enable "Passive-measurement" in SD-WAN rules.