An LTM Specialist reviews a Virtual Server with the following configuration: ltm virtual /Common/https-virtual { destination /Common/10.10.10.25:https ip-protocol tcp mask 255.255.255.255 pool /Common/test-pool profiles { /Common/http { } /Common/tcp { } } source 0.0.0.0/0 source-address-translation { type automap } translate-address enabled translate-port enabled } ltm pool /Common/test-pool { members { /Common/10.10.10.19:80 { address 10.10.10.19 } /Common/10.10.10.20:80 { address 10.10.10.20 } /Common/10.10.10.21:80 { address 10.10.10.21 } } monitor /Common/https } tcpdump output 10:53:03.911234 IP 10.1.70.10.52144 > 10.10.1.20.http: Flags [S], seq 1054321789, win 65535, options [mss 1460,sackOK,TS val 123456789 ecr 0,nop,wscale 7], length 0 in slot1/tmm3 10:53:03.912001 IP 10.10.1.20.http > 10.1.70.10.52144: Flags [R], seq 0, ack 1054321790, win 0, length 0 out slot1/tmm3 10:53:04.001876 IP 10.1.70.10.52144 > 10.10.1.20.http: Flags [S], seq 1054321789, win 65535, options [mss 1460,sackOK,TS val 123456999 ecr 0,nop,wscale 7], length 0 in slot1/tmm3 10:53:04.002411 IP 10.10.1.20.http > 10.1.70.10.52144: Flags [R], seq 0, ack 1054321790, win 0, length 0 out slot1/tmm3 What is the root cause of the TCP resets? (Choose one answer)

• A. The Virtual Server is missing client and server SSL profiles
• B. SNAT Automap is NOT configured on the Virtual Server
• C. Pool members are NOT accepting connections on port 443
• D. The certificate installed on the pool members is invalid

Correct Answer: C

Brave-Dump Clients Votes