Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam

Exam AZ-104 topic 5 question 50 discussion

Actual exam question from Microsoft's AZ-104

Question #: 50
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 create a Basic SKU public IP address, associate the address to the network interface of VM1, and then start VM1.
Does this meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️

by mdyck at May 3, 2021, 1:55 a.m.

Comments

Submit Cancel

mlantonis

Highly Voted 4 years ago

Correct Answer: B - No 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 86 times

mlantonis

4 years ago

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

upvoted 18 times

Pear7777

2 years, 5 months ago

The thing is this is a STANDARD, LB which can not work with BASIC ip's.

upvoted 4 times

GBAU

2 years, 3 months ago

I lab tested it, they can. Lab was with a Public LB though. It just didn't care the VM had a basic dynamic LIP and a basic dynamic PIP, I could still attach it to the backend pool, create a rule to LB a port and connect to it through the LB's PIP.

upvoted 1 times

...

Abubaker3030

2 years, 11 months ago

Basic SKU: If you are creating a public IP address in a region that supports availability zones, the Availability zone setting is set to None by default. Basic Public IPs do not support Availability zones. Standard SKU: A Standard SKU public IP can be associated to a virtual machine or a load balancer front end

upvoted 1 times

...

Holydud

2 years, 9 months ago

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

upvoted 8 times

...

klexams

2 years, 7 months ago

Also the LB is internal so no public IP.

upvoted 3 times

...

mdyck

Highly Voted 4 years ago

B. No Tested this and as you are creating the back end it says: "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." -It does not matter if the VM is stopped or started. -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. https://docs.microsoft.com/en-us/azure/load-balancer/backend-pool-management -When they dont have a public IP they are assigned an ephemeral IP. https://docs.microsoft.com/en-us/azure/load-balancer/quickstart-load-balancer-standard-internal-portal?tabs=option-1-create-internal-load-balancer-standard#create-virtual-machines

upvoted 26 times

...

[Removed]

Most Recent 8 months ago

Selected Answer: B

B is correct You create two Standard SKU public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine.

upvoted 1 times

[Removed]

6 months, 3 weeks ago

or You disassociate the public IP address from the network interface of VM2.

upvoted 1 times

...

tashakori

1 year, 2 months ago

No is right

upvoted 1 times

...

devops_devops

1 year, 4 months ago

This question was in exam 15/01/24

upvoted 2 times

...

oopspruu

1 year, 9 months ago

These questions that have you memorize or Cram the SKUs are the most pointless ones imo. I mean this info is just 1 google search away. But no, Azure Admins needs to know every single SKU by heart as per MS

upvoted 4 times

...

marioZuo

1 year, 10 months ago

IF VM has a basic IP, LB is a basic LB with basic IP. It can work as well.

upvoted 1 times

...

Eugene77

2 years ago

The question and discussions are not very clear. What is a problem with adding VM1 and VM2 by private IP addresses? Internal LB will work.

upvoted 1 times

...

Spam101198

2 years, 2 months ago

as LB is standard then IP should be standard only.

upvoted 1 times

...

zellck

2 years, 3 months ago

Selected Answer: B

B is the answer. https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#sku Matching SKUs are required for load balancer and public IP resources. You can't have a mixture of basic SKU resources and standard SKU resources.

upvoted 2 times

...

EmnCours

2 years, 9 months ago

Selected Answer: B

Correct Answer: B - No

upvoted 1 times

...

NotMeAnyWay

2 years, 10 months ago

Simply put you cannot mix the SKU type for a Load Balancer and a Public IP. Both in this case should be Standard SKUs: Read Here (Under the important section as the bottom of the SKU section): (https://docs.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#sku)

upvoted 2 times

...