AZ-700 Question 170
Single answerYou are designing a production-scale application hosted in Azure that must serve incoming internet traffic to a single Azure region for regulatory compliance. The solution requires zone redundancy, advanced metrics in Azure Monitor, and support for both inbound and outbound traffic rules. Which Azure Load Balancer SKU and tier should you deploy to meet these requirements?
- A
Basic SKU, Public Load Balancer
- B
Standard SKU, Global Load Balancer
- C
Basic SKU, Internal Load Balancer
- D
Standard SKU, Public Load Balancer
Show answer and explanation
Correct answer: D
Explanation
The Standard SKU, Public Load Balancer is recommended for production environments where you need zone redundancy, advanced logging and metrics, and thorough control over inbound and outbound traffic. Basic SKU load balancers lack these capabilities, and a Global Load Balancer would violate the requirement to keep traffic in a single region. For more details, refer to the Microsoft documentation on Azure Load Balancer SKUs (https://docs.microsoft.com/azure/load-balancer/skus).
- A. Incorrect.
Option 1: Basic SKU, Public Load Balancer � Incorrect. The Basic SKU lacks some advanced features such as zone redundancy and detailed metrics. It� not recommended for production workloads requiring high availability and advanced monitoring.
- B. Incorrect.
Option 2: Standard SKU, Global Load Balancer � Incorrect. While the Standard SKU offers advanced features, the Global Load Balancer spans multiple regions, which goes against the requirement to keep all traffic within a single Azure region for compliance.
- C. Incorrect.
Option 3: Basic SKU, Internal Load Balancer � Incorrect. Although an internal load balancer can be used for workloads within a virtual network, it does not support direct inbound internet traffic. Also, the Basic SKU still lacks the advanced capabilities required.
- D. Correct.
Option 4: Standard SKU, Public Load Balancer � Correct. This selection supports advanced monitoring, zone redundancy, inbound and outbound rules, and is suitable for production workloads. It also ensures that traffic is contained within a single Azure region to meet regulatory requirements, making it the ideal choice.