VNet creation and address space in Azure - Mini Project: Build & Apply

VNet creation and address space

📖 Scenario: You are setting up a basic network in Microsoft Azure for a small company. This network will allow their virtual machines to communicate securely within a private space.

🎯 Goal: Create an Azure Virtual Network (VNet) with a specific address space to isolate and manage the company's cloud resources.

📋 What You'll Learn

Create a variable named vnet_name with the exact value MyCompanyVNet.

Create a variable named address_space with the exact value 10.0.0.0/16.

Define a resource block for an Azure Virtual Network using the variables vnet_name and address_space.

Add the location attribute with the value eastus to the Virtual Network resource.

💡 Why This Matters

🌍 Real World

Creating a Virtual Network is a fundamental step in setting up cloud infrastructure in Azure. It allows secure communication between resources.

💼 Career

Cloud engineers and architects frequently create and configure VNets to isolate and manage network traffic in Azure environments.

1

Create variables for VNet name and address space

Create a variable called vnet_name and set it to "MyCompanyVNet". Then create a variable called address_space and set it to ["10.0.0.0/16"].

Azure

# Create variables 'vnet_name' and 'address_space'
vnet_name = ""
address_space = []
# Your code here

Hint

Use simple assignment to create the variables with the exact names and values.

2

Start defining the Azure Virtual Network resource

Create a dictionary called virtual_network with a key name set to the variable vnet_name. Also add a key address_space set to the variable address_space.

Azure

vnet_name = "MyCompanyVNet"
address_space = ["10.0.0.0/16"]

# Create dictionary 'virtual_network' with keys 'name' and 'address_space'
virtual_network = {}
# Your code here

Hint

Use a dictionary with keys exactly named name and address_space.

3

Add location to the Virtual Network configuration

Add a key location with the value "eastus" to the virtual_network dictionary.

Azure

vnet_name = "MyCompanyVNet"
address_space = ["10.0.0.0/16"]

virtual_network = {
    "name": vnet_name,
    "address_space": address_space
}

# Add key 'location' with value '"eastus"' to 'virtual_network'
# Your code here

Hint

Add the location key-value pair inside the existing dictionary.

4

Complete the Virtual Network resource with type and properties

Create a dictionary called vnet_resource with keys: type set to "Microsoft.Network/virtualNetworks", name set to vnet_name, location set to "eastus", and properties set to a dictionary with key addressSpace set to a dictionary with key addressPrefixes set to address_space.

Azure

vnet_name = "MyCompanyVNet"
address_space = ["10.0.0.0/16"]

virtual_network = {
    "name": vnet_name,
    "address_space": address_space,
    "location": "eastus"
}

# Create dictionary 'vnet_resource' with keys 'type', 'name', 'location', and 'properties'
# Your code here

Hint

Follow the Azure resource structure with nested dictionaries for properties and address space.

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