A BIG-IP Administrator suspects that one of the BIG-IP device power supplies is experiencing power outages. Which log file should the BIG-IP Administrator check to verify the suspicion?

• A./var/log/kern.log
• B./var/log/audit
• C./var/log/daemon.log
• D./var/log/ltm

Comment: *

Name: *

Email: *

Verification: *

Which two methods should the BIG-IP Administrator troubleshoot a Pool-member that's been marked "DOWN" by its Health Monitor? (Pick the 2 correct responses below)

• A.Enable Monitor Logging for the Pool-member that's "DOWN".
• B.Review the BIG-IP's routing table using "netstat -rn" to show all routes.
• C.Collect a TCPdump packet capture for the "DOWN" Pool-member.
• D.Review the Pool & Pool-member Statistics table for error data.

Comment: *

Name: *

Email: *

Verification: *

Exhibit:

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:
Plaintext
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.pool
profiles {
tcp{}
}
serverssl-use-sni disabled
source 0.0.0.0/0
source-address-translation {
type automap
}
translate-address enabled
}
What is the most likely cause of this behavior?

• A.Automap source address translation can cause uneven load balancing
• B.Pool members' ratio settings are causing the uneven traffic distribution
• C.Round Robin requires an HTTP profile to work efficiently
• D.A persistence profile assigned to the virtual server can cause uneven load balancing

Comment: *

Name: *

Email: *

Verification: *

A BIG-IP Administrator observes the following messages in the /var/log/ltm log:
warning tmm[pid]: 011e0002: sweeper_segment_cb_any: Aggressive mode
/Common/default- eviction-policy activated (0) (global memory)
(345209/690176 pages)
warning tmm[pid]: 011e0003: Aggressive mode sweeper /Common/default-
eviction-policy (0) (global memory) 1 connections killed
warning tmm[pid]: 011e0003: Aggressive mode sweeper /Common/default-
eviction-policy (0) (global memory) 1 connections killed
warning tmm[pid]: 011e0003: Aggressive mode sweeper /Common/default-
eviction-policy (0) (global memory) 1 connections killed
What is happening when the BIG-IP Administrator sees the messages displayed above? (Choose two answers)

• A.The global eviction policy is triggered due to TMM memory exhaustion
• B.The BIG-IP system starts reaping connections; all the connections will be dropped
• C.The BIG-IP system starts reaping connections; some connections will be dropped
• D.The global eviction policy is triggered due to swap memory being used too high

Comment: *

Name: *

Email: *

Verification: *

A BIG-IP Administrator creates a new Virtual Server. The end user is unable to access the page. During troubleshooting, the administrator learns that the connection between the BIG-IP system and server is NOT set up correctly. What should the administrator do to solve this issue?

• A.Disable Address Translation
• B.Set Address Translation to Auto Map, configure a SNAT pool, and have pool members in the same subnet of the servers
• C.Set Address Translation to SNAT and configure a specific translation address
• D.Set Address Translation to SNAT and have self-IP configured in the same subnet of servers

Comment: *

Name: *

Email: *

Verification: *