AZ-700 Question 171
Single answerYou are deploying a three-tier web application in Azure. The front-end tier provides public-facing web pages to Internet users, while the middle and data tiers must remain private and only accept traffic from the front-end. You plan to use Azure Load Balancer for high availability. Which load balancing approach should you implement to meet these requirements?
- A
Use only a public load balancer to handle traffic for both front-end and backend tiers.
- B
Use only an internal load balancer to handle traffic for all tiers.
- C
Use a public load balancer for the front-end tier and an internal load balancer for the private tiers.
- D
Use separate public load balancers for the front-end tier and each private tier.
Show answer and explanation
Correct answer: C
Explanation
In Azure, public load balancers are used to distribute Internet-facing traffic to virtual machines in a front-end pool, while internal load balancers are used for private backend traffic within a virtual network. Azure documentation recommends using a public load balancer to route requests to a publicly accessible front-end and an internal load balancer for private tiers that require load balancing and isolation from external access. See Microsoft Learn documentation on 'What is Azure Load Balancer?' for more details.
- A. Incorrect.
Incorrect. While a public load balancer can expose the front-end to Internet users, it would also make your backend tiers publicly accessible, violating the requirement to keep them private.
- B. Incorrect.
Incorrect. An internal load balancer would keep all traffic private, but you wouldn�t have a publicly accessible endpoint for the front-end tier, so external users couldn�t reach the application.
- C. Correct.
Correct. A public load balancer provides external accessibility for the web front-end, while an internal load balancer ensures private communication and high availability for the backend tiers.
- D. Incorrect.
Incorrect. You don�t need multiple public load balancers for every tier. This would add unnecessary complexity and expose backend tiers that should remain private.