VNet creation and address space in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the address space for the virtual network.

Azure

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

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

A"255.255.255.0"

B"192.168.1.0/24"

C"172.16.0.0/12"

D"10.0.0.0/16"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a subnet mask instead of CIDR notation.

Choosing an address space too small for the network.

The address space must be a valid CIDR block like "10.0.0.0/16". Option D is a subnet mask, not an address space.

2fill in blank

medium

Complete the code to create a subnet within the VNet with the correct address prefix.

Azure

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

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

A"10.0.1.0/24"

B"192.168.1.0/24"

C"10.0.0.0/16"

D"172.16.0.0/12"

Attempts:

3 left

💡 Hint

Common Mistakes

Using an address prefix outside the VNet's range.

Using the same prefix as the VNet for the subnet.

The subnet address prefix must be a subset of the VNet's address space. "10.0.1.0/24" fits inside "10.0.0.0/16".

3fill in blank

hard

Fix the error in the VNet creation command by choosing the correct parameter for address space.

Azure

az network vnet create --name MyVNet --resource-group MyResourceGroup --[1] "10.0.0.0/16"

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

Aaddress-prefixes

Baddress-prefix

Caddress-space

Dsubnet-prefix

Attempts:

3 left

💡 Hint

Common Mistakes

Using a singular form that does not exist.

Confusing subnet prefix with VNet address space.

The correct parameter to specify one or more address spaces is --address-prefixes.

4fill in blank

hard

Fill both blanks to create a VNet with two address spaces.

Azure

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

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

A"10.0.0.0/16"

B"192.168.0.0/16"

C"10.1.0.0/16"

D"172.16.0.0/12"

Attempts:

3 left

💡 Hint

Common Mistakes

Using overlapping address spaces.

Using invalid CIDR notation.

You can specify multiple address spaces separated by spaces. Here, "10.0.0.0/16" and "10.1.0.0/16" are valid and non-overlapping.

5fill in blank

hard

Fill all three blanks to create a subnet with a specific name and address prefix inside a VNet.

Azure

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

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

AMyVNet

BMySubnet

C"10.0.2.0/24"

DMyResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing resource group name with VNet name.

Using invalid address prefix format.

The VNet name is "MyVNet", the subnet name is "MySubnet", and the subnet address prefix must be a valid CIDR block inside the VNet.

Practice

1. What does the address space in an Azure Virtual Network (VNet) define?

easy

A. The physical location of the VNet data center

B. The number of virtual machines allowed in the VNet

C. The range of IP addresses available for resources inside the VNet

D. The security rules applied to the VNet

Solution

1. Step 1: Understand the purpose of address space in VNet

   The address space specifies the IP address range that the VNet can use for its resources.

2. Step 2: Differentiate from other VNet properties

   Physical location, VM count, and security rules are separate configurations unrelated to address space.

3. Final Answer:

   The range of IP addresses available for resources inside the VNet -> Option C

4. Quick Check:

   Address space = IP range [OK]

Hint: Address space means IP range inside the VNet [OK]

Common Mistakes:

• Confusing address space with location
• Thinking address space limits VM count
• Mixing address space with security settings

2. Which Azure CLI command correctly creates a VNet named MyVNet with address space 10.0.0.0/16 in resource group MyGroup?

easy

A. az network vnet create --name MyVNet --resource-group MyGroup --address-prefixes 10.0.0.0/16

B. az network vnet create --vnet-name MyVNet --group MyGroup --address-space 10.0.0.0/16

C. az vnet create --name MyVNet --resource-group MyGroup --address 10.0.0.0/16

D. az network vnet new --name MyVNet --resource-group MyGroup --address-prefix 10.0.0.0/16

Solution

1. Step 1: Identify correct Azure CLI syntax for VNet creation

   The correct command uses az network vnet create with parameters --name, --resource-group, and --address-prefixes.

2. Step 2: Check each option for syntax correctness

   az network vnet create --name MyVNet --resource-group MyGroup --address-prefixes 10.0.0.0/16 matches the correct syntax. Other options use incorrect commands (like az vnet create or az network vnet new) or parameter names (like --vnet-name, --group, --address-space, --address, --address-prefix).

