Exam AZ-303 topic 5 question 73 discussion

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

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.

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

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

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

Yes, it will meet the goal

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

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.

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

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

A is the correct

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