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

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-connect-virtual-networks-portal

You can connect virtual networks to each other with virtual network peering. These virtual networks can be in the same region or different regions (also known as Global VNet peering). Once virtual networks are peered, resources in both virtual networks are able to communicate with each other, with the same latency and bandwidth as if the resources were in the same virtual network.

Global VNet Peering is now generally available in all Azure public regions, excluding the China, Germany, and Azure Government regions.

The address space is the most critical configuration for a VNet in Azure. This is the IP range for the entire network that will be divided into subnets. The address space can almost be any IP range that you wish (public or private). You can add multiple address spaces to a VNet. To ensure this VNet can be connected to other networks, the address space should never overlap with any other networks in your environment. If a VNet has an address space that overlaps with another Azure VNet or on premises network, the networks cannot be connected, as the routing of traffic will not work properly.

https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-connect-virtual-networks-portal

https://azure.microsoft.com/en-in/updates/general-availability-global-vnetpeering/#:~:text=Global%20VNet%20Peering%20is%20now,transit%20over%20the%20public%20internet.

https://www.microsoftpressstore.com/articles/article.aspx?p=2873369

Box 1: Remove the public IP address from VM1

If the Public IP on VM1 is set to Dynamic, that means it is a Public IP with Basic SKU because Public IPs with Standard SKU have Static assignments by default, that cannot be changed. We cannot associate Basic SKUs IPs with Standard SKUs LBs. One cannot create a backend SLB pool if the VM to be associated has a Public IP. For Private IP it doesn't matter weather it is dynamic or static, still we can add the such VM into the SLB backend pool.

Box 2: Create and configure an NSG

Standard Load Balancer is built on the zero trust network security model at its core. Standard Load Balancer secure by default and is part of your virtual network. The virtual network is a private and isolated network. This means Standard Load Balancers and Standard Public IP addresses are closed to inbound flows unless opened by Network Security Groups. NSGs are used to explicitly permit allowed traffic. If you do not have an NSG on a subnet or NIC of your virtual machine resource, traffic is not allowed to reach this resource. To learn more about NSGs and how to apply them for your scenario, see Network Security Groups. Basic Load Balancer is open to the internet by default.

Reference:

https://docs.microsoft.com/en-us/azure/load-balancer/quickstart-load-balancer-standard-publicportal

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

Before creating a network interface, you must have an existing virtual network in the same location and subscription you create a network interface in.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface

Box 1: Yes

A Basic Load Balancer supports virtual machines in a single availability set or virtual machine scale set.

Box 2: Yes

When using load-balancing rules with Azure Load Balancer, you need to specify health probes to allow Load Balancer to detect the backend endpoint status. The configuration of the health probe and probe responses determine which backend pool instances will receive new flows. You can use health probes to detect the failure of an application on a backend endpoint. You can also generate a custom response to a health probe and use the health probe for flow control to manage load or planned downtime. When a health probe fails, Load Balancer will stop sending new flows to the respective unhealthy instance. Outbound connectivity is not impacted, only inbound connectivity is impacted.

Box 3: No

Reference:

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

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

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-supportresources

https://docs.microsoft.com/en-us/azure/virtual-network/move-across-regions-publicip-powershell

Azure Import/Export service supports the following of storage accounts:

Standard General Purpose v2 storage accounts (recommended for most scenarios)

Blob Storage accounts

General Purpose v1 storage accounts (both Classic or Azure Resource Manager deployments),

Azure Import/Export service supports the following storage types

Import supports Azure Blob storage and Azure File storage

Export supports Azure Blob storage

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-import-export-requirements