nerdexam
F5

201 · Question #24

The ICMP monitor has been assigned to all nodes. In addition, all pools have been assigned custom monitors. If a pool eb.is marked vailable. The ICMP monitor has been assigned to all nodes. In additio

The correct answer is D. Over 25% of the eb.pool members have had their content updated and it no longer matches the receive rule. This question addresses the conditions required for a BIG-IP pool to be marked 'available' (green) when both node-level ICMP monitors and pool-level custom monitors are configured.

Section 2: Configure Load Balancing Features

Question

The ICMP monitor has been assigned to all nodes. In addition, all pools have been assigned custom monitors. If a pool eb.is marked vailable. The ICMP monitor has been assigned to all nodes. In addition, all pools have been assigned custom monitors. If a pool .eb.is marked .vailable (green) which situation is sufficient to cause this.

Options

  • AAll of the eb.pool member nodes are responding to the ICMP monitor as expected.All of the .eb.pool.
  • BLess than 50% of the eb.pool member nodes responded to the ICMP echo request.Less than 50% of
  • CAll of the members of the eb.pool have had their content updated recently and their responses no longer
  • DOver 25% of the eb.pool members have had their content updated and it no longer matches the receive rule

How the community answered

(32 responses)
  • A
    3% (1)
  • B
    6% (2)
  • C
    16% (5)
  • D
    75% (24)

Why each option

This question addresses the conditions required for a BIG-IP pool to be marked 'available' (green) when both node-level ICMP monitors and pool-level custom monitors are configured.

AAll of the eb.pool member nodes are responding to the ICMP monitor as expected.All of the .eb.pool.

While all nodes responding to ICMP means the underlying nodes are up, the pool's availability is ultimately determined by its custom monitors checking the *service* health of its members, not just node pingability.

BLess than 50% of the eb.pool member nodes responded to the ICMP echo request.Less than 50% of

If less than 50% of member nodes responded to ICMP, it would likely lead to many pool members being marked down, which would typically cause the pool itself to be unavailable.

CAll of the members of the eb.pool have had their content updated recently and their responses no longer

If all members' responses no longer match the custom monitor's receive rule, then all members would be marked 'down' by their custom monitor, causing the entire pool to be marked 'unavailable' (red).

DOver 25% of the eb.pool members have had their content updated and it no longer matches the receive ruleCorrect

If 'over 25% of the eb.pool members have had their content updated and it no longer matches the receive rule', this means that at least 75% of the pool members are still matching the custom monitor's receive rule and are therefore marked 'available'. With 75% or more members being available, the pool as a whole would typically be marked 'available' (green), assuming the pool's minimum availability requirements are met (e.g., at least one member is up, or a percentage threshold is met).

Concept tested: BIG-IP pool availability and monitor interaction

Source: https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-local-traffic-management-concepts/monitors.html

Topics

#health monitor#node monitor#pool monitor#monitor logic

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 201 Practice