You plan to deploy a public Standard Load Balancer named LB1. LB1 will have a backend pool… — Microsoft Azure Administrator (AZ-104)

You plan to deploy a public Standard Load Balancer named $LB1$ . $LB1$ will have a backend pool named $Pool1$ . You have a virtual network named $VNet1$ that contains a subnet named $Subnet1$ . $Subnet1$ contains three virtual machines:

- $VM1$ : Configured with a Basic SKU public IP address directly assigned to its network interface ( $NIC1$ ).
- $VM2$ : Configured with a Standard SKU public IP address directly assigned to its network interface ( $NIC2$ ).
- $VM3$ : Configured with no public IP address.

Currently, no Network Security Groups (NSGs) are associated with $Subnet1$ or any of the virtual machine network interfaces. Which of the following sets of actions must you perform to successfully add all three virtual machines to $Pool1$ and ensure that health probes succeed?

Associate a network security group (NSG) to $Subnet1$ with an inbound rule allowing the `AzureLoadBalancer` service tag, and either upgrade the public IP of $VM1$ to Standard SKU or dissociate it from $NIC1$ .Cevap
B
Associate a network security group (NSG) to $Subnet1$ with an inbound rule allowing the `AzureLoadBalancer` service tag, and change the public IP of $VM2$ to a Basic SKU public IP.
C
Remove $VM1$ from $Pool1$ and configure a network security group (NSG) on $Subnet1$ with an inbound rule allowing the `Internet` service tag.
D
Dissociate the public IP address from $VM2$ , and create an inbound network security group (NSG) rule allowing the `AzureLoadBalancer` service tag on $NIC1$ only.

Cevap

Associate a network security group (NSG) to Subnet1 with an inbound rule allowing the AzureLoadBalancer service tag, and either upgrade the public IP of VM1 to Standard SKU or dissociate it from NIC1.

The correct action resolves the SKU compatibility issue on VM1 while satisfying the security requirements of the Standard Load Balancer. Since Standard Load Balancers only support Standard SKU public IPs or interfaces with no public IPs in their backend pool, VM1's Basic public IP must be upgraded or dissociated. Furthermore, Standard Load Balancers are secure by default, so health probes will fail unless an NSG is associated with the subnet (or NICs) and contains an inbound rule allowing traffic from the AzureLoadBalancer service tag.

Adım Adım Çözüm

Analyze the SKU compatibility requirements for the Standard Load Balancer backend pool.

Standard Load Balancers require all backend network interfaces to either have no public IP or have a Standard SKU public IP. VM1's Basic SKU public IP is incompatible.

To identify why VM1 cannot be added directly to the backend pool.

Select the resolution for VM1's IP address SKU mismatch.

The public IP of VM1 must be upgraded to Standard SKU or dissociated from NIC1. VM2 and VM3 do not require changes.

To align VM1's configuration with the Standard Load Balancer requirements.

Analyze health probe behavior and default security settings of Standard Load Balancers.

Standard Load Balancers are secure by default, meaning all inbound traffic to backend instances (including health probes) is blocked without an NSG.

To determine why health probes would fail by default.

Define the security rule requirement to allow health probes.

Associate an NSG to Subnet1 and configure an inbound security rule allowing traffic from the AzureLoadBalancer service tag.

To permit the load balancer health probe traffic to reach all backend VMs.

Anahtar Kavram

Azure Standard Load Balancer SKU compatibility and default security behaviors.

Tahmini Süre:3m 0s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru