CloudFormation vs Terraform awareness in AWS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the infrastructure as code tool used in AWS native templates.

AWS

The AWS native infrastructure as code tool is called [1].

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

AAnsible

BChef

CCloudFormation

DTerraform

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Terraform as the native AWS tool.

Mixing configuration management tools like Ansible or Chef.

AWS CloudFormation is the native infrastructure as code service provided by AWS to define and provision resources.

2fill in blank

medium

Complete the code to identify the tool that supports multiple cloud providers.

AWS

The tool that supports provisioning infrastructure across AWS, Azure, and Google Cloud is [1].

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

ACloudFormation

BServerless Framework

CAWS CDK

DTerraform

Attempts:

3 left

💡 Hint

Common Mistakes

Assuming CloudFormation supports multiple clouds.

Confusing AWS CDK with Terraform.

Terraform is a multi-cloud infrastructure as code tool that supports many cloud providers.

3fill in blank

hard

Fix the error in the statement about state management in infrastructure as code tools.

AWS

Terraform manages infrastructure state using a state file, while CloudFormation manages state [1].

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

Alocal

Binternally

Cremote

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking CloudFormation uses a state file like Terraform.

Confusing local and remote state concepts.

CloudFormation manages state internally within AWS, while Terraform uses a state file that can be local or remote.

4fill in blank

hard

Fill both blanks to complete the sentence about template languages and resource provisioning.

AWS

CloudFormation templates are written in [1] or [2], while Terraform uses its own language called HCL.

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

AJSON

BYAML

CXML

DPython

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking CloudFormation supports XML or Python as template languages.

Confusing Terraform language with CloudFormation templates.

CloudFormation supports JSON and YAML template formats for defining infrastructure.

5fill in blank

hard

Fill all three blanks to complete the sentence about tool integration and usage.

AWS

Terraform uses [1] files to define infrastructure, supports [2] backends for state storage, and can be integrated with [3] for automation.

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

A.tf

Bremote

CCI/CD pipelines

DCloudFormation

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing CloudFormation with Terraform file types.

Not knowing about remote state backends.

Ignoring automation integration possibilities.

Terraform uses .tf files, supports remote backends for state, and integrates with CI/CD pipelines for automation.

Practice

1. Which statement best describes the main difference between AWS CloudFormation and Terraform?

easy

A. CloudFormation works only with AWS, while Terraform supports multiple cloud providers.

B. Terraform is only for AWS, CloudFormation supports all clouds.

C. Both tools only work with AWS services.

D. CloudFormation supports multiple clouds, Terraform is AWS-only.

Solution

1. Step 1: Understand CloudFormation scope

   CloudFormation is designed specifically for AWS and manages AWS resources only.

2. Step 2: Understand Terraform scope

   Terraform supports many cloud providers like AWS, Azure, Google Cloud, and more.

3. Final Answer:

   CloudFormation works only with AWS, while Terraform supports multiple cloud providers. -> Option A

4. Quick Check:

   CloudFormation = AWS-only, Terraform = multi-cloud [OK]

Hint: CloudFormation = AWS-only; Terraform = many clouds [OK]

Common Mistakes:

• Thinking Terraform only works with AWS
• Believing CloudFormation supports multiple clouds
• Confusing both as identical tools

2. Which of the following is the correct way to define a resource in AWS CloudFormation?

easy

A. resource "aws_ec2_instance" "web" {}

B. resource "aws_instance" "web" {}

C. AWS::EC2::Instance:

D. resource "ec2_instance" "web" {}

Solution

1. Step 1: Identify CloudFormation syntax

   CloudFormation uses YAML or JSON with resource types like 'AWS::EC2::Instance'.

2. Step 2: Recognize Terraform syntax

   Terraform uses 'resource "aws_instance" "name" {}'.

3. Final Answer:

   CloudFormation resource types use 'AWS::Service::Resource' format. -> Option C

4. Quick Check:

   CloudFormation uses AWS:: notation [OK]

Hint: CloudFormation uses AWS::Service::Resource format [OK]

Common Mistakes:

• Confusing Terraform resource syntax with CloudFormation
• Using Terraform resource blocks in CloudFormation
• Misnaming resource types

3. Given this Terraform snippet:

resource "aws_s3_bucket" "bucket" {
  bucket = "my-unique-bucket"
  acl    = "private"
}

What will happen when you run terraform apply?

medium

A. Creates a public S3 bucket named 'my-unique-bucket' in AWS.

B. Fails because bucket names cannot be unique.

C. Throws a syntax error due to missing region.

D. Creates a private S3 bucket named 'my-unique-bucket' in AWS.

Solution

1. Step 1: Analyze Terraform resource block

   The resource defines an AWS S3 bucket with name 'my-unique-bucket' and ACL set to 'private'.

2. Step 2: Understand Terraform apply behavior

   Terraform will create the bucket with the specified name and private access control.

3. Final Answer:

   Creates a private S3 bucket named 'my-unique-bucket' in AWS. -> Option D

4. Quick Check:

   ACL 'private' means private bucket [OK]

Hint: ACL 'private' means bucket is private [OK]

Common Mistakes:

• Assuming default ACL is public
• Expecting syntax error without region (region is set elsewhere)
• Thinking bucket names cannot be unique (they must be unique)

4. You wrote this CloudFormation snippet:

Resources:
  MyBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: my-bucket
      AccessControl: PublicRead

But deployment fails with an error about bucket name. What is the likely cause?

medium

A. BucketName must be globally unique and 'my-bucket' is already taken.

B. AccessControl property is invalid in CloudFormation.

C. Resource type AWS::S3::Bucket is incorrect.

D. BucketName cannot be specified in CloudFormation.

Solution

1. Step 1: Understand S3 bucket naming rules

   S3 bucket names must be globally unique across all AWS accounts.

2. Step 2: Analyze error cause

   If 'my-bucket' is already used, deployment fails due to name conflict.

3. Final Answer:

   BucketName must be globally unique and 'my-bucket' is already taken. -> Option A

4. Quick Check:

   S3 bucket names are global and unique [OK]

Hint: S3 bucket names must be globally unique [OK]

Common Mistakes:

• Thinking AccessControl is invalid (it is valid)
• Assuming resource type is wrong
• Believing BucketName is optional or disallowed

5. Your team wants to manage infrastructure across AWS, Azure, and Google Cloud with one tool. Which approach is best?

hard

A. Use AWS CloudFormation for all clouds to keep consistency.

B. Use Terraform because it supports multiple cloud providers.

C. Use separate CloudFormation stacks for each cloud provider.

D. Use manual console setup for each cloud to avoid tool complexity.

Solution

1. Step 1: Identify tool cloud support

   CloudFormation only supports AWS, so it cannot manage Azure or Google Cloud.

2. Step 2: Choose tool for multi-cloud management

   Terraform supports AWS, Azure, Google Cloud, and others in one tool.

3. Step 3: Evaluate other options

   Separate CloudFormation stacks or manual setup increase complexity and reduce automation benefits.

4. Final Answer:

   Use Terraform because it supports multiple cloud providers. -> Option B

5. Quick Check:

   Terraform = multi-cloud support [OK]

Hint: Terraform supports many clouds; CloudFormation is AWS-only [OK]

Common Mistakes:

• Assuming CloudFormation works outside AWS
• Thinking manual setup is simpler for multi-cloud
• Believing separate CloudFormation stacks can manage non-AWS clouds