| Exam Code/Number: | F5CAB5Join the discussion |
| Exam Name: | BIG-IP Administration Support and Troubleshooting |
| Certification: | F5 |
| Question Number: | 82 |
| Publish Date: | Sep 02, 2026 |
|
Rating
100%
|
|
Clients report that they cannot reach the virtual server vs-production on port 80, but are able to ping the virtual server address. The configuration is shown below:
Plaintext
ltm virtual vs-production {
destination 10.99.20.50:http
ip-protocol tcp
mask 255.255.255.255
profiles {
http {}
tcp {}
}
source 192.168.0.0/16
translate-address enabled
translate-port enabled
vlans {
external
}
vlans-enabled
}
What is the cause?
Which tool helps inspect SSL handshake issues?
A traffic group includes four devices. The failover method is HA order. The failover order is:
- BIGIP-D
- BIGIP-B
- BIGIP-C
- BIGIP-A
Auto fallback is enabled. BIGIP-D has been forced to standby. BIGIP-B was active before being rebooted. Which device is active when BIGIP-B is up after the reboot?
Pool /Common/testpool member /Common/10.120.0.5:8090 monitor status down.
[ /Common/http: up, /Common/http2: down; last error: ] [ was up for
lhr:0min:43sec ]
Why is this pool member being marked down?
Refer to the exhibit. A user with IP address 192.168.162.70 is unable to connect to an HTTP application. What is a possible cause within the Virtual Server configuration?