ExpressRoute for dedicated connections in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an ExpressRoute circuit with the correct SKU.

Azure

az network express-route create --name myCircuit --resource-group myResourceGroup --location eastus --bandwidth 200 --sku [1]

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

AStandard_UnlimitedData

BPremium_MeteredData

CBasic_UnlimitedData

DStandard_MeteredData

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a SKU that does not support unlimited data.

Using a SKU that is not valid for the specified location.

The SKU Standard_UnlimitedData is a valid SKU for ExpressRoute circuits providing unlimited data with standard features.

2fill in blank

medium

Complete the code to link the ExpressRoute circuit to a virtual network gateway.

Azure

az network vpn-connection create --name myConnection --resource-group myResourceGroup --vnet-gateway1 myVnetGateway --express-route-circuit2 [1] --location eastus

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

AmyExpressRouteCircuit

BmyVnet

CmyResourceGroup

DmySubnet

Attempts:

3 left

💡 Hint

Common Mistakes

Using the virtual network name instead of the ExpressRoute circuit name.

Confusing resource group name with circuit name.

The parameter --express-route-circuit2 expects the name of the ExpressRoute circuit to link to the VPN connection.

3fill in blank

hard

Fix the error in the command to create a peering on the ExpressRoute circuit.

Azure

az network express-route peering create --circuit-name myCircuit --resource-group myResourceGroup --peering-type [1] --peer-asn 65010 --vlan 200

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

APublicPeering

BAzurePrivatePeering

CPrivatePeering

DMicrosoftPeering

Attempts:

3 left

💡 Hint

Common Mistakes

Using PrivatePeering when MicrosoftPeering is required.

Confusing peering types and their purposes.

The correct peering type for Microsoft services over ExpressRoute is MicrosoftPeering.

4fill in blank

hard

Fill both blanks to configure the ExpressRoute circuit with the correct service provider and peering location.

Azure

az network express-route create --name myCircuit --resource-group myResourceGroup --location eastus --bandwidth 1000 --provider [1] --peering-location [2]

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

AEquinix

BLevel3

CSilicon Valley

DWashington DC

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing provider names with peering locations.

Using invalid or unsupported provider names.

The service provider Equinix and peering location Silicon Valley are valid and commonly paired for ExpressRoute circuits.

5fill in blank

hard

Fill all three blanks to create an ExpressRoute circuit with the correct SKU, bandwidth, and peering location.

Azure

az network express-route create --name myCircuit --resource-group myResourceGroup --location eastus --bandwidth [1] --sku [2] --peering-location [3]

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

A500

BStandard_UnlimitedData

CNew York

D200

EPremium_MeteredData

Attempts:

3 left

💡 Hint

Common Mistakes

Using bandwidth values not supported by the SKU.

Choosing peering locations not available in the region.

The bandwidth 200 Mbps, SKU Standard_UnlimitedData, and peering location New York form a valid ExpressRoute circuit configuration.