All Pool resources are "Down" and not available, but the Virtual Service port is still responding. The operator would like the VS port to not respond when there are no Pool resources available…

Question

Options

• APool -> Advanced -> "Remove listening port when VS is down"
• BVirtual Service -> Advanced -> "Remove listening port when VS is down"
• CPool -> Settings -> "Ignore reachability constraints for server pool"
• DVirtual Service -> Settings -> "Ignore reachability constraints for server pool"

• A
  12% (3)
• B
  8% (2)
• C
  76% (19)
• D
  4% (1)

Explanation

Option C is correct because "Ignore reachability constraints for server pool" is the Pool-level setting that controls whether the Virtual Service respects the health of its pool members. When this option is enabled, the VS stays up and continues listening even if all pool servers are down - which is exactly the problematic behavior described. Disabling it forces the VS to take itself offline when no healthy pool resources remain.

Why the distractors are wrong:

• A is wrong because "Remove listening port when VS is down" doesn't exist as a Pool-level setting - it's a VS-level concept, and the path itself is fabricated.
• B is wrong because "Remove listening port when VS is down" addresses a scenario where the VS itself is administratively or explicitly marked down, not one driven by pool member health.
• D is wrong because the reachability constraint setting belongs to the Pool configuration, not the Virtual Service settings - placing it under VS Settings is a location trick.

Memory tip: Think of it as a chain: Pool health → VS availability. The word "Ignore" is the red flag - if you're ignoring pool reachability, you're telling the system "keep the VS up no matter what." To make the VS go dark with the pool, you must stop ignoring that constraint at the Pool level.

No community discussion yet for this question.