6V0-22.25 Exam Preparation Material | VMware Avi Load Balancer 30.x Administrator

Explanation:
Avi Virtual Services can listen on multiple ports, and some deployments require different port and protocol mappings for the same Virtual Service configuration. The simplified Basic Mode wizard is intended for common application deployment and does not expose the full set of Virtual Service options. Broadcom’s Avi documentation states that creating a Virtual Service in Advanced Setup allows administrators to configure all options through the available tabs. Documentation for mapping multiple Virtual Service ports also describes using the Virtual Service editor settings to define multiple service ports. Therefore, when a new Virtual Service must support multiple ports and network protocols, the correct method is to use Advanced Mode, where the full port, profile, and protocol configuration is available.

Explanation:
Avi Load Balancer Network Security Policies operate at the network security layer and are used to control whether traffic is accepted, discarded, denied, or rate-limited before higher-level HTTP processing occurs. Broadcom’s Avi documentation specifically describes Network Security Policy behavior as determining whether a connection should be accepted, discarded, or rate-limited. Because of this, Rate Limit is a valid Network Security Policy action. “Send Local Response” and “Redirect” are HTTP-layer actions that belong to HTTP policies, not Network Security Policies. “Continue” is commonly associated with policy flow processing in other policy types but is not the correct Network Security Policy action in this question. Therefore, the valid action from the listed options is Rate Limit.

Explanation:
Avi Load Balancer collects analytics metrics at different frequencies depending on whether real-time metrics are enabled. VMware Avi documentation explains that a newly created Virtual Service captures analytics aggressively for the first 30 minutes, but after that period the update frequency slows down unless real-time metrics are enabled. This behavior commonly appears as graph data updating every five minutes instead of continuously or near real time. The issue is not caused by the GUI refresh interval, and selecting “Average Values” is not the root cause. The timeframe of “Past 30 Minutes” can show recent data, but it does not automatically enable real-time collection. Therefore, the correct explanation is that, by default, the Real Time Metrics option is not enabled for the Virtual Service.

Explanation:
Avi Load Balancer supports sharing a single VIP across multiple Virtual Services when each Virtual Service uses a different service port. This is useful when multiple applications or protocols must use the same IP address but separate listener ports, profiles, pools, and policies. Broadcom documentation for sharing a single VIP across multiple Virtual Services describes selecting an existing VS VIP while creating another Virtual Service. This avoids manually typing the same IP address as a separate allocation, which could create duplicate or inconsistent VIP configuration. Creating a child Virtual Service is used for other use cases, such as SNI or parent-child designs, not simply reusing the same VIP on a different port. Therefore, the correct method is to use Advanced Setup and select the existing VS VIP.

Explanation:
VMware Avi Load Balancer supports scaling a Virtual Service across multiple Service Engines. The documentation for automatic scaling of Virtual Services references using the Scale Out action for a Virtual Service to increase the number of Service Engines actively supporting that Virtual Service. Therefore, the correct action is to use the Scale Out button in the Virtual Service popup.