AZ-303 Exam QuestionsBrowse all questions from this exam

AZ-303 Exam - Question 228


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: Design a scale set to automatically assign public IP addresses to all VMs.

Does the solution meet the goal?

Show Answer
Correct Answer: A

Designing a scale set to automatically assign public IP addresses to all VMs will indeed provide public access to the VMs. This solution ensures that each virtual machine in the scale set has an individual public IP address, thus meeting the requirement of providing public access for monitoring purposes.

Discussion

12 comments
Sign in to comment
AmitRoy
Jan 26, 2021

A. It'll meet the goal. However, it's not a good practice.

nExoR
Apr 19, 2021

seems to me as a 'part of solution' and not 'solution that meets the goal'...

Hermin
Dec 30, 2021

I think it is A (Yes) How can I configure a scale set to assign a public IP address to each VM? To create a virtual machine scale set that assigns a public IP address to each VM, make sure the API version of the Microsoft.Compute/virtualMachineScaleSets resource is 2017-03-30, and add a publicipaddressconfiguration JSON packet to the scale set ipConfigurations section. https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-faq

Stevezzc
Jan 8, 2021

not sure about the answer, but assigning PIP to each VM within a VMSS is fesible. https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#creating-a-scale-set-with-public-ip-per-virtual-machine

souvik123
Jul 10, 2021

Yes, it will meet the goal

tteesstt
Aug 31, 2021

When you create VMSS you can click on a checkbox to assign each one of them a public IP address.

AD3
Feb 21, 2022

B is still valid. The VMs in scale set come and go with the public IPs assigned dynamically. It's not possible to discover or difficult to discover such VMs. The best way is to have a VM with the public IP which will do the job of this discovery and keeping track of the VMs in the scale set. I think the goal can be met with the single VM with the public IP only.

xaccan
Jan 15, 2021

A is the correct

VALEARN
Jan 21, 2021

A is Correct: https://azure.microsoft.com/en-us/blog/new-networking-features-in-azure-scale-sets/ Read the section: Public IPv4 addresses per VM

crazyaboutazure
Jul 10, 2021

This solution can be done via individual VM, Load Balancer or VM scaleset. 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). However, some scenarios do require scale set virtual machines to have their own public IP addresses. An example is gaming, where a console needs to make a direct connection to a cloud virtual machine, which is doing game physics processing. Another example is where virtual machines need to make external connections to one another across regions in a distributed database. https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking

syu31svc
Aug 29, 2021

https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine To create a scale set that assigns a public IP address to each virtual machine with the CLI, add the --public-ip-per-vm parameter to the vmss create command. Answer is Yes

JBS
Dec 13, 2021

I think correct answer is B. Focus on word "Automatically" It never assigns public IP automatically but you have to enable it by yourself.

Blimpy
Jan 22, 2021

i was wondering how this would work in a scenario for monitoring the instances as I would expect the PIP to be static if it needs to be monitored... however I see it possible by using domain name labels for the dynamic PIPs - : https://docs.microsoft.com/en-us/azure/virtual-network/public-ip-addresses#dns-hostname-resolution ... So this answer could be YES ... however it seems to be more complicated with VMSS using PIP as names need to be auto generated https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-public-ip-address#virtual-machine-scale-sets .. This doesnt seem to be a n easy way for monitoring, however to answer the question of defining a public access to the VMS, I would answer YES to this question.. although Im not entirely confident with it

GetulioJr
May 30, 2021

Of course not. Scale set is for identical VMS, that is not the case. it does not meet the requirements, and cannot be used like that.

pentium75
Jul 14, 2021

Why not? The whole question is about a scale set. It's just, how to make the VMs in the scale set accessible from other VNet. Public IP for all VMs in the scale set would be an idiotic solution, but it would work.

medi01
Aug 17, 2021

How would you figure the IP address of a dynamically allocated VM?

tteesstt
Aug 21, 2021

Automation script?

tteesstt
Aug 21, 2021

Automation script?

medi01
Aug 17, 2021

How would you figure the IP address of a dynamically allocated VM?

tteesstt
Aug 21, 2021

Automation script?

tteesstt
Aug 21, 2021

Automation script?