New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft AZ-104 Exam - Topic 4 Question 117 Discussion

Actual exam question for Microsoft's AZ-104 exam
Question #: 117
Topic #: 4
[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 a Standard SKU public IP address, associate the address to the network interface of VM1, and then stop VM2.

Does this meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: C

https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-overview

https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/tutorial-install-apps-template

https://docs.microsoft.com/en-us/samples/mspnp/samples/azure-well-architected-framework-sample-state-configuration

https://docs.microsoft.com/en-us/azure/architecture/framework/devops/automation-configuration


Contribute your Thoughts:

0/2000 characters
Juan
3 months ago
Standard SKU public IP is for public load balancers, not internal.
upvoted 0 times
...
Jennifer
3 months ago
Just stopping VM2 doesn't help with the backend pool.
upvoted 0 times
...
Marquetta
3 months ago
You can't add VMs to an internal load balancer with a public IP.
upvoted 0 times
...
Farrah
3 months ago
Wait, are we sure about that? Sounds off.
upvoted 0 times
...
Corinne
3 months ago
Totally agree, that won't work!
upvoted 0 times
...
Juan
4 months ago
I feel like I’ve seen this scenario before, and I think the answer is "No" because of the public IP requirement.
upvoted 0 times
...
William
4 months ago
I’m a bit confused about the need for a public IP with an internal load balancer. I thought it was unnecessary.
upvoted 0 times
...
Rex
4 months ago
I think I practiced a similar question where we had to ensure VMs were in the same virtual network. Not sure if stopping VM2 is relevant here.
upvoted 0 times
...
Carman
4 months ago
I remember that internal load balancers don't require public IPs, so this solution might not work.
upvoted 0 times
...
Elena
5 months ago
Okay, I think I see what's going on here. The goal is to add VM1 and VM2 to the backend pool of the internal load balancer. The proposed solution of adding a public IP to VM1 and stopping VM2 doesn't seem to address that directly. I'll need to think about how to properly configure the VMs and the load balancer to meet the requirements.
upvoted 0 times
...
Cassi
5 months ago
I think I've got a handle on this. The key is that the load balancer is internal, so the VMs need to be in the same virtual network. The proposed solution of adding a public IP to VM1 doesn't seem quite right. Let me review the requirements again and see if I can come up with a better approach.
upvoted 0 times
...
Rikki
5 months ago
I'm a bit confused by the part about the public IP address. Isn't this an internal load balancer? I'll need to make sure I understand how that fits into the solution.
upvoted 0 times
...
Rosalind
5 months ago
Okay, let me think this through step-by-step. The key seems to be ensuring that VM1 and VM2 can be added to the backend pool of the internal load balancer. I'll need to double-check the requirements and see if the proposed solution fully addresses that.
upvoted 0 times
...
Maile
5 months ago
Hmm, this seems like a tricky one. I'll need to carefully review the requirements and the proposed solution to make sure I understand everything correctly.
upvoted 0 times
...
Krissy
10 months ago
Stop VM2? What is this, a hostage situation? Let's just add both VMs and call it a day.
upvoted 0 times
...
Suzi
10 months ago
Ugh, these Azure questions can be so confusing sometimes. I'm just going to go with 'No' and hope for the best.
upvoted 0 times
...
Blythe
10 months ago
Haha, I bet the person who wrote this question was trying to trick us. 'Unique solution' my foot, this is clearly not the way to go about it.
upvoted 0 times
Argelia
8 months ago
Definitely not the way to achieve the goal.
upvoted 0 times
...
Dorathy
8 months ago
I agree, this solution doesn't seem right.
upvoted 0 times
...
Chau
9 months ago
B) No
upvoted 0 times
...
Ollie
9 months ago
A) Yes
upvoted 0 times
...
...
Nana
10 months ago
Hmm, I'm not sure creating a public IP address for an internal load balancer is the correct solution. Isn't that kind of defeating the purpose of an internal load balancer?
upvoted 0 times
Chanel
9 months ago
B) No
upvoted 0 times
...
Dulce
9 months ago
I agree, creating a public IP for an internal load balancer doesn't make sense.
upvoted 0 times
...
Ciara
9 months ago
B) No
upvoted 0 times
...
Isaac
10 months ago
A) Yes
upvoted 0 times
...
...
Benton
11 months ago
Wait, why do we need to stop VM2? That doesn't seem like the right approach. Shouldn't we just be able to add both VMs to the backend pool?
upvoted 0 times
Glenna
10 months ago
Agreed, we can simply add both VMs to the backend pool without the need to stop VM2.
upvoted 0 times
...
Aaron
10 months ago
Stopping VM2 is not necessary. We should be able to add both VMs to the backend pool without stopping any of them.
upvoted 0 times
...
...
An
11 months ago
I'm not sure. Let's think about it.
upvoted 0 times
...
Kathrine
11 months ago
But does associating the address to the network interface of VM1 and stopping VM2 really add both VMs to the backend pool of LB1?
upvoted 0 times
...
An
11 months ago
I think the solution is to create a Standard SKU public IP address.
upvoted 0 times
...

Save Cancel