AZ-120 · Question #87
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is A. Yes. Deploying an Azure Standard Load Balancer in front of a Network Virtual Appliance (NVA) is the Microsoft-recommended architecture for ensuring all traffic between an Azure subnet and an on-premises network is routed through the NVA firewall reliably. The Standard Load…
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an SAP production landscape on-premises and an SAP development landscape on Azure. You deploy a network virtual appliance to act as a firewall between the Azure subnet and the on- premises network. Solution: You deploy an Azure Standard Load balancer. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(54 responses)- A76% (41)
- B24% (13)
Explanation
Deploying an Azure Standard Load Balancer in front of a Network Virtual Appliance (NVA) is the Microsoft-recommended architecture for ensuring all traffic between an Azure subnet and an on-premises network is routed through the NVA firewall reliably. The Standard Load Balancer's HA (High Availability) ports feature - exclusive to the Standard SKU - allows it to load balance traffic across all ports and protocols simultaneously, which is required for an NVA acting as a firewall to inspect every packet. Without the Load Balancer, the NVA becomes a single point of failure, so the Standard LB also provides redundancy by distributing traffic across multiple NVA instances. A Basic Load Balancer would not meet this goal because it lacks HA ports and zone-redundancy support needed for production-grade NVA deployments.
Memory tip: Think "Standard = Security appliance support" - whenever you see an NVA firewall scenario in Azure, the Standard Load Balancer with HA ports is the glue that makes it production-ready.
Topics
Community Discussion
No community discussion yet for this question.