Microsoft AZ-104 Practice Test - Questions Answers, Page 22

Statement 1 : Basic load balancer supports Virtual machine in a single Availability set or virtual machine scale set (VMSS) only . Hence this statement is correct.

Statement 2 : Basic load balancer supports Virtual machine in a single Availability set or virtual scale set only or one standalone VM. VM3 and VM4 are not part of any availability set or VMSS .Hence this statement is incorrect.

Statement 3 : Basic load balancer supports Virtual machine in a single Availability set or virtual scale set only or one standalone VM. VM5 and VM6 are not part of any availability set or VMSS .Hence this statement is incorrect.

Reference:

https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview

To port forward traffic to a specific port on specific VMs use an inbound network address translation (NAT) rule.

https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview an inbound NAT rule :

Create a load balancer inbound network address translation (NAT) rule to forward traffic from a specific port of the front-end IP address to a specific port of a back-end VM.

Hence this option is Correct a load balancing rule : Incorrect Choice

A load balancer rule defines how traffic is distributed to the VMs. The rule defines the front-end IP configuration for incoming traffic, the back-end IP pool to receive the traffic, and the required source and destination ports.

a new public load balancer for VM3 : Incorrect Choice

This option will not help you since this will route all traffic to VM3 only. a frontend IP configuration : Incorrect Choice

When you define an Azure Load Balancer, a frontend and a backend pool configuration are connected with rules. The health probe referenced by the rule is used to determine how new flows are sent to a node in the backend pool. The frontend (aka VIP) is defined by a 3-tuple comprised of an IP address (public or internal), a transport protocol (UDP or TCP), and a port number from the load balancing rule. The backend pool is a collection of Virtual Machine IP configurations (part of the NIC resource) which reference the Load Balancer backend pool.

Reference:

https://docs.microsoft.com/en-us/azure/load-balancer/tutorial-load-balancer-port-forwardingportal

https://pixelrobots.co.uk/2017/08/azure-load-balancer-for-rds/

The virtual networks can be in the same or different regions, and from the same or different subscriptions. When connecting VNets from different subscriptions, the subscriptions do not need to be associated with the same Active Directory tenant.

Configuring a VNet-to-VNet connection is a good way to easily connect VNets. Connecting a virtual network to another virtual network using the VNet-to-VNet connection type (VNet2VNet) is similar to creating a Site-to-Site IPsec connection to an on-premises location. Both connectivity types use a VPN gateway to provide a secure tunnel using IPsec/IKE, and both function the same way when communicating.

The local network gateway for each VNet treats the other VNet as a local site. This lets you specify additional address space for the local network gateway in order to route traffic.

Reference: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-vnet-vnetresource-manager-portal

Box 1: No

It limits traffic to VM2, but not VM1 traffic.

Box 2: Yes

Yes, the destination is VM2.

Box 3: No

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/network-security-group-how-it-works

Box1: LRS will keep minimum three copies.

Box2: Changing the access tier from hot to cool will reduce the cost. In performance, standard is cheap.

In the Account kind, GPV2 is giving best price. Can be checked yourself using the pricing calculator on below link.

Reference:

https://azure.microsoft.com/en-in/pricing/calculator/?service=storage

Reference:

https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/app-based-mfa

Installing Azure CLI doesn't mean that Azure Kubernates client is installed. So before running kubectl client command, you have install kubectl, the Kubernetes command-line client.

First need to run az aks install-cli to install Kubernetes CLI, which is kubectl

Reference:

https://docs.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest

Installing Azure CLI doesn't mean that Azure Kubernates client is installed. So before running kubectl client command, you have install kubectl, the Kubernetes command-line client.

First need to run az aks install-cli to install Kubernetes CLI, which is kubectl

Reference:

https://docs.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest

Kubectl is not installed by installing AZ ClI. As stated Azure CLI is already available but installing Azure CLI doesn't mean that Azure Kubernates client is also installed. So before running any aks command, we have to install kubectl, the Kubernetes command-line client. az aks install-cli

Reference:

https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough#connect-to-the-cluster