Exam AZ-303 All Questions

View all questions & answers for the AZ-303 exam

Exam AZ-303 topic 5 question 72 discussion

Actual exam question from Microsoft's AZ-303

Question #: 72
Topic #: 5

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 Kraviecc at Jan. 16, 2021, 10:10 a.m.

Comments

Submit Cancel

DNeo

Highly Voted 4 years, 4 months ago

Load balancer supports both inbound and outbound scenarios. Assuming we use public load balancer here, inbound NAT will work and make this answer "YES". https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview#:~:text=A%20public%20load%20balancer%20can,internet%20traffic%20to%20your%20VMs.

upvoted 21 times

pentium75

4 years ago

But the monitoring solution must access EACH individual VM. Not 'any of the VMs' by the Load Balancer's random choice.

upvoted 2 times

Pinto

4 years ago

Let's entertain the fact that the monitoring solution (no mention of what it is) is there to only check the app logs and report on those and is not a critical app. The logs are written locally. The monitoring solution will connect to the LB IP every 1 second and it will be pointed to a specific VM. The monitoring solution picks the log entries after the last one it had read in earlier attempt. Round robin will ensure that every server gets connected unless it is down. If only the questions were not trying to test our imagination and guessing skills as well.

upvoted 2 times

medi01

3 years, 11 months ago

Besides, can't monitoring solution use different ports + NAT for accessing different VMs?

upvoted 1 times

...

altafpatel1984

3 years, 5 months ago

Answer is A as per followinig: https://docs.microsoft.com/en-gb/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine

upvoted 1 times

...

nfett

Highly Voted 4 years, 1 month ago

this copied from another az-300 thread. 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 8 times

...

AberdeenAngus

Most Recent 3 years, 6 months ago

I'm going for No. I haven't tested it but I think 2 problems with the inbound NAT rule idea are: - the VM seems to have to exist to define the NAT rule in the LB, and with a scale set any VM might be deleted/created any time - I doubt if there are many monitoring tools out there which can be configured to use adhoc ports to connect to VMs which they're monitoring, I've never heard of one.

upvoted 1 times

...

syu31svc

3 years, 11 months ago

https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking 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 (also known as a jumpbox), which then routes incoming connections to scale set virtual machines as needed (for example, through inbound NAT rules). I would say Yes

upvoted 2 times

...

tteesstt

3 years, 11 months ago

You can define Inbound NAT rules/port forwarding on Azure Load Balancer. This enables access to each individual vm like this: xxx.yyy.zzz.www:50001 - vm1 xxx.yyy.zzz.www:50002 - vm2 xxx.yyy.zzz.www:50003 - vm3 ....

upvoted 2 times

...

anupam77

4 years, 1 month ago

Ans is A - Yes. See Link [Section : Public IPv4 per virtual machine] https://docs.microsoft.com/en-gb/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#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 (also known as a jumpbox), which then routes incoming connections to scale set virtual machines as needed (for example, through inbound NAT rules).

upvoted 2 times

...

paulot

4 years, 3 months ago

Lots of IF here. However a public LB should enable access.

upvoted 2 times

...

snoopinator

4 years, 3 months ago

If that monitoring solution need to access all the VMs as stated then a public LB won't work. It will give you access potentially to one at a time. I'd say NO.

upvoted 5 times

...