VNet-to-VNet connectivity in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a virtual network with the correct address space.

Azure

az network vnet create --name MyVNet --resource-group MyResourceGroup --address-prefix [1]

Drag options to blanks, or click blank then click option'

A192.168.1.0/24

B10.0.0.0/16

C172.16.0.0/12

D255.255.255.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using a subnet mask instead of CIDR notation.

Using a public IP range.

The address prefix for a virtual network must be a valid CIDR block like 10.0.0.0/16.

2fill in blank

medium

Complete the code to create a virtual network peering from VNet1 to VNet2.

Azure

az network vnet peering create --name VNet1ToVNet2 --resource-group MyResourceGroup --vnet-name VNet1 --remote-vnet-id [1] --allow-vnet-access

Drag options to blanks, or click blank then click option'

AMyResourceGroup

BVNet3

C/subscriptions/{subscription-id}/resourceGroups/MyResourceGroup/providers/Microsoft.Network/virtualNetworks/VNet2

DVNet1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the VNet name instead of the full resource ID.

Using the resource group name instead of VNet resource ID.

The remote virtual network ID must be the full resource ID of the VNet you want to peer with, here VNet2.

3fill in blank

hard

Fix the error in the peering command by completing the missing parameter for allowing forwarded traffic.

Azure

az network vnet peering update --name VNet1ToVNet2 --resource-group MyResourceGroup --vnet-name VNet1 --set allowForwardedTraffic=[1]

Drag options to blanks, or click blank then click option'

Afalse

Benabled

Cyes

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using string values like 'yes' or 'enabled' instead of true.

Using false disables forwarded traffic.

The parameter allowForwardedTraffic expects a boolean value true or false. Use true to allow forwarded traffic.

4fill in blank

hard

Fill both blanks to create a peering that allows gateway transit and uses remote gateways.

Azure

az network vnet peering create --name VNet2ToVNet1 --resource-group MyResourceGroup --vnet-name VNet2 --remote-vnet-id /subscriptions/{subscription-id}/resourceGroups/MyResourceGroup/providers/Microsoft.Network/virtualNetworks/VNet1 --allow-vnet-access --allow-gateway-transit=[1] --use-remote-gateways=[2]

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

Cyes

Dno

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up true and false for these parameters.

Using 'yes' or 'no' instead of boolean values.

To allow gateway transit and use remote gateways, set allow-gateway-transit to true and use-remote-gateways to true.

5fill in blank

hard

Fill all three blanks to create a subnet with the correct name, address prefix, and network security group association.

Azure

az network vnet subnet create --resource-group MyResourceGroup --vnet-name MyVNet --name [1] --address-prefix [2] --network-security-group [3]

Drag options to blanks, or click blank then click option'

AGatewaySubnet

B10.0.1.0/24

CMyNSG

DSubnet1

Attempts:

3 left

💡 Hint

Common Mistakes

Using special subnet names like GatewaySubnet which cannot have NSG.

Using an invalid address prefix.

Not associating the correct NSG.

The subnet name is 'Subnet1'. The address prefix must be a valid CIDR block like 10.0.1.0/24. The network security group must be the name of an existing NSG, here 'MyNSG'.