CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. AZ-104

Free AZ-104 Exam Braindumps (page: 37)

Page 36 of 132
PDF with 521 Questions

You have an Azure subscription that contains the resources shown in the following table.



You create a route table named RT1 in the East US Azure region.

To which resources can you associate RT1?

  1. VNet1 only
  2. Subnet1 only
  3. VNet1 and NIC1 only
  4. Subnet1 and NIC1 only
  5. VNet1, Subnet1, and NIC1

Answer(s): B

Explanation:

Azure automatically routes traffic between Azure subnets, virtual networks, and on-premises networks. If you want to change Azure's default routing, you do so by creating a route table.

Associate a route table to a subnet
You can optionally associate a route table to a subnet. A route table can be associated to zero or more subnets. Route tables aren't associated to virtual networks. You must associate a route table to each subnet you want the route table associated to.

You can only associate a route table to subnets in virtual networks that exist in the same Azure location and subscription as the route table.


Reference:

https://learn.microsoft.com/en-us/azure/virtual-network/manage-route-table



You have an Azure subscription.
You create a routing table named RT1.
You need to add a route to RT1 that specifies the next hop IP address.

Which next hop type should you select?

  1. Internet
  2. Virtual network gateway
  3. Virtual network
  4. Virtual appliance

Answer(s): D



You have two Azure subscriptions named Sub1 and Sub2 that are linked to separate Microsoft Entra tenants.



You have the virtual networks shown in the following table.

Which virtual networks can you peer with VNet1?

  1. VNet2 only
  2. VNet2 and VNet3 only
  3. VNet2 and VNet4 only
  4. VNet2, VNet3, and VNet4 only
  5. VNet2, VNet3, VNet4, and VNet5

Answer(s): E

Explanation:

* Yes - VNet2 - in the same location and subscription as VNet1.

* Yes - VNet3 - in the same subscription as VNet1, but different regions.

Every subscription can create up to 50 virtual networks across all regions.

Note: Peering virtual networks in different regions is also referred to as Global Virtual Network Peering.

* Yes - VNet4 - different subscription, same region.

The virtual networks to be peered can belong to the same subscription or different subscriptions. Virtual networks can be peered within the same region or across different regions. Peering virtual networks across different regions is also called Global VNet Peering.

* Yes - VNet5 - different subscription, different region.

The virtual networks to be peered can belong to the same subscription or different subscriptions. Virtual networks can be peered within the same region or across different regions. Peering virtual networks across different regions is also called Global VNet Peering.


Reference:

https://azure.microsoft.com/en-us/pricing/details/virtual-network/
https://www.linkedin.com/pulse/how-peer-two-azure-virtual-networks-jon-bonso-nsvje



HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription that contains the virtual networks shown in the following table.



You have the peering options shown in the following exhibit.



You need to design a communication strategy for the resources on the virtual networks.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.

NOTE: Each correct selection is worth one point.

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: No
No - Peering 1-2 is a possible configuration.

Peering 1-2 is between VNet1 and VNet2.
VNet1 is in East US.
VNet1 is of type Azure Government.
VNet2 is in West US 2.
VNet2 is of type Public.

Note: Peering virtual networks across different regions is also called Global VNet Peering.

Global VNet Peering is generally available in all Azure Government cloud regions. This means you can peer virtual networks across the Azure Government cloud regions. You cannot peer across Azure Government cloud and Azure public cloud regions.

Box 2: Yes
Yes - Peering 1-3 is a possible configuration.

Peering 1-3 is between VNet1 and VNet3.
VNet1 is in East US.
VNet1 is of type Azure Government.
VNet3 is in Chine East.
VNet3 is of type Azure China.

Neither VNet1 or VNet3 are public, so global network peering is possible.

Note: Global VNet Peering now supports Standard Load Balancer.
This support is in all Azure regions, including Azure China and Azure Government regions.

Box 3: No
No - Peering 3-2 is a possible configuration.

As per same logic as for Box 1.


Reference:

https://azure.microsoft.com/en-us/updates/global-vnet-peering-available-in-azure-government/
https://azure.microsoft.com/en-us/updates/global-vnet-peering-now-supports-standard-load-balancer/






Post your Comments and Discuss Microsoft AZ-104 exam with other Community members:

AZ-104 Exam Discussions & Posts