AWS global infrastructure (regions, AZs) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS region for deployment.

AWS

provider "aws" {
  region = "[1]"
}

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

Aus-east-1

Beurope-west1

Casia-south1

Dus-central

Attempts:

3 left

💡 Hint

Common Mistakes

Using region codes from other cloud providers.

Using incomplete or incorrect region codes.

The correct AWS region code for US East (N. Virginia) is us-east-1. Other options are not valid AWS region codes.

2fill in blank

medium

Complete the code to select an Availability Zone in the us-east-1 region.

AWS

resource "aws_instance" "example" {
  availability_zone = "us-east-1[1]"
  ami               = "ami-0c94855ba95c71c99"
  instance_type     = "t2.micro"
}

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

Aa

Bz1

Cb

Dc

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid AZ suffixes like 'z1'.

Confusing AZ names with region codes.

Availability Zones in AWS regions are labeled with letters like 'a', 'b', 'c'. Here, 'us-east-1b' is a valid AZ.

3fill in blank

hard

Fix the error in the code to correctly reference an Availability Zone in the eu-west-1 region.

AWS

resource "aws_subnet" "example" {
  vpc_id            = "vpc-123456"
  cidr_block        = "10.0.1.0/24"
  availability_zone = "eu-west-1[1]"
}

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

Aa

Bzone1

C1a

Dwest-1a

Attempts:

3 left

💡 Hint

Common Mistakes

Adding numbers or extra words in AZ suffix.

Using incorrect region codes.

The correct AZ suffix is a single letter like 'a'. 'eu-west-1a' is valid, while '1a' or 'west-1a' are incorrect.

4fill in blank

hard

Fill both blanks to create a subnet in the us-west-2 region and specify its Availability Zone.

AWS

resource "aws_subnet" "example" {
  vpc_id            = "vpc-789012"
  cidr_block        = "10.0.2.0/24"
  availability_zone = "[1][2]"
}

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

Aus-west-2

Bus-east-1

Ca

Db

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing region codes and AZ suffixes incorrectly.

Using invalid region or AZ values.

The subnet's Availability Zone must be in the correct region and use a valid AZ suffix. 'us-west-2a' is valid.

5fill in blank

hard

Fill all three blanks to define an EC2 instance in the ap-southeast-1 region, in Availability Zone 'b', with instance type 't3.micro'.

AWS

resource "aws_instance" "example" {
  ami               = "ami-0abcdef1234567890"
  instance_type     = "[1]"
  availability_zone = "[2][3]"
}

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

At3.micro

Bap-southeast-1

Cb

Dus-east-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong instance types.

Mixing up region and AZ suffix order.

Using invalid AZ suffixes.

The instance type is 't3.micro'. The region is 'ap-southeast-1' and the AZ suffix is 'b', so the availability zone is 'ap-southeast-1b'.