Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam

Exam AZ-104 topic 5 question 62 discussion

Actual exam question from Microsoft's AZ-104

Question #: 62
Topic #: 5

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 Azure subscription that contains the virtual machines shown in the following table.

You deploy a load balancer that has the following configurations:
✑ Name: LB1
✑ Type: Internal
✑ SKU: Standard
✑ Virtual network: VNET1
You need to ensure that you can add VM1 and VM2 to the backend pool of LB1.
Solution: You disassociate the public IP address from the network interface of VM2.
Does this meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: A 🗳️

by sandysy2002 at May 1, 2021, 1:52 p.m.

Comments

Submit Cancel

mlantonis

Highly Voted 4 years, 2 months ago

Correct Answer: A - Yes You can only attach virtual machines that are in the same location and on the same virtual network as the LB. Virtual machines must have a standard SKU public IP or no public IP. The LB needs to be a standard SKU to accept individual VMs outside an availability set or vmss. VMs do not need to have public IPs but if they do have them they have to be standard SKU. Vms can only be from a single network. When they don’t have a public IP they are assigned an ephemeral IP. Also, when adding them to a backend pool, it doesn’t matter in which status are the VMs. Note: Load balancer and the public IP address SKU must match when you use them with public IP addresses.

upvoted 102 times

mlantonis

4 years, 2 months ago

It's valid, because: LB1: Standard SKU VM1: No public IP VM2: No public IP

upvoted 36 times

KelvinTan

3 years, 11 months ago

disassociate the public IP address from the network interface of VM2

upvoted 2 times

...

kennynelcon

3 years, 3 months ago

Mlantonis oil dey your head

upvoted 3 times

haazybanj

3 years, 1 month ago

Baba werey. Dis one no be Naija o.Answer is right

upvoted 3 times

Tholudee

2 months, 2 weeks ago

naija boys

upvoted 1 times

...

Load full discussion...

...

andrew_ura

2 years, 8 months ago

Public IP of the VM is basic SKU, not standad. And if "The LB needs to be a standard SKU to accept individual VMs outside an availability set or vmss. VMs do not need to have public IPs but if they do have them they have to be standard SKU. ", then it will fail!? B - No is correct

upvoted 1 times

curtmcgirt

2 years, 5 months ago

-we're _removing_ the public IP from vm2, so it doesn't matter anymore if the public IP sku is basic or standard. -the lb _IS_ a standard SKU, so it can accept these individual VMs that have no public IPs.

upvoted 3 times

...

Moyuihftg

Highly Voted 4 years, 3 months ago

You can only attach virtual machines that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network. ALso, VMs do not have to be powered on when adding them to a backend pool. So answer should be A (Yes)

upvoted 91 times

Takloy

3 years, 7 months ago

That's what I thought!

upvoted 4 times

...

Holydud

2 years, 11 months ago

Was on exam 19 Aug 2022. Scored 870. Around 85% questions were also on ET. Answered A

upvoted 9 times

...

GenjamBhai

3 years, 1 month ago

2 possible ways - either no Public IPs on BE VMs or Std Public IPs on both VMs matching Std LB SKU

upvoted 9 times

GBAU

2 years, 5 months ago

Tested in a Lab Feb '23. Standard SKU LB had ZERO problems using VMs with basic PIPs and LIPs in the backend pool.

upvoted 4 times

josola

1 year, 8 months ago

That's cloud something that wasn't possible now it is. So "A" was probably right long ago, but not anymore.

upvoted 1 times

...

MasterMans

Most Recent 3 weeks ago

Selected Answer: B

VM1-not in running state

upvoted 1 times

...

Kabilanis

1 month ago

Selected Answer: A

Below are the possible options for this scenario. Consolidating here for easy read of subscribers. Solution: You create a Basic SKU public IP address, associate the address to the network interface of VM1, and then start VM1. - No Solution: You create a Standard SKU public IP address, associate the address to the network interface of VM1, and then stop VM2. - No Solution: You create two Standard SKU public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine. - Yes Solution: You disassociate the public IP address from the network interface of VM2. - Yes

upvoted 1 times

...

Josh219

11 months, 3 weeks ago

B: NO Disassociating the public IP address from the network interface of VM2 is not necessary to add VM1 and VM2 to the backend pool of an internal load balancer. Instead, you need to ensure that both VMs are in the same virtual network (VNET1) and subnet as the load balancer

upvoted 1 times

...

tashakori

1 year, 4 months ago

Yes is correct

upvoted 1 times

...

fastlearner21

2 years, 3 months ago

Can someone explain why ET has answer B. How is this answer selected on ET platform?

upvoted 3 times

...

JayLearn2022

2 years, 5 months ago

There are several versions of this question. The following are the correct and incorrect answers that can be presented. Correct Answer: Meets the goal. -Solution: You create two Standard SKU public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine. Incorrect Answers: Does not meet the goal. -Solution: You disassociate the public IP address from the network interface of VM2. -Solution: You create a Basic SKU public IP address, associate the address to the network interface of VM1, and then start VM1. -Solution: You create a Standard SKU public IP address, associate the address to the network interface of VM1, and then stop VM2.

upvoted 4 times

garmatey

2 years, 1 month ago

why post all this on multiple different questions and not make sure its correct...

upvoted 1 times

...

obaali1990

2 years, 4 months ago

Your provided guidelines for option 2 is not valid

upvoted 1 times

...

meeko86

2 years, 7 months ago

Selected Answer: A

For this series question, there are two possible answers: 1. You create two Standard public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine. 2. You disassociate the public IP address from the network interface of VM2.

upvoted 5 times

...

EmnCours

2 years, 11 months ago

Selected Answer: A

Correct Answer: A You can only attach virtual machines that are in the same location and on the same virtual network as the LB. Virtual machines must have a standard SKU public IP or no public IP.

upvoted 1 times

...

Gino_Slim

3 years, 1 month ago

Selected Answer: A

It's A....they need to update this.

upvoted 1 times

...

Pramodswagh

3 years, 1 month ago

Selected Answer: A

Need is to have either standard sku public ip or no public ip so answer is yes.

upvoted 1 times

...

Lazylinux

3 years, 1 month ago

Selected Answer: A

A for sure As the Basic Public IP SKU had been removed and the LB is STD which means can support singles VMs to be added and dont need be in AV set or VM scale set and all are in same region

upvoted 2 times

...

cloudera

3 years, 1 month ago

Selected Answer: A

VM1 has no public IP, VM2 has public IP. To add VM1 and VM2 as LB back-end pools - you can either remove the public IP of VM2 or assign standard SKU public IP to both the VMs.

upvoted 1 times

...