All pool members are online. All other virtual server settings are at default.
What might alter the load balancing behavior? (Choose one answer)
By default, BIG-IP load balancing algorithms (such as Round Robin) distribute connections evenly across all available pool members. However, persistence profiles override normal load balancing decisions by forcing subsequent connections from a client to be sent to the same pool member.
According to the BIG-IP Administration: Data Plane Configuration documentation:
Persistence creates a client-to-server mapping that is honored before load balancing algorithms are applied.
When persistence is enabled, BIG-IP may repeatedly select the same pool member even if others are available.
This directly alters load balancing behavior.
Why the other options are incorrect:
A . Adding a OneConnect profile
OneConnect optimizes server-side TCP connections but does not change which pool member is selected.
B . Enabling SNAT automap
SNAT affects source address translation, not pool member selection.
C . Enabling a fallback host in the HTTP profile
A fallback host is only used when no pool members are available.
Correct Resolution:
Adding a persistence profile alters load balancing behavior by maintaining client affinity to a specific pool member.
A BIG-IP Administrator creates a new Virtual Server to load balance SSH traffic. Users are unable to log on to the servers.
What should the BIG-IP Administrator do to resolve the issue?
SSH is a TCP Layer 4 protocol. Applying an HTTP profile causes BIG-IP to expect HTTP headers, breaking SSH sessions. Removing the HTTP profile allows raw TCP forwarding.
A Standard Virtual Server reports poor network performance for Internet-based clients.
What configuration should be applied?
WAN TCP profiles are optimized for high latency and packet loss typical of Internet clients, while LAN profiles are ideal for backend servers.
Refer to the exhibit.

DNS queries from two internal DNS servers are being load-balanced to external DNS servers via a virtual server on a BIG-IP device. The DNS queries originate from:
192.168.10.100
192.168.10.200
and target:
192.168.2.150
All DNS queries destined for the external DNS servers fail.
Which property change should the BIG-IP Administrator make in the Virtual Server to resolve this issue? (Choose one answer)
DNS traffic is primarily transported using UDP port 53. In the exhibit, the Virtual Server is configured with the Protocol set to TCP, which prevents standard DNS queries from being processed correctly. BIG-IP Virtual Servers must be configured with the correct Layer 4 protocol to match the application traffic they are handling.
According to the BIG-IP Administration: Data Plane Configuration documentation:
The Protocol setting on a Virtual Server defines whether traffic is processed as TCP, UDP, or another supported transport protocol.
Standard DNS queries and responses use UDP, while TCP is only required for DNS zone transfers (AXFR) or exceptionally large responses.
When a DNS Virtual Server is incorrectly configured with TCP, UDP-based DNS queries are dropped, causing all requests to fail.
Why the other options are incorrect:
A . Protocol profile (Client) to DNS_OPTIMIZED
A DNS profile enhances DNS functionality but does not correct an incorrect transport protocol configuration.
B . Type to Performance (HTTP)
Performance (HTTP) Virtual Servers are designed for HTTP traffic and are not suitable for DNS services.
C . Source Address to 192.168.10.0/24
The existing source IPs already fall within the allowed range, so this setting does not address the failure.
Correct Resolution:
Changing the Protocol to UDP aligns the Virtual Server with standard DNS transport requirements, allowing DNS queries to be successfully processed and load-balanced.
Users are unable to reach an application. The Virtual Server shows a red diamond status.
What is the cause?
A red diamond indicates that the Virtual Server is enabled but unavailable, typically due to all pool members being down.
Margret
2 days agoMarisha
10 days agoCordelia
17 days agoMicaela
24 days agoLeandro
1 month agoCammy
1 month agoColeen
2 months agoCharisse
2 months agoClaudio
2 months agoDylan
2 months ago