6V0-22.25 Exam Questions & Answers

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.

Avi Load Balancer data-plane performance is provided by Service Engines, so scaling performance means increasing Service Engine processing capacity or distributing traffic across more Service Engines. Broadcom documentation for Autoscale Service Engines states that Avi supports three techniques to scale data-plane performance: vertical scaling of individual Service Engine performance, native horizontal scaling of Service Engines in a group, and ECMP horizontal scale-out. Increasing individual SE resources is vertical scaling. Native horizontal scale-out places a Virtual Service across multiple SEs using Avi's native scale-out model. ECMP horizontal scale-out distributes traffic using equal-cost multipath routing. Increasing the maximum number of Service Engines only raises a limit; it does not itself scale active data-plane performance. Virtual Service priority affects placement decisions, not a direct scaling method.

In Avi analytics, Server RTT represents the round-trip latency between the Service Engine and the backend pool servers. VMware Avi documentation states that an abnormally high Server RTT can indicate a network issue between the Service Engine and the servers. Because Client RTT and App Response remain unchanged, the issue is most likely on the network path between the Service Engine and one or more pool servers.

An HTTPS client shows an untrusted certificate warning when the presented certificate cannot be validated by the client. Common causes include an expired certificate, a self-signed certificate, or a certificate signed by an internal certificate authority that the client does not trust. Avi documentation distinguishes between RSA and EC certificates as certificate algorithm types that can both be used by Virtual Services. A certificate being RSA instead of EC does not inherently make it untrusted. RSA certificates are still valid and supported when issued by a trusted CA, within their validity period, and matching the requested hostname. Therefore, the certificate algorithm alone is not a cause of an untrusted certificate error. The answer that would not cause the issue is B.

The Avi architecture separates control-plane and data-plane responsibilities. Service Engines perform data-plane tasks, including traffic processing, inserting persistence cookies, health checking pool members, and handling load-balanced connections. The Avi Controller provides centralized management, analytics, configuration, and operational visibility. Broadcom's Avi documentation explains that when an administrator requests to view Virtual Service or pool logs, the Controller pulls logs from Service Engines, indexes them, and displays the results. This makes log indexing a Controller function. By contrast, inserting cookies and checking backend server health occur in the Service Engine data plane. Active-active packet processing decisions are also handled by Service Engines according to the Virtual Service placement and traffic flow. Therefore, the task performed by the Avi Controller is indexing client logs.