A Service Engine on which the Virtual Service is placed is experiencing a high level of memory utilization, but users of the application are not experiencing any issues. What impact, if any, will…

Question

Options

• AThe Virtual Service's Health Score will not be impacted.
• BThe Performance score will be reduced.
• CThe Security Penalty will be increased.
• DThe Resource Penalty will be increased.

• A
  2% (1)
• B
  81% (34)
• C
  12% (5)
• D
  5% (2)

Explanation

Option B is correct because in VMware NSX Advanced Load Balancer (Avi Networks), the Virtual Service Health Score includes a Performance component that accounts for Service Engine resource conditions - including memory utilization - even when users haven't yet experienced degradation. The system proactively reduces the Performance score as a predictive signal that the SE is under strain and may soon impact user experience.

Why the distractors are wrong:

• A is wrong because high SE memory utilization does affect the Health Score - the monitoring system is designed to flag resource pressure before it becomes user-visible.
• C is wrong because the Security Penalty is reserved for security-related concerns (e.g., DDoS indicators, policy violations), not resource metrics.
• D is the most tempting distractor, but in Avi's health scoring model, the Resource Penalty specifically tracks application-layer resource exhaustion (e.g., connection table limits, packet drops) - not raw SE hardware utilization like memory.

Memory tip: Think of the Health Score's Performance component as "how healthy is the infrastructure supporting this VS, right now?" - Avi scores performance proactively, so SE memory pressure lowers Performance before users complain. The Resource Penalty, despite its name, applies to application-level resource limits, not SE hardware metrics.

No community discussion yet for this question.