An operator created a Virtual Service and wants to enable non-significant logs for only that specific Virtual Service. Which action, if any, will meet this goal?

Question

Options

• AThe CLI must be used to create a Virtual Service with non-significant logs enabled.
• BEnable non-significant logs in the Analytics tab of the Virtual Service.
• CThis goal cannot be met because non-significant logs are defined globally.
• DCreate a dedicated Application Profile, and assign it to the Virtual Service.

• A
  2% (1)
• B
  93% (39)
• C
  5% (2)

Explanation

Option B is correct because, in VMware NSX Advanced Load Balancer (Avi Networks), each Virtual Service has its own Analytics tab in the UI where logging behavior - including non-significant (non-error) logs - can be enabled on a per-Virtual Service basis without touching any global setting.

Why the distractors are wrong:

• A is incorrect because the CLI is not required; the UI fully supports enabling this setting, making "must use CLI" a false constraint.
• C is incorrect because non-significant logs are not exclusively a global configuration - they can be scoped to an individual Virtual Service, which is exactly the scenario described.
• D is incorrect because Application Profiles govern protocol-level behavior (e.g., HTTP, TCP settings), not logging configuration; assigning a custom profile would not control non-significant log capture.

Memory tip: Think "Analytics tab = per-VS log control." If the question mentions where to configure logging for a specific Virtual Service, navigate mentally to that Virtual Service's Analytics tab - that's always where Avi exposes per-VS log toggles.

No community discussion yet for this question.