Your organization is deploying a critical database application on OCI. To ensure high availability, you have deployed the database instances across…

Requirements: Low-latency, minimal overhead for TCP connections, no session persistence.

Load Balancer Types:

Application Load Balancer (ALB): Layer 7, higher overhead, suited for HTTP/HTTPS.

Network Load Balancer (NLB): Layer 4, low overhead, ideal for TCP/UDP.

Evaluate Options:

A: ALB with HTTP checks is for HTTP traffic, adds overhead; unsuitable.

B: NLB with TCP checks is optimized for TCP, low latency; best fit.

C: ALB with TCP checks still has Layer 7 overhead; less efficient.

D: “Flexible Load Balancer” isn’t a specific OCI service; incorrect.

Conclusion: NLB minimizes latency and overhead for TCP connections.

The Network Load Balancer is designed for high-performance TCP scenarios. The Oracle Networking

Professional study guide states, "Network Load Balancer operates at Layer 4, providing low-latency,

high-throughput load balancing for TCP/UDP traffic with minimal overhead, ideal for database

connections" (OCI Networking Documentation, Section: Load Balancing). TCP health checks ensure

instance availability without session persistence complexity.

Reference: Oracle Cloud Infrastructure Documentation - Network Load Balancer.