1Z0-1072-25 Question 136
Single answerYou are designing a microservices application on Oracle Cloud Infrastructure (OCI) using a single public Load Balancer front end. You need to ensure that all requests to the '/api' path are routed to one backend set of Compute instances running the API service, while requests to the '/images' path are directed to a different backend set. Which Load Balancer feature allows you to achieve this routing configuration?
- A
Weighted Round Robin scheduling
- B
Path route rules
- C
SSL pass-through
- D
IP-based routing configuration
Show answer and explanation
Correct answer: B
Explanation
Path route rules allow you to configure the Load Balancer to inspect incoming HTTP requests and route them to specific backend sets based on the requested path. This design is commonly used for microservices or applications that require separating traffic flows for different functional components. By defining specific path route rules for '/api' and '/images', you ensure requests are directed to the appropriate backend pool. Refer to Oracle� official documentation on OCI Load Balancer features and configuration for additional details and best practices.
- A. Incorrect.
Option 1: Weighted Round Robin scheduling distributes traffic based on assigned weights to each backend, but it does not examine the URL path. This is useful when you want certain backends to receive more traffic rather than routing requests based on different paths.
- B. Correct.
Option 2: Path route rules are designed to inspect the incoming request paths (like '/api' or '/images') and forward those requests to the corresponding backend sets. This directly addresses the requirement to route traffic by path.
- C. Incorrect.
Option 3: SSL pass-through involves passing encrypted traffic through the load balancer to the backends without decrypting it. While it helps maintain end-to-end encryption, it does not provide URL path-based routing capabilities by itself.
- D. Incorrect.
Option 4: IP-based routing configuration would route traffic based on the client's source IP address or IP ranges, not the requested URL path. This is incorrect for the specified scenario.