Launch templates in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a launch template with a name.

AWS

aws ec2 create-launch-template --launch-template-name [1] --version-description "v1" --launch-template-data file://template.json

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

Atemplate123

BMyLaunchTemplate

CLaunchTemplate1

DTestTemplate

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces in the launch template name

Leaving the name empty

The --launch-template-name parameter requires a unique name. "template123" is a valid example.

2fill in blank

medium

Complete the code to specify the AMI ID in the launch template data.

AWS

{
  "ImageId": "[1]",
  "InstanceType": "t2.micro"
}

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

Aami-xyz789

Bami-12345

Cami-0abcdef1234567890

Dimage-123456

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid AMI ID formats

Using placeholder text instead of real AMI IDs

The ImageId must be a valid AMI ID format like "ami-0abcdef1234567890".

3fill in blank

hard

Fix the error in the launch template data to correctly specify the instance type.

AWS

{
  "ImageId": "ami-0abcdef1234567890",
  "InstanceType": "[1]"
}

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

At2.micro

Bmicro.t2

Ct2_micro

Dt2micro

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores or missing dots in instance type

Swapping family and size order

The correct instance type format is like "t2.micro" with a dot separating family and size.

4fill in blank

hard

Fill both blanks to specify the key name and security group IDs in the launch template data.

AWS

{
  "KeyName": "[1]",
  "SecurityGroupIds": ["[2]"]
}

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

AMyKeyPair

Bdefault

Csg-0a1b2c3d4e5f6g7h8

Dsg-12345678

Attempts:

3 left

💡 Hint

Common Mistakes

Using security group names instead of IDs

Using invalid key pair names

The KeyName should be your SSH key pair name, and SecurityGroupIds must be valid security group IDs like "sg-0a1b2c3d4e5f6g7h8".

5fill in blank

hard

Fill all three blanks to create a launch template data snippet with user data, tag specifications, and block device mappings.

AWS

{
  "UserData": "[1]",
  "TagSpecifications": [{"ResourceType": "instance", "Tags": [{"Key": "Name", "Value": "[2]"}]}],
  "BlockDeviceMappings": [{"DeviceName": "/dev/xvda", "Ebs": {"VolumeSize": [3]]
}

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

AIyEvYmluL2Jhc2gKZWNobyAiSGVsbG8gV29ybGQiID4gL2hvbWUvZXMvdXNlci9pbmRleC50eHQ=

BMyInstance

C30

DHelloWorld

Attempts:

3 left

💡 Hint

Common Mistakes

Using plain text instead of base64 for user data

Incorrect volume size types

Missing tag keys or values

UserData must be base64 encoded script, TagSpecifications include the instance name, and BlockDeviceMappings specify the volume size in GB.

Practice

1. What is the main purpose of an AWS Launch Template?

easy

A. To automatically back up EC2 instance data

B. To monitor running EC2 instances in real-time

C. To store configuration settings for launching EC2 instances consistently

D. To manage user permissions for EC2 instances

Solution

1. Step 1: Understand Launch Template role

   Launch templates save settings like instance type, AMI, and security groups for EC2 instances.

2. Step 2: Identify main purpose

   This helps launch instances with consistent configurations quickly and easily.

3. Final Answer:

   To store configuration settings for launching EC2 instances consistently -> Option C

4. Quick Check:

   Launch Template = Configuration storage [OK]

Hint: Launch templates save instance settings for reuse [OK]

Common Mistakes:

• Confusing launch templates with monitoring tools
• Thinking launch templates handle backups
• Assuming launch templates manage permissions

2. Which of the following is the correct way to specify a launch template version in an AWS CLI command to run an EC2 instance?

easy

A. aws ec2 run-instances --launch-template LaunchTemplateId=lt-12345678,Version=2

B. aws ec2 run-instances --template-id lt-12345678 --version 2

C. aws ec2 run-instances --launch-template-id lt-12345678 --template-version 2

D. aws ec2 run-instances --launch-template lt-12345678 version=2

Solution

1. Step 1: Recall AWS CLI syntax for launch templates

   The correct syntax uses --launch-template with parameters LaunchTemplateId and Version separated by commas.

2. Step 2: Match syntax to options

   aws ec2 run-instances --launch-template LaunchTemplateId=lt-12345678,Version=2 matches the correct syntax exactly.

3. Final Answer:

   aws ec2 run-instances --launch-template LaunchTemplateId=lt-12345678,Version=2 -> Option A

4. Quick Check:

   Correct CLI syntax = aws ec2 run-instances --launch-template LaunchTemplateId=lt-12345678,Version=2 [OK]

Hint: Use --launch-template LaunchTemplateId=ID,Version=NUM [OK]

Common Mistakes:

• Using incorrect parameter names like --template-id
• Separating parameters with spaces instead of commas
• Omitting the 'Version=' keyword

3. Given this launch template version history:
Version 1: AMI ami-11111111, InstanceType t2.micro
Version 2: AMI ami-22222222, InstanceType t2.small
If you launch an instance specifying version 1, what will be the instance type?

medium

A. t2.small

B. t2.micro

C. t2.medium

D. The latest version's instance type

Solution

1. Step 1: Identify version specified in launch

   The question says version 1 is specified for launching the instance.

2. Step 2: Check instance type in version 1

   Version 1 has instance type t2.micro, so that will be used.

3. Final Answer:

   t2.micro -> Option B

4. Quick Check:

   Specified version settings apply = t2.micro [OK]

Hint: Specified version settings override latest [OK]

Common Mistakes:

• Assuming latest version is always used
• Confusing AMI with instance type
• Ignoring version number in launch command

4. You tried to launch an EC2 instance using a launch template but got an error: "Invalid launch template version specified." What is the most likely cause?

medium

A. The launch template ID is incorrect

B. The instance type is not supported in the region

C. The AMI in the launch template is deprecated

D. The specified version number does not exist in the launch template

Solution

1. Step 1: Analyze error message

   The error says "Invalid launch template version specified," indicating a problem with the version number.

2. Step 2: Identify cause

   This usually means the version number given does not exist or is mistyped.

3. Final Answer:

   The specified version number does not exist in the launch template -> Option D

4. Quick Check:

   Error about version = wrong version number [OK]

Hint: Check version number exists in template [OK]

Common Mistakes:

• Assuming AMI or instance type causes version error
• Not verifying launch template ID correctness
• Ignoring error details about version

5. You want to update a launch template to change the instance type but keep the original version intact for rollback. What is the best practice to achieve this?

hard

A. Create a new version of the existing launch template with the updated instance type

B. Modify the existing launch template version directly

C. Create a new launch template with the updated instance type

D. Delete the old launch template and create a new one with the updated instance type

Solution

1. Step 1: Understand launch template versioning

   Launch templates support multiple versions to track changes safely without overwriting.

2. Step 2: Choose update method preserving old version

   Creating a new version keeps the old version intact for rollback if needed.

3. Final Answer:

   Create a new version of the existing launch template with the updated instance type -> Option A

4. Quick Check:

   Use versioning to update safely = Create a new version of the existing launch template with the updated instance type [OK]

Hint: Use new version to update, keep old for rollback [OK]

Common Mistakes:

• Modifying existing version directly (not allowed)
• Deleting old template loses rollback option
• Creating new template duplicates effort unnecessarily