VNet peering for connectivity in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a VNet peering from VNetA to VNetB.

Azure

az network vnet peering create --name VNetAtoVNetB --resource-group MyResourceGroup --vnet-name VNetA --remote-vnet [1] --allow-vnet-access

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

AVNetB

BVNetC

CVNetD

DVNetE

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong VNet name for the remote VNet.

Confusing the local VNet name with the remote VNet name.

The remote VNet name must be the target VNet you want to peer with, here it is VNetB.

2fill in blank

medium

Complete the code to allow forwarded traffic in the VNet peering.

Azure

az network vnet peering create --name VNetBtoVNetA --resource-group MyResourceGroup --vnet-name VNetB --remote-vnet VNetA --allow-vnet-access --allow-[1]-traffic

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

Aprivate

Bgateway

Cinternet

Dforwarded

Attempts:

3 left

💡 Hint

Common Mistakes

Using --allow-gateway-traffic instead of --allow-forwarded-traffic.

Confusing forwarded traffic with internet traffic.

To allow traffic that is forwarded through a virtual appliance, use --allow-forwarded-traffic.

3fill in blank

hard

Fix the error in the peering creation command by completing the missing parameter.

Azure

az network vnet peering create --name VNetAtoVNetB --resource-group MyResourceGroup --vnet-name VNetA --remote-vnet VNetB --allow-vnet-access --[1]-gateway-use

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

Adisable

Benable

Callow

Dblock

Attempts:

3 left

💡 Hint

Common Mistakes

Using --enable-gateway-use which is invalid.

Using --disable-gateway-use which disables the feature.

The correct parameter to allow gateway transit is --allow-gateway-use.

4fill in blank

hard

Fill both blanks to create a peering that allows gateway transit and forwarded traffic.

Azure

az network vnet peering create --name VNetBtoVNetA --resource-group MyResourceGroup --vnet-name VNetB --remote-vnet VNetA --allow-[1]-gateway-use --allow-[2]-traffic

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

Aallow

Bforwarded

Cinternet

Dblock

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'internet' or 'block' instead of 'forwarded' for traffic.

Using 'enable' instead of 'allow' for gateway use.

Use --allow-gateway-use to allow gateway transit and --allow-forwarded-traffic to allow forwarded traffic.

5fill in blank

hard

Fill all three blanks to update an existing peering to allow gateway transit, forwarded traffic, and remote VNet access.

Azure

az network vnet peering update --name VNetAtoVNetB --resource-group MyResourceGroup --vnet-name VNetA --set allow[1]gatewayUse=[2] allow[3]traffic=[4]

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

AGateway

BForwarded

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'False' instead of 'True' to enable permissions.

Swapping 'Gateway' and 'Forwarded' in the wrong places.

To update the peering, set allowGatewayUse=true and allowForwardedTraffic=true.