Free VMware 6V0-22.25 Practice Exam with Questions & Answers | Set: 2

Avi supports several persistence methods, and some require persistence tables stored in Service Engine memory. Client IP persistence uses a persistence table that maps client addresses to selected backend servers, which consumes Service Engine memory. TLS persistence also relies on state associated with TLS session behavior. App Cookie Persistence depends on application cookies and persistence handling that Avi must interpret or track. HTTP Cookie Persistence , however, is different because Avi can insert or use a cookie value that identifies the selected server, allowing the client to carry the persistence information in subsequent requests. This avoids maintaining the same kind of server-side persistence table in Service Engine memory. Therefore, the persistence type that does not consume Service Engine memory is HTTP Cookie Persistence .

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 .

The TCP Proxy Profile controls TCP behavior for a Virtual Service when Avi terminates the client TCP connection and opens a separate server-side TCP connection. VMware Avi documentation states that the TCP proxy terminates client connections, processes traffic, and then establishes a connection to the destination server. The Custom TCP Proxy Profile mode is used when administrators need to manually configure TCP proxy settings rather than use predefined system defaults. A valid reason to use this mode is to change TCP timeout behavior, including the idle duration timeout. Rate limiting is generally handled by policy or security controls, disabling SNAT is configured through network service or preserve-client-IP-related settings, and exposing destination port to the application is not the standard reason for selecting TCP Proxy Custom mode in this question.

Cookies are carried in HTTP headers, specifically the client request Cookie header and the server response Set-Cookie header. Avi application logs can show many useful request and response details, but not every header is captured in the standard visible log fields. Broadcom documentation for client log levels explains that full client logs include many data points and that All Headers logging can be enabled to capture HTTP headers. Broadcom’s logging-all-headers guidance also recommends using this feature carefully, preferably with log filters or temporary troubleshooting scope, because collecting all headers can increase log volume and may expose sensitive data. A client IP filter narrows log capture but does not by itself capture cookies. Real-time metrics and non-significant logs also do not specifically enable cookie/header capture.

Avi Load Balancer does not continuously forward and index every client transaction log by default. Broadcom documentation states that both significant and non-significant logs are not automatically forwarded by Service Engines to the Controller cluster for indexing by default. A newly created or newly enabled Virtual Service may show more log activity initially, but after the initial period, ordinary successful transactions are not shown unless non-significant logging or a user-defined client log filter is enabled. Significant logs, such as errors or policy-related events, continue to appear because they are operationally important. Therefore, if the Logs tab suddenly shows dramatically fewer entries after the first 30 minutes, the likely reason is that non-significant logs are not enabled .

The TCP Proxy Profile controls TCP behavior for a Virtual Service. Avi provides system TCP proxy profiles for common use cases, but Custom mode is used when an administrator needs to modify specific TCP proxy behavior beyond the default templates. In this question, the key valid use case is exposing the original client destination TCP port to the application. This is useful when the Virtual Service listens on multiple ports or when the backend application needs awareness of the client-facing destination port. Port Address Translation is handled through Virtual Service and pool port mappings, not as the main reason for TCP Proxy Custom mode. Default gateway configuration is a network routing function, and statically increasing the TCP receive window is not the best Avi-specific answer here. Therefore, the correct choice is D.

Avi HTTP compression behavior is influenced by network latency and compression policy settings. Broadcom’s Avi documentation explains that when round-trip time is less than 10 ms, no compression is applied; when RTT is between 10 ms and 200 ms, normal compression is used; and when RTT is above 200 ms, aggressive compression may be used. This is especially relevant in a lab environment, where client-to-Service-Engine latency is often extremely low. In that situation, compression can be correctly enabled, but Avi may choose not to compress responses because the RTT is below the threshold where compression is considered beneficial. Therefore, the most likely reason initial tests do not show compression is that the default behavior excludes traffic with RTT below 10 ms.

The Basic Virtual Service creation wizard is intended for common application deployment and exposes only the most frequently required settings. Broadcom’s Avi documentation describes a Virtual Service as the application endpoint with an IP address, service ports, application type, pools, and related configuration. In the Basic wizard, administrators can choose the Application Type , such as HTTP, HTTPS, or other common application categories, while more detailed profile, policy, analytics, and log-throttle configuration is reserved for Advanced Setup or later editing. TCP/UDP profiles, HTTP Request Policies, and significant log throttle settings are advanced configuration items and are not the typical Basic wizard inputs. Therefore, the option available in Basic Virtual Service creation is Application Type .

Avi supports HTTP-to-HTTPS redirection at the HTTP/application layer. This can be done using the secure HTTP application profile for common redirect behavior, an HTTP Request Policy for conditional redirect logic, or a DataScript for highly customized redirect handling. Broadcom documentation describes DataScripts as being able to perform redirection and header manipulation, while HTTP Policy Sets are used to define Layer 7 HTTP and HTTPS behavior. A Network Security Policy operates at a lower network-security layer and is used for actions such as accepting, denying, discarding, or rate-limiting connections. It does not operate as an HTTP redirect mechanism because it does not generate HTTP-layer 301 or 302 responses. Therefore, Network Security Policy cannot be used for HTTP-to-HTTPS redirection.