An organization plans to deploy a public Azure Load Balancer named LB1 to distribute HTTPS… — Microsoft Azure Administrator (AZ-104)

An organization plans to deploy a public Azure Load Balancer named $LB1$ to distribute HTTPS traffic across three virtual machines: $VM1$ , $VM2$ , and $VM3$ . The virtual machines are configured as follows:

* $VM1$ and $VM2$ are member instances of an Availability Set named $AS1$ .
* $VM3$ is a standalone virtual machine.
* $VM1$ has a public IP address named $IP1$ that uses the Basic SKU.

You plan to configure $LB1$ using the Standard SKU. Which two actions must you perform to ensure that all three virtual machines can be successfully configured in the backend pool of $LB1$ and receive load-balanced traffic?

Disassociate the Basic SKU public IP address from $VM1$ or upgrade it to a Standard SKU public IP address.Answer
Associate a Network Security Group (NSG) with the subnet of the virtual machines and create an inbound rule to allow the load-balanced traffic.Answer
C
Re-create $VM3$ within the same Availability Set as $VM1$ and $VM2$ .
D
Configure the frontend IP of the load balancer to use a dynamic Standard SKU public IP address.

Answer

The administrator must disassociate the Basic SKU public IP address from the virtual machine or upgrade it to a Standard SKU public IP address, and associate a Network Security Group (NSG) with the subnet of the virtual machines to allow inbound traffic.

To use a Standard Load Balancer, all public IP addresses on the network interfaces of VMs in the backend pool must also be of the Standard SKU, or be disassociated. In addition, Standard SKU resources are secure by default, meaning inbound flows are blocked unless explicitly allowed by a Network Security Group (NSG) associated with the subnet or network interface.

Step-by-Step Solution

Analyze backend pool requirements for Standard SKU Load Balancers.

Standard SKU load balancers allow a mix of standalone VMs and VMs in availability sets, meaning VM3 does not need to be re-created in the availability set.

To verify if VM3 needs to be modified to match the availability set configuration of VM1 and VM2.

Inspect public IP SKU compatibility on the backend network interfaces.

VM1 has a Basic SKU public IP. Standard Load Balancer backend pool members cannot have Basic SKU public IPs associated with their NICs.

To identify SKU mismatches on backend pool members that would block the deployment.

Remediate the SKU mismatch on the backend network interface.

Disassociate the Basic SKU IP from VM1 or upgrade it to Standard SKU.

To satisfy the SKU uniformity requirement of the Standard Load Balancer.

Determine the default security behavior of the Standard SKU Load Balancer.

Standard SKU resources are secure by default. Traffic is blocked without an explicit permit rule.

To ensure traffic can flow to the backend virtual machines once they are added to the pool.

Configure a Network Security Group (NSG) to allow inbound traffic.

Associate an NSG with the subnet and add an inbound security rule allowing the load-balanced traffic.

To permit inbound flow through the Standard Load Balancer to the backend VMs.

Key Concept

Standard SKU Load Balancer configuration requirements, backend pool SKU alignment, and secure-by-default architecture.

Estimated Time:3m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic