The global eviction policy is triggered due to swap memory being used too high
The BIG-IP system starts reaping connections, all the connections will be dropped
The BIG-IP system starts reaping connections, some connections will be dropped
The global eviction policy is triggered due to TMM memory exhaustion
Question 2
Refer to the exhibit.A BIG-IP Administrator notices that one of the servers that runs an application is NOT receiving any traffic. The BIG-IP Administrator examines the configuration status of the application and observes the displayed monitor configuration and affected Pool Member status.What is the possible cause of this issue?
The Node Health Monitor is NOT responding.
HTTP 1.1 is NOT appropriate for monitoring purposes.
The BIG-IP device is NOT able to reach the Pool Member.
The application is NOT responding with the expected Receive String.
Question 3
A BIG-IP Administrator configured a virtual server with a pool of 3 members and selected the Round Robin load balancing method to evenly distribute traffic across the pool members. During initial testing, traffic was not evenly distributed and the pool member 172.16.20.3 received more traffic than the other pool members.Refer to the exhibit and the virtual server configuration provided below: ltm virtual http_vs { destination 10.10.1.100:http ip-protocol tcp mask 255.255.255.255 persist { source_addr { default yes}}pool http_poolprofiles {tcp{)}serverssl-use-sni disabledsource 0.0.0.0/0source-address-translation {type automap}translate-address enabledtranslate-port enabled}What is the most likely cause of this behavior?
A persistence profile assigned to the virtual server can cause uneven load balancing
Automap source address translation can cause uneven load balancing
Pool members' ratio settings are causing the uneven traffic distribution
Round Robin requires an HTTP profile to work efficiently
Question 4
During a maintenance window, an EUD test was executed and the output displayed on the screen. The BIG-IP Administrator did NOT save the screen output. The BIG-IP device is currently handling business critical traffic. The BIG-IP Administrator needs to minimize impact.What should the BIG-IP Administrator do to provide the EUD results to F5 Support?
Boot the device into EUD then collect output form console
Execute the EUD from tmsh and collect output from console
Collect file /var/log/messages
Collect file /shared/log/eud.log
Question 5
What information is required for a BIG-IP Administrator to open an F5 Support ticket?
Serial number of the device, ucs file, license file, log files
Serial number of the device, qkview, packet capture files, license file, ucs file
Serial number of the device, qkview, problem description, contact info
Serial number of the device, problem description, contact info
We are moving to a new platform
CertificationTest is being migrated. Some pages may be slow or briefly unavailable; everything will be back to normal within a few hours. If you run into any issue, email support@certificationtest.net.