Exam AZ-300 All Questions

View all questions & answers for the AZ-300 exam

Exam AZ-300 topic 1 question 73 discussion

Actual exam question from Microsoft's AZ-300

Question #: 73
Topic #: 1

Note: This question is part of 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 are planning to create a virtual network that has a scale set that contains six virtual machines (VMs).
A monitoring solution on a different network will need access to the VMs inside the scale set.
You need to define public access to the VMs.
Solution: Implement an Azure Load Balancer.
Does the solution meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️

by Santosh_Nalikul at Nov. 30, 2019, 12:26 p.m.

Comments

Submit Cancel

praiser

Highly Voted 5 years, 6 months ago

A Load Balancer would not make sense - the monitoring solution will need access to all the VM's inside the Scale Set, and not to one by one in a round-robin mode. Answer B should be correct.

upvoted 29 times

...

pokerpa71

Highly Voted 5 years, 4 months ago

The correct answer is "A" - https://docs.microsoft.com/en-gb/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-IPv4-per-virtual-machine - : "Public IPv4 per virtual machine" In general, Azure scale set virtual machines do not require their own public IP addresses. For most scenarios, it is more economical and secure to associate a public IP address to a load balancer or to an individual virtual machine (aka a jumpbox), which then routes incoming connections to scale set virtual machines as needed (for example, through inbound NAT rules).

upvoted 12 times

...

cloudcuckooland

Most Recent 4 years, 9 months ago

horrible question. you could add nat rules for each of vms, if the vms remain at 6 and don't scale horizontally.if this comes up in the exam I would flag it as extremely poorly written. the fact is, LB could be used with NAT rules to allow access to each vm, but it's a completely ridiculous solution., but does it meet the goal, yes it does, so answer in theory is YES. see https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-windows-nat

upvoted 1 times

...

arseyam

4 years, 10 months ago

The answer should be A When you select add load balancer to the VMSS, by default the load balancer will create NAT rules for RDP or SSH for each instance in the VMSS on a different port.

upvoted 1 times

...

exams0123456

4 years, 10 months ago

Correct answer: B Load balance indeed removes the necessity of assigning public IP, but the requirement here is that the monitoring agent requires ACCESS to the VMs. This is not a purpose of a load balancer. A load balancer is only used to balance/distribute SERVICE REQUEST to underlying VMs. Its not/never used for ACCESS PROVISIONING which is the requirement here. Hence correct answer is B

upvoted 1 times

admins

4 years, 9 months ago

But you can add NAT rules to a load balancer and then get access to each VM on a different port. The answer is A: Yes.

upvoted 2 times

...

viplov

4 years, 10 months ago

Correct Answer B, After the scale set has been created, the backend port cannot be modified for a load balancing rule used by a health probe of the load balancer. To change the port, you can remove the health probe by updating the Azure virtual machine scale set, update the port and then configure the health probe again.

upvoted 2 times

...

dumbu

5 years ago

Correct Answer is A. When you create a load balancer you can assign load balancer and the loadbalancer has NAT rules to connect to VM. After you create old balancer go to VMss instances and choose to connect in the dropdown select loadbalancer IP and they you can connect.

upvoted 2 times

X_L

4 years, 11 months ago

Exactly, you can target a specific VMSS member by mapping a port of your choice to its Private IP & RDP port

upvoted 1 times

...

dg63

5 years, 2 months ago

B is correct answer. You need deterministic access to individual VMs in the scaleset (e.g. you want to access vm1 out of 6 VMs). A loab balancer, even with the sticky session on, will take you to some VM based on routing rules which may not be the VM that you want to access. So load balancer is not a good solution.

upvoted 8 times

TYT

5 years, 2 months ago

Exactly. You need to be able to access a specific VM in the scale set for monitoring.

upvoted 2 times

...

praveen97

4 years, 10 months ago

Agree with dg63.

upvoted 1 times

...

BiggusJiggus

4 years, 10 months ago

dg63 has the correct answer

upvoted 1 times

...

Happiman

5 years, 3 months ago

There are four solutions, three of them are Deploy a standalone VM that has a public IP address to the virtual network. Implement an Azure Load Balancer. Design a scale set to automatically assign public IP addresses to all VMs. https://subscription.packtpub.com/book/virtualization_and_cloud/9781788991735/1/ch01lvl1sec17/vm-scale-sets

upvoted 5 times

...

AnilV

5 years, 3 months ago

Answer is A https://azure.microsoft.com/en-in/blog/virtual-machine-scale-set-insights-from-azure-monitor/

upvoted 2 times

...

[Removed]

5 years, 4 months ago

The correct answer is B A scale set is created inside a virtual network, and individual VMs in the scale set are not allocated public IP addresses by default. This policy avoids the expense and management overhead of allocating separate public IP addresses to all the nodes in your compute grid. If you do need direct external connections to scale set VMs, you can configure a scale set to automatically assign public IP addresses to new VMs. https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-overview

upvoted 3 times

...

wlfjck

5 years, 5 months ago

it should be A, as load balancer + VMSS, you can configure inbound NAT rules for each VM inside of VMSS

upvoted 9 times

poohtt

4 years, 10 months ago

No, B is correct. Who will modify NAT rules for new/deleted machines every time the VMSS scales out/in?

upvoted 2 times

admins

4 years, 9 months ago

it doesnt say anything in the question about the scale set actually scaling. It does say that there are 6 VMs though. Thats a pretty specific number and we can read that to mean it has 6 vms intentionally (and therefore won't be changing often). Scale sets aren't always used for their automatic scaling ability, sometimes they're used because the server is stateless and we just want duplicate copies of the same image.

upvoted 1 times

...

maheshyadav

5 years, 6 months ago

B is right since a Load Balancer is created when creating VMSS. If it was Application Gateway instead of LB

upvoted 1 times

...

Santosh_Nalikul

5 years, 6 months ago

Why A is not correct ?

upvoted 1 times

JakeCallham

5 years, 6 months ago

A is indeed a valid answer, the questions is, is this the most optimal way? https://subscription.packtpub.com/book/virtualization_and_cloud/9781788991735/1/ch01lvl1sec17/vm-scale-sets

upvoted 1 times

admins

4 years, 9 months ago

Where in the question does it say "what is the most optimal way?", it doesnt. It does however say "Some question sets may have more than one correct solution". So we can choose more than one answer to be correct. This would be one of them. We can use NAT rules to connect to the VMs in the scale set.

upvoted 1 times

tartar

4 years, 9 months ago

A is ok

upvoted 1 times

...