Question 61 Discussion

Refer to the folllowing. New TCP connection #1: 172.24.130.52 (????) <-> 172.24.130.48 (80) GET / HTTP/1.1 Accept: application/xml, application/xhtml+xml, text/html;q=0.9, image/webp, */*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729) Connection: Keep-Alive HTTP/1.1 302 Found Content-Type: text/html <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>302 Found</title> </head> <body> <h1>Found</h1> <p>The document has moved <a href="https://www.example.com/">here</a>.</p> </body> </html> TCP FIN HTTP/1.1 302 Found Content-Type: text/html <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>302 Found</title> </head> <body> <h1>Found</h1> <p>The document has moved <a href="https://www.example.com/">here</a>.</p> </body> </html> TCP FIN An LTM Specialist has created HTTPS Virtual Server 172.24.130.152 which listens on Port 443. The application has one pool member 172.24.130.48, which listens on port 80. The user is NOT getting the right response and the LTM Specialist must determine the cause of the problem. The LTM Specialist has the ssldump extract shown. What is the root cause of the problem? (Choose one answer)

  • A. The response does NOT contain a Cache-Control header
  • B. The backend server is redirecting the traffic to HTTP
  • C. The backend server is redirecting the traffic to HTTPS
  • D. The client is sending an invalid request
Correct Answer: D

Brave-Dump Clients Votes

C 100%

Comments



Anonymous User 2026-03-04 19:45:41

Selected Answers: C


The correct answer is:
C. The backend server is redirecting the traffic to HTTPS.
Explanation
- The client initiates a connection to the pool member (172.24.130.48) on port 80 (HTTP).
- The server responds with HTTP 302 Found, which is a redirect.
- The redirect points to https://www.example.com/, meaning the backend server is instructing the client to switch to HTTPS.
- Since the LTM Specialist configured the Virtual Server to listen on port 443 (HTTPS) but the pool member only listens on port 80 (HTTP), the mismatch causes the client to not receive the expected response. The server itself is telling the client to use HTTPS, but the pool member isn’t serving HTTPS directly—it’s only serving HTTP.
Why not the other options?
- A. Cache-Control header missing → Irrelevant; caching doesn’t affect redirects.
- B. Redirecting to HTTP → Incorrect; the redirect clearly points to https://....
- D. Invalid request → The client request is valid; the issue lies in the server’s redirect.
This is a classic misconfiguration scenario: the backend server is enforcing HTTPS, but the load balancer is sending traffic to it over HTTP