Scenario: Litware must meet technical requirements including:
Ensure that VM3 can establish outbound connections over TCP port 8080 to the applications servers in the Montreal office.
IP flow verify checks if a packet is allowed or denied to or from a virtual machine. The information consists of direction, protocol, local IP, remote IP, local port, and remote port. If the packet is denied by a security group, the name of the rule that denied the packet is returned. While any source or destination IP can be chosen, IP flow verify helps administrators quickly diagnose connectivity issues from or to the internet and from or to the on-premises environment.
References:
https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-ip-flow-verify-overview

The correct answer is Subnet1 only . In Azure, a route table is associated to one or more subnets , not directly to a virtual network or a network interface. Microsoft states that after creating custom routes, you associate the route table to zero or more virtual network subnets, and each subnet can have zero or one route table associated with it. This means RT1 can be associated with Subnet1 , provided the subnet is in a virtual network in the same Azure location and subscription as the route table. Here, RT1 is created in East US , and Subnet1 is also in East US , so the association is valid.
RT1 cannot be associated directly with VNet1 , because route tables apply at the subnet level within a virtual network rather than the VNet object itself. RT1 also cannot be associated directly with NIC1 ; network interfaces have effective routes, but those routes are derived from system routes, subnet-associated route tables, BGP routes, and other platform routing behavior. Therefore, among the listed resources, only Subnet1 is a valid route table association target. Study Guide reference: AZ-104 Configure and manage virtual networking , specifically configuring route tables, user-defined routes, and subnet-level routing.

Explanation:

When any internet user will try to access the cluster which is behind a load balancer, traffic will first hit to load balancer front end IP. So in the DNS configuration you have to provide the IP address of the load balancer.
Reference:
https://stackoverflow.com/questions/43660490/giving-a-dns-name-to-azure-load-balancer

Explanation: