Template structure (JSON/YAML) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the AWS CloudFormation template version.

AWS

{
  "AWSTemplateFormatVersion": "[1]",
  "Resources": {}
}

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

A2010-09-09

B2020-01-01

C2005-12-15

D2015-07-30

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect date format.

Leaving the version field empty.

The correct AWS CloudFormation template version is 2010-09-09.

2fill in blank

medium

Complete the code to specify the description field in the AWS CloudFormation template.

AWS

{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Description": "[1]",
  "Resources": {}
}

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

ATemplate Metadata

BMy AWS CloudFormation Template

CResource Definitions

DAWS Template Version

Attempts:

3 left

💡 Hint

Common Mistakes

Using technical terms instead of a description.

Leaving the description empty.

The Description field should be a short text describing the template, such as My AWS CloudFormation Template.

3fill in blank

hard

Fix the error in the Resources section by completing the resource type.

AWS

{
  "Resources": {
    "MyBucket": {
      "Type": "[1]",
      "Properties": {
        "BucketName": "my-sample-bucket"
      }
    }
  }
}

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

AAWS::S3::Bucket

BAWS::Lambda::Function

CAWS::EC2::Instance

DAWS::DynamoDB::Table

Attempts:

3 left

💡 Hint

Common Mistakes

Using EC2 instance type for a bucket.

Using Lambda function type for a bucket.

The resource type for an S3 bucket is AWS::S3::Bucket.

4fill in blank

hard

Fill both blanks to define an EC2 instance with a specific instance type and AMI ID.

AWS

{
  "Resources": {
    "MyInstance": {
      "Type": "AWS::EC2::Instance",
      "Properties": {
        "InstanceType": "[1]",
        "ImageId": "[2]"
      }
    }
  }
}

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

At2.micro

Bami-0abcdef1234567890

Cm5.large

Dami-1234567890abcdef0

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing instance types and AMI IDs.

Using invalid AMI IDs.

The InstanceType is commonly t2.micro for small instances, and the ImageId is a valid AMI ID like ami-0abcdef1234567890.

5fill in blank

hard

Fill all three blanks to define an IAM role with assume role policy and managed policy ARN.

AWS

{
  "Resources": {
    "MyRole": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "AssumeRolePolicyDocument": [1],
        "Path": "[2]",
        "ManagedPolicyArns": ["[3]"]
      }
    }
  }
}

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

A{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": {"Service": "ec2.amazonaws.com"}, "Action": "sts:AssumeRole" }] }

B/

Carn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess

D{}

Attempts:

3 left

💡 Hint

Common Mistakes

Using empty or incorrect policy documents.

Wrong path format.

Incorrect or missing policy ARN.

The AssumeRolePolicyDocument must allow EC2 service to assume the role, the Path is usually "/", and the ManagedPolicyArns can include the AmazonS3ReadOnlyAccess policy ARN.

Practice

1. What is the main purpose of a cloud template written in JSON or YAML?

easy

A. To manually configure cloud resources one by one

B. To write application code for cloud functions

C. To monitor cloud resource usage in real-time

D. To describe and set up cloud resources automatically

Solution

1. Step 1: Understand what a cloud template does

   A cloud template is a file that describes cloud resources and how to create them automatically.

2. Step 2: Compare options with this purpose

   Only To describe and set up cloud resources automatically matches this description; others describe different tasks.

3. Final Answer:

   To describe and set up cloud resources automatically -> Option D

4. Quick Check:

   Cloud templates automate resource setup = D [OK]

Hint: Templates automate resource setup, not manual or monitoring tasks [OK]

Common Mistakes:

• Confusing templates with monitoring tools
• Thinking templates are for writing application code
• Assuming templates require manual resource setup

2. Which of the following is the correct top-level section name in an AWS CloudFormation JSON template?

easy

A. Resources

B. Scripts

C. Functions

D. Commands

Solution

1. Step 1: Recall AWS CloudFormation template structure

   The main sections include Parameters, Resources, Outputs, etc. 'Resources' defines the cloud resources.

2. Step 2: Identify valid section names

   Only 'Resources' is a valid top-level section; others are not used in CloudFormation templates.

3. Final Answer:

   Resources -> Option A

4. Quick Check:

   Resources section defines cloud resources = C [OK]

Hint: Remember: Resources section always defines cloud items [OK]

Common Mistakes:

• Using non-existent sections like Scripts or Commands
• Confusing function code with template sections
• Mixing up template sections with programming terms

3. Given this snippet of a CloudFormation JSON template:

{
  "Resources": {
    "MyBucket": {
      "Type": "AWS::S3::Bucket"
    }
  }
}

What resource will this template create?

medium

A. An EC2 virtual server

B. An S3 storage bucket

C. A Lambda function

D. A VPC network

Solution

1. Step 1: Read the resource type in the template

   The resource type is "AWS::S3::Bucket", which means an S3 storage bucket.

2. Step 2: Match resource type to options

   Only An S3 storage bucket matches the S3 bucket resource type.

3. Final Answer:

   An S3 storage bucket -> Option B

4. Quick Check:

   "AWS::S3::Bucket" means S3 bucket = B [OK]

Hint: Look for "Type" value to identify resource created [OK]

Common Mistakes:

• Confusing S3 bucket with EC2 or Lambda
• Ignoring the resource type string
• Assuming resource names define type

4. You wrote this YAML snippet for a CloudFormation template but it fails to deploy:

Resources:
  MyInstance:
    Type: AWS::EC2::Instance
    Properties:
      ImageId: ami-12345678
      InstanceType: t2.micro
      SecurityGroups: my-security-group

What is the likely error?

medium

A. InstanceType is invalid for EC2

B. ImageId must be a number, not a string

C. SecurityGroups should be a list, not a single string

D. Resources section name is misspelled

Solution

1. Step 1: Check the SecurityGroups property format

   SecurityGroups expects a list of strings, but here it is a single string.

2. Step 2: Validate other properties

   ImageId is a string (correct), InstanceType is valid, Resources is spelled correctly.

3. Final Answer:

   SecurityGroups should be a list, not a single string -> Option C

4. Quick Check:

   SecurityGroups needs list format = A [OK]

Hint: Lists must be in brackets or dash format in YAML [OK]

Common Mistakes:

• Using string instead of list for SecurityGroups
• Assuming ImageId is numeric
• Misspelling Resources section

5. You want to create a reusable CloudFormation template that accepts a bucket name as input and outputs the bucket ARN. Which two sections must you include in your JSON template?

hard

A. Parameters and Outputs

B. Resources and Scripts

C. Functions and Parameters

D. Outputs and Commands

Solution

1. Step 1: Identify input and output sections needed

   To accept input like bucket name, use Parameters. To show output like ARN, use Outputs.

2. Step 2: Confirm other sections are invalid

   Scripts, Functions, Commands are not valid top-level sections in CloudFormation templates.

3. Final Answer:

   Parameters and Outputs -> Option A

4. Quick Check:

   Input = Parameters, Output = Outputs [OK]

Hint: Parameters take inputs; Outputs show results [OK]

Common Mistakes:

• Using non-existent sections like Scripts or Commands
• Confusing Resources with input/output sections
• Forgetting to include Outputs for results