3. Final Answer:

   az network vnet create --name MyVNet --resource-group MyGroup --address-prefixes 10.0.0.0/16 -> Option A

4. Quick Check:

   Correct CLI syntax = az network vnet create --name MyVNet --resource-group MyGroup --address-prefixes 10.0.0.0/16 [OK]

Hint: Use --address-prefixes for IP range in az network vnet create [OK]

Common Mistakes:

• Using wrong parameter names like --address-space
• Using incorrect commands like az vnet create
• Mixing resource group parameter names

3. Given the Azure CLI command:

az network vnet create --name TestVNet --resource-group TestGroup --address-prefixes 192.168.0.0/24

What is the size of the IP address range allocated to TestVNet?

medium

A. 1024 IP addresses

B. 65,536 IP addresses

C. 16 IP addresses

D. 256 IP addresses

Solution

1. Step 1: Understand CIDR notation /24

   The /24 means the first 24 bits are fixed, leaving 8 bits for host addresses.

2. Step 2: Calculate number of IP addresses

   2^8 = 256 IP addresses are available in the 192.168.0.0/24 range.

3. Final Answer:

   256 IP addresses -> Option D

4. Quick Check:

   /24 = 256 IPs [OK]

Hint: /24 means 256 IP addresses in the range [OK]

Common Mistakes:

• Confusing /24 with /16 or /28
• Miscounting IP addresses as 1024 or 65,536
• Ignoring subnet mask meaning

4. You try to create a VNet with the command:

az network vnet create --name MyVNet --resource-group MyGroup --address-prefixes 10.0.0.0/16 10.0.0.0/24

But it fails. What is the most likely reason?

medium

A. The VNet name is already in use

B. You cannot specify overlapping address spaces in one VNet

C. The resource group name is invalid

D. The command requires a location parameter

Solution

1. Step 1: Analyze the address prefixes given

   The prefixes 10.0.0.0/16 and 10.0.0.0/24 overlap because /24 is a subset of /16.

2. Step 2: Understand Azure VNet address space rules

   Azure does not allow overlapping address spaces within the same VNet.

3. Final Answer:

   You cannot specify overlapping address spaces in one VNet -> Option B

4. Quick Check:

   Overlapping address spaces cause failure [OK]

Hint: Avoid overlapping IP ranges in one VNet [OK]

Common Mistakes:

• Assuming location is mandatory for this error
• Thinking resource group name causes this error
• Believing VNet name conflict causes this error

5. You want to create a VNet with two non-overlapping address spaces: 10.1.0.0/16 and 10.2.0.0/16. Which command correctly creates this VNet named MultiVNet in resource group RG1?

hard

A. az network vnet create --name MultiVNet --resource-group RG1 --address-prefixes 10.1.0.0/16 10.2.0.0/16

B. az network vnet create --name MultiVNet --resource-group RG1 --address-prefix 10.1.0.0/16,10.2.0.0/16

C. az network vnet create --name MultiVNet --resource-group RG1 --address-prefixes 10.1.0.0/16,10.2.0.0/16

D. az network vnet create --name MultiVNet --resource-group RG1 --address-space 10.1.0.0/16 10.2.0.0/16

Solution

1. Step 1: Check correct parameter for multiple address spaces

   The parameter --address-prefixes accepts multiple space-separated CIDR blocks.

2. Step 2: Validate syntax for multiple prefixes

   az network vnet create --name MultiVNet --resource-group RG1 --address-prefixes 10.1.0.0/16 10.2.0.0/16 uses space-separated prefixes correctly. Using commas to separate prefixes, singular --address-prefix, or --address-space instead of --address-prefixes is invalid.

3. Final Answer:

   az network vnet create --name MultiVNet --resource-group RG1 --address-prefixes 10.1.0.0/16 10.2.0.0/16 -> Option A

4. Quick Check:

   Multiple prefixes = space-separated with --address-prefixes [OK]

Hint: Use --address-prefixes with spaces for multiple CIDRs [OK]

Common Mistakes:

• Using commas instead of spaces between prefixes
• Using --address-prefix instead of --address-prefixes
• Using --address-space which is invalid