Creating a custom VPC in AWS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a new VPC with a CIDR block.

AWS

resource "aws_vpc" "main" {
  cidr_block = "[1]"
}

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

A10.0.0.0/16

B256.0.0.0/16

C172.16.0.0/12

D192.168.0.0/24

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid CIDR block like 256.0.0.0/16

Using a public IP range

The CIDR block 10.0.0.0/16 is a valid private IP range commonly used for VPCs.

2fill in blank

medium

Complete the code to enable DNS support in the VPC.

AWS

resource "aws_vpc" "main" {
  cidr_block           = "10.0.0.0/16"
  enable_dns_support   = [1]
}

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

A"true"

Btrue

Cyes

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around boolean values

Using strings like 'yes' instead of boolean true

The enable_dns_support attribute expects a boolean value true or false, not a string.

3fill in blank

hard

Fix the error in the subnet resource by completing the missing VPC ID reference.

AWS

resource "aws_subnet" "subnet1" {
  vpc_id     = [1]
  cidr_block = "10.0.1.0/24"
}

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

A"aws_vpc.main.id"

Bmain.id

Caws_vpc.main.id

Dvpc_id

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the reference in quotes, making it a string literal

Using undefined variables

The vpc_id must reference the VPC resource ID without quotes to link the subnet correctly.

4fill in blank

hard

Fill both blanks to create a route table and associate it with the subnet.

AWS

resource "aws_route_table" "rt" {
  vpc_id = [1]
}

resource "aws_route_table_association" "rta" {
  subnet_id      = [2]
  route_table_id = aws_route_table.rt.id
}

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

Aaws_vpc.main.id

Baws_subnet.subnet1.id

Csubnet1.id

Dmain.id

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or incomplete resource references

Mixing resource names and IDs

The route table must be linked to the VPC ID, and the association must use the subnet's ID.

5fill in blank

hard

Fill all three blanks to create an internet gateway, attach it to the VPC, and add a route to the route table.

AWS

resource "aws_internet_gateway" "igw" {
  vpc_id = [1]
}

resource "aws_route" "default_route" {
  route_table_id         = aws_route_table.rt.id
  destination_cidr_block = [2]
  gateway_id             = [3]
}

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

Aaws_vpc.main.id

B"0.0.0.0/0"

Caws_internet_gateway.igw.id

D"10.0.0.0/16"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong CIDR block for the route

Referencing the internet gateway ID incorrectly

The internet gateway must be attached to the VPC ID. The route destination for internet traffic is 0.0.0.0/0. The gateway ID in the route is the internet gateway's ID.

Practice

1. What is the main purpose of creating a custom VPC in AWS?

easy

A. To automatically create public IP addresses for all instances

B. To connect your AWS account to social media platforms

C. To enable AWS to manage your network without your input

D. To have a private network with a specific IP range for your resources

Solution

1. Step 1: Understand what a VPC is

   A VPC is a private network in AWS where you control IP ranges and network settings.

2. Step 2: Identify the purpose of a custom VPC

   Creating a custom VPC lets you choose your IP range and control network setup for your resources.

3. Final Answer:

   To have a private network with a specific IP range for your resources -> Option D

4. Quick Check:

   Custom VPC = Private network with chosen IP range [OK]

Hint: Custom VPC means your own private network in AWS [OK]

Common Mistakes:

• Thinking VPC automatically assigns public IPs
• Believing AWS manages the network without user control
• Confusing VPC with external internet connections

2. Which of the following is the correct way to specify the CIDR block when creating a custom VPC?

easy

A. 192.168.1.256/24

B. 255.255.255.0

C. 10.0.0.0/16

D. 10.0.0.0/33

Solution

1. Step 1: Understand CIDR notation

   CIDR block defines IP range with format like x.x.x.x/y where y is between 0 and 32.

2. Step 2: Check each option for validity

   10.0.0.0/16 is valid CIDR (10.0.0.0/16). 255.255.255.0 is a subnet mask, not CIDR. 192.168.1.256/24 has invalid IP (256). 10.0.0.0/33 has invalid prefix length (33).

