Q: 18
Your organization is deploying a critical database application on OCI. To ensure high availability, you
have deployed the database instances across multiple availability domains (ADs) within a single
region. You need to distribute client connections to the database instances and ensure that the load
balancer can handle long-lived TCP connections with minimal overhead. Session persistence is not
required. Which OCI load balancing solution would you choose in this scenario to minimize latency
and connection establishment overhead?
Options
Discussion
Call it it's B. Network Load Balancer is what Oracle recommends for raw TCP workloads, keeps latency and overhead low compared to ALB. Official docs and Oracle study guides usually make that distinction clear for database backends. If you want to double-check, I'd skim through the OCI Networking documentation and try a hands-on lab to see NLB in action.
For me, C is the way to go since Application Load Balancer can use TCP health checks and should handle TCP connections too. Plus, ALB gives more features if you need to tweak things later. Not totally sure though because NLB has lower overhead for TCP, but ALB feels like a safer default for app traffic. Agree?
Be respectful. No spam.
