CloudFormation

Question 1

What is CloudFormation

Answer 1

A declarative way of outlining your AWS Infrastructure, for any resources. (Most are supported)

Question 2

What does CloudFormation do?

Answer 2

Eliminates the need for manual configuration, as everything is provisioned automatically through templates.

Question 3

How can you reference a template in CloudFormation?

Answer 3

After uploading a template in S3.

Question 4

How is a template edited?

Answer 4

It’s not. Re-upload a new version of the template.

Question 5

What is deleted along with a stack?

Answer 5

Every single artifact that was created by CloudFormation.

Question 6

Two ways to deploy CloudFormation templates?

Answer 6

1. Manual
2. Automated

Question 7

Features:
- Editing templates in CloudFormation Designer or code editor
- Using the console to input parameters, etc…

Answer 7

Manual deployment

Question 8

Features:
- Editing templates in a YAML file
- Using the AWS CLI (Command Line Interface) to deploy the templates, or using a Continuous Delivery (CD) tool

Answer 8

Automated deployment

Question 9

What is the core of your CloudFormation template?

Answer 9

Resources

Question 10

What are “Resources”?

Answer 10

Different AWS Components that will be created and configured.

Question 11

Resources are….. and can…… each other.

Answer 11

declared, reference

Question 12

How are resources created, updated, and deleted?

Answer 12

AWS does it.

Question 13

What do “Parameters” do?

Answer 13

Provides inputs to AWS CloudFormation template.

Question 14

Features:
- You want to reuse your templates across the company
- Some inputs can not be determined ahead of time

Answer 14

Parameteres

Question 15

How can parameters help prevents errors in a template?

Answer 15

Types

Question 16

What should a “parameter” be used?

Answer 16

When a resource configuration is likely to change.

Question 17

What are “Mappings”?

Answer 17

Fixed variables within your CloudFormation template.

Question 18

When should “mappings” be used?

Answer 18

When you know in advance all the values that can be taken.

Question 19

When should “parameters” be used?

Answer 19

When the values are really user specific.

Question 20

What are “Outputs”?

Answer 20

Declares optional outputs values that we can import into other stacks

Question 21

What are “Conditions”?

Answer 21

They control the creation of resources or outputs based on a condition.

Question 22

Each condition can reference..

Answer 22

Other condition, parameter value or mapping.

Question 23

Different types of “Rollbacks”?

Answer 23

1. Stack Creation Fails
2. Stack Update Fails

Question 24

What is a CloudFormation “Serve Role”?

Answer 24

IAM roles that allows CloudFormation create/update/delete stack resources.

Question 25

How can you give users CRUD abilities to the stack resource even if they don’t have permissions?

Answer 25

Service role

Question 26

What is “Deletion Policy”?

Answer 26

Allows control of what happens when the CloudFormation template is deleted/ resource is removed.

Question 27

What is an extra safety measure to preserve and backup resource?

Answer 27

Deletion policy

Question 28

Delete won’t work on an S3 bucket if the bucket is not empty?

Answer 28

True

Question 29

What is a “Stack Policy”?

Answer 29

A JSON document that defines the update actions that are allowed on specific resources during Stack updates.

Question 30

What are all resources in a Stack protected by default?

Answer 30

What a Stack Policy is set.