3. Final Answer:

   10.0.0.0/16 -> Option C

4. Quick Check:

   CIDR block format = x.x.x.x/y with y ≤ 32 [OK]

Hint: CIDR uses / and prefix ≤ 32, IP parts ≤ 255 [OK]

Common Mistakes:

• Using subnet mask instead of CIDR
• Using invalid IP numbers like 256
• Using prefix length greater than 32

3. Given this AWS CLI command to create a VPC:

aws ec2 create-vpc --cidr-block 10.1.0.0/16 --tag-specifications 'ResourceType=vpc,Tags=[{Key=Name,Value=MyVPC}]'

What will be the result?

medium

A. A VPC with CIDR 10.1.0.0/16 and a Name tag 'MyVPC' will be created

B. The command will fail due to incorrect tag syntax

C. A VPC with default CIDR will be created ignoring the specified CIDR

D. A subnet will be created instead of a VPC

Solution

1. Step 1: Analyze the CLI command structure

   The command uses 'create-vpc' with a valid CIDR block and correct tag specification syntax.

2. Step 2: Understand the effect of the command

   This creates a VPC with the given CIDR and applies the Name tag 'MyVPC' to it.

3. Final Answer:

   A VPC with CIDR 10.1.0.0/16 and a Name tag 'MyVPC' will be created -> Option A

4. Quick Check:

   Valid CLI command creates VPC with CIDR and tags [OK]

Hint: Tags use 'ResourceType' and 'Tags' in CLI [OK]

Common Mistakes:

• Incorrect tag syntax causing command failure
• Confusing subnet creation with VPC creation
• Ignoring the CIDR block parameter

4. You created a custom VPC but forgot to enable DNS hostnames. What is the best way to fix this?

medium

A. Modify the VPC attribute to enable DNS hostnames using AWS console or CLI

B. Delete the VPC and create a new one with DNS hostnames enabled

C. Create a new subnet with DNS hostnames enabled

D. DNS hostnames cannot be enabled after VPC creation

Solution

1. Step 1: Understand DNS hostnames setting in VPC

   DNS hostnames is a VPC attribute that can be enabled or disabled after creation.

2. Step 2: Identify how to enable DNS hostnames

   You can modify the VPC attribute via AWS console or CLI without deleting the VPC.

3. Final Answer:

   Modify the VPC attribute to enable DNS hostnames using AWS console or CLI -> Option A

4. Quick Check:

   DNS hostnames can be enabled post-creation [OK]

Hint: VPC attributes can be changed anytime without deletion [OK]

Common Mistakes:

• Thinking you must delete and recreate the VPC
• Trying to enable DNS hostnames on a subnet instead of VPC
• Believing DNS hostnames are enabled by default always

5. You want to create a custom VPC with two public subnets in different availability zones and enable DNS support and hostnames. Which sequence of steps is correct?

hard

A. Attach internet gateway first, then create VPC and subnets, DNS settings are automatic

B. Create VPC with CIDR, enable DNS support and hostnames, create two public subnets in different AZs, attach internet gateway

C. Create VPC with CIDR, create subnets, attach internet gateway, then enable DNS support and hostnames

D. Create two subnets first, then create VPC, enable DNS hostnames, attach internet gateway

Solution

1. Step 1: Create the VPC with chosen CIDR block

   The VPC must exist before creating subnets or attaching gateways.

2. Step 2: Enable DNS support and hostnames on the VPC

   This ensures resources inside can resolve names properly.

3. Step 3: Create two public subnets in different availability zones

   Subnets must be inside the VPC and in separate AZs for high availability.

4. Step 4: Attach an internet gateway to allow internet access

   This makes the subnets public.

5. Final Answer:

   Create VPC with CIDR, enable DNS support and hostnames, create two public subnets in different AZs, attach internet gateway -> Option B

6. Quick Check:

   VPC -> DNS -> Subnets -> Internet Gateway [OK]

Hint: VPC first, then DNS settings, subnets, internet gateway [OK]

Common Mistakes:

• Creating subnets before the VPC exists
• Attaching internet gateway before VPC creation
• Assuming DNS settings are automatic