AZ-104 Question 238
Single answerYou manage a multi-tier application in Azure. The front-end VMs should connect to a set of backend VMs that handle the application logic, and traffic between these tiers must remain private (not exposed to the public Internet). You need to evenly distribute traffic across these backend VMs and minimize overhead. Which configuration should you use for your Azure Load Balancer?
- A
Configure a public Load Balancer with a public front-end IP address
- B
Configure an internal Load Balancer with a private front-end IP address in the backend subnet
- C
Use DNS round-robin to cycle traffic among the backend VMs
- D
Configure an Application Gateway with a WAF tier to protect the backend
Show answer and explanation
Correct answer: B
Explanation
An internal Load Balancer with a private front-end IP provides load balancing exclusively within your virtual network. This meets the requirement of keeping backend traffic private and ensures traffic distribution among the backend VMs.
- A. Incorrect.
Public Load Balancer exposes your service to the internet, which does not meet the internal traffic requirement.
- B. Correct.
Internal Load Balancer with a private front-end IP keeps traffic within the virtual network and balances requests across backend VMs.
- C. Incorrect.
DNS round-robin lacks built-in health probes and doesn’t dynamically manage traffic if a VM goes down.
- D. Incorrect.
Application Gateway with WAF is primarily designed for web scenarios and external traffic; it’s not necessary if your requirement is strictly internal load balancing.