1Z0-1072-25 Question 139
Select 2You have deployed a public Load Balancer in Oracle Cloud Infrastructure to serve HTTPS traffic for a web application. The web application team requires that all SSL/TLS sessions be terminated on the load balancer, yet the backend servers still need to log the original client IP addresses. Which two configuration steps must you complete to meet these requirements?
- A
Configure an HTTPS listener on the Load Balancer and upload the SSL certificate.
- B
Enable the X-Forwarded-For header in the Load Balancer to pass the client� IP address.
- C
Use a Network Load Balancer with TCP pass-through to preserve the original client IP address.
- D
Implement a custom TCP health check on your backend servers to identify the client IP address directly.
Show answer and explanation
Correct answers: A, B
Explanation
When your application requires SSL termination at the Load Balancer and still needs the client� original IP address, you must configure an HTTPS listener with the appropriate SSL certificate and enable an X-Forwarded-For header. Oracle documentation (see 'Setting Up a Load Balancer for HTTPS Traffic' in Oracle Cloud Infrastructure docs) provides details on configuring an HTTPS listener and inserting the client's IP address into the request header.
- A. Correct.
Option 1: Correct. If you want the Load Balancer to terminate SSL/TLS, you must configure an HTTPS listener and upload the appropriate SSL certificate to the Load Balancer.
- B. Correct.
Option 2: Correct. To pass the original client IP address to the backend servers after SSL termination, you need to enable the X-Forwarded-For header. This ensures the application sees the client� IP.
- C. Incorrect.
Option 3: Incorrect. A Network Load Balancer can preserve the client IP by default, but it does not support SSL termination. The requirement explicitly states that SSL/TLS must terminate on the Load Balancer, hence a Network Load Balancer with pass-through mode would not meet that requirement.
- D. Incorrect.
Option 4: Incorrect. Custom TCP health checks do not address the need for SSL termination or passing the client IP address. Health checks are used to verify backend availability, not to handle client IP forwarding.