VNet creation and address space in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Virtual Network (VNet) in Azure?

A Virtual Network (VNet) is like a private network in the cloud where your Azure resources can securely communicate with each other, just like devices connected in your home Wi-Fi network.

beginner

Why do you need to specify an address space when creating a VNet?

The address space defines the range of IP addresses that your VNet can use. It’s like setting the size of your neighborhood so devices inside don’t get overlapping addresses.

intermediate

What format is used to define the address space in a VNet?

The address space is defined using CIDR notation, for example, 10.0.0.0/16, which means the network includes all IP addresses from 10.0.0.0 to 10.0.255.255.

intermediate

Can you add multiple address spaces to a single VNet?

Yes, you can add multiple address spaces to a VNet to expand the range of IP addresses available, similar to adding more streets to your neighborhood.

advanced

What happens if two VNets have overlapping address spaces?

If two VNets have overlapping address spaces, it can cause communication problems because IP addresses may conflict, like two houses having the same street address.

What does the address space in a VNet define?

A The storage capacity of the VNet

B The number of virtual machines allowed

C The physical location of the VNet

D The range of IP addresses available in the VNet

The address space defines the range of IP addresses that the VNet can use.

Which notation is used to specify the address space in a VNet?

A Decimal notation

B CIDR notation

C Hexadecimal notation

D Binary notation

CIDR notation (e.g., 10.0.0.0/16) is used to define the address space.

Can a VNet have more than one address space?

A Yes, to expand IP ranges

B No, only one address space is allowed

C Only if using IPv6

D Only in premium subscriptions

You can add multiple address spaces to a VNet to increase available IP addresses.

What issue arises if two VNets have overlapping address spaces?

A IP address conflicts causing communication problems

B Faster network speeds

C Automatic merging of VNets

D No issues at all

Overlapping address spaces cause IP conflicts, preventing proper communication.

Which of the following is NOT a reason to define a VNet address space carefully?

A Avoid IP conflicts

B Ensure enough IPs for resources

C Control physical location of resources

D Allow future network expansion

Address space does not control physical location; it controls IP ranges.

Explain what a VNet is and why defining an address space is important.

Think about how devices connect in a home network.

Describe the consequences of overlapping address spaces between two VNets.

Imagine two houses with the same street address.

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