ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam
Go to Exam

Exam AZ-104 topic 5 question 52 discussion

Actual exam question from Microsoft's AZ-104
Question #: 52
Topic #: 5
[All AZ-104 Questions]

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 create two Standard SKU public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine.
Does this meet the goal?

  • A. Yes
  • B. No
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by Moyuihftg at May 1, 2021, 10:09 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
mlantonis
Highly Voted 3 years, 11 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 75 times
djhyfdgjk
1 year, 2 months ago
You must be kidding. This is INTERNAL LB.
upvoted 3 times
...
Acai
3 years, 9 months ago
One of the few slip-ups from Azure Jesus. The provided answer is correct, the reasoning is correct but missed that VM1 has a basic SKU.
upvoted 3 times
Acai
3 years, 9 months ago
Nope AJ is correct, thought it was the other question.
upvoted 3 times
...
...
stdevops
3 years, 6 months ago
you need to start VM also
upvoted 3 times
xRiot007
1 year, 11 months ago
No, the VM can remain stopped.
upvoted 1 times
...
...
mlantonis
3 years, 11 months ago
It's valid, because: LB1: Standard SKU VM1: Standard SKU public IP VM2: Standard SKU public IP
upvoted 17 times
...
Load full discussion...
...
Moyuihftg
Highly Voted 4 years ago
Answer correct. You can only attach virtual machines that are in the same location and on the same virtual network as the loadbalancer. Virtual machines must have a standard SKU public IP or no public IP.
upvoted 12 times
...
cris_exam
Most Recent 1 month, 2 weeks ago
Selected Answer: A
so, I agree with the Azure god here <mlantonis>, answer is YES - but only after I tested this myself. So... found out: - for a VM to be added to a backend of a internal LB, it has to be within the network "reach" of where you decide to place the iLB. For example within the same VNET/subnet or if you have multiple VNETs, they need to be peered or communicating. - If the VM has a Basic pip (public ip) it won't work even if the VM is in the network reach. - it doesn't matter if the VM is ON or OFF, they can still be added to the backend. - you can add VMs to the iLB backend if both VMs are pip-less and/or they have STANDARD pips, but if you have basic pip, it will not even show you the VMs to be able to select and add. Azure does not allow mixing Basic SKU and Standard SKU load balancer or public IP resources within the same availability set or virtual network.
upvoted 1 times
...
ElMordini
2 months, 3 weeks ago
Selected Answer: B
It's an internal LB what are you supposed to do with the public ips?
upvoted 2 times
...
Sicaben
5 months, 2 weeks ago
Hello! VM1 is de-allocated...anyone! help!!!
upvoted 2 times
...
[Removed]
7 months, 1 week ago
Selected Answer: A
A is correct
upvoted 1 times
...
tashakori
1 year, 1 month ago
Yes is right
upvoted 1 times
...
sardonique
1 year, 7 months ago
I don't understand, it is an internal load balancer, you place your VM behind an internal Load balancer when you do not want to expose them, what is the need of public ip in the first place? some questions are really weird
upvoted 7 times
alsmk2
8 months, 3 weeks ago
Microsoft logic - it's not whether you should be doing it, but can you be doing it. I agree though - I can't see a scenario where I'd want to internally LB a service, but also have each one publicly accessible individually at the same time.
upvoted 2 times
...
...
AntaninaD
1 year, 7 months ago
Got this question on 09/09/23
upvoted 2 times
...
HALLYdre
1 year, 10 months ago
I think the answer should be no. The load balancer is an internal load balancer and nothing to do with SKU of a public ip is relevant in making the VMs to work.
upvoted 6 times
...
ojogbon
2 years, 1 month ago
On the exam Apr 2nd, 2023
upvoted 1 times
...
JayLearn2022
2 years, 2 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 9 times
EzBL
1 year, 3 months ago
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 I a valid answ er if You disassociate the public IP address from the network interface of VM2
upvoted 2 times
...
...
meeko86
2 years, 4 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 2 times
...
kusucu
2 years, 6 months ago
Selected Answer: A
mlatonis is right
upvoted 2 times
...
EmnCours
2 years, 8 months ago
Selected Answer: A
Answer correct. You can only attach virtual machines that are in the same location and on the same virtual network as the loadbalancer. Virtual machines must have a standard SKU public IP or no public IP.
upvoted 1 times
...
DragonDagger
2 years, 8 months ago
Selected Answer: A
A is correct
upvoted 1 times
...
benvdw
3 years, 1 month ago
A- on exam 13/3/2022 (the one above as well)
upvoted 3 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago