An administrator is tasked to enable a WAF Policy that was created by a fellow administrator in NSX Advanced Load Balancer. How should this task be completed?

Question

Options

• AEnable the policy by associating it with a Virtual Service
• BAttach the policy to the Service Engine
• CAssociate the policy to the Pool
• DConfigure the policy in the Application Profile

• A
  85% (17)
• B
  10% (2)
• C
  5% (1)

Explanation

In NSX Advanced Load Balancer (Avi Networks), a WAF Policy becomes active only when it is associated with a Virtual Service - the logical entity that represents a load-balanced application endpoint and is where traffic inspection actually occurs. Without that association, the policy exists but is never enforced against any traffic.

Why the distractors are wrong:

• B (Service Engine): Service Engines are the data-plane VMs that process traffic; they don't directly receive policy assignments - policies are applied at the Virtual Service layer above them.
• C (Pool): Pools define backend server groups for load balancing; WAF policies operate on incoming client-to-VIP traffic, not on the server-side pool configuration.
• D (Application Profile): Application Profiles define protocol behavior (HTTP settings, connection limits, etc.) and are not the attachment point for WAF policies.

Memory tip: Think of the Virtual Service as the "front door" of your application - WAF (Web Application Firewall) guards the door, so it must be attached at the door (Virtual Service), not to the engine room (Service Engine) or the back warehouse (Pool).

No community discussion yet for this question.