An administrator wants to increase the number of active Service Engines utilized by a Virtual Service for more performance. Which action, if any, should be taken to meet this goal?

Question

Options

• ANo action is necessary since the data plane is scaled automatically.
• BUse the Scale Out button in the Service Engine Group configuration.
• CUse the Scale Out button in the Virtual Service popup.
• DUse the Migrate button in the Virtual Service popup.

• A
  7% (3)
• B
  2% (1)
• C
  89% (39)
• D
  2% (1)

Explanation

Option C is correct because in Avi Networks (NSX Advanced Load Balancer), scaling out a specific Virtual Service is performed directly from the Virtual Service's action menu, which contains a Scale Out button that manually adds another Service Engine to handle that VS's traffic.

Why the distractors are wrong:

• A is incorrect because while auto-scaling policies can be configured, the administrator here wants to manually trigger a scale-out - auto-scaling requires threshold conditions to be met and may not act immediately.
• B is incorrect because the Service Engine Group configuration defines policies and limits (max SEs, placement rules), but it does not trigger a scale-out action for a running Virtual Service.
• D is incorrect because the Migrate button moves a Virtual Service from one SE to another - it's a 1-for-1 relocation, not an expansion of capacity.

Memory tip: Match the action to the object - you want to scale a Virtual Service, so the button lives on the Virtual Service, not on the group that manages the underlying infrastructure.

No community discussion yet for this question.