Hotspot Question
You have a virtual machine (VM) that must be secured. Direct access to the VM is not permitted.
You create the following Azure PowerShell script. Line numbers are included for reference only.
You assign the virtual network to the variable $vnet. You assign the subnet to the variable
$backendSubnet. For each of the following statements, select Yes if the statement is true.
Otherwise, select No.
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-get-started-internet-arm-ps
Even though it does not have the public IP address (as it should for internet facing) for the front-end IP I would still say that the inbound NAT rule does allow direct access to the VM instance on port 3441 to 3389.
I agree with the other answers (will only allow port 80 traffic an interface is on virtual network).
Yes, No, Yes
0
0
I don’t think this is meant to be an internet-facing LB. It’s being built as an Internal Load-Balancer.
1) {YES}: The LBRule does configure direct access (via RDP) on port 3441 (translated to 3389) – so users will be able to access it.
2) {NO}:This is an internal L/B (configured with Private IP vs PublicIP) so Zero internet traffic will be able to reach the backend pool.
3) {YES}: You can see that the $backendnic is configured to use $backendsubnet which is on NPRVNet.
Support Article:
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-get-started-ilb-arm-ps
0
0
I would go with
No – It’s behind a LB, so it can never be direct.
No – There is no incoming internet traffic. The frontend IP is no PIP.
No – Interfaces don’t connect to VNETs, they connect to the machine or the LB.
0
0
Network interfaces
A network interface (NIC) is the interconnection between a VM and a virtual network (VNet). A VM must have at least one NIC, but can have more than one, depending on the size of the VM you create. Learn about how many NICs each VM size supports in Sizes for virtual machines in Azure.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/network-overview
0
0