CloudFormation Physical and Logical Resources

Question 1

The “What” in a CloudFormation Template

Answer 1

Logical Resources

Question 2

What CloudFormation templates are used to create

Answer 2

Stacks

Question 3

Creates physical resources from the logical resources which can be updated or deleted

Answer 3

Stacks

Question 4

If you delete a stack are the logical resources deleted?

Answer 4

Yes

Question 5

If the logical resources are deleted in a CloudFormation Stack and the physical resources deleted?

Answer 5

Yes

Question 6

Parameters that accept input from console/cli/api when a stack is created or updated

Answer 6

Template Parameters

Question 7

Parameters that are made by AWS based on the environment when creating the stack which can be referenced

Answer 7

Pseudo Parameters

Question 8

Function which allows you to reference a value from one logical resource or parameter in another one

Answer 8

!Ref & Fn::GetAtt

Question 9

Function which allows you to join strings together or split them

Answer 9

Fn::Join & Fn::Split

Question 10

Function which can be used to get a list of availability zones for a given AWS region

Answer 10

FN::GetAZs

Question 11

Function which allows you to select one element from list of Availible AZs

Answer 11

Fn::Select

Question 12

Function used to provision resources based on conditional checks

Answer 12

Fn:: IF, And, Equals, Not, Or

Question 13

Function used to accept non-encoded text and outputs base64 encoded text that can be provided to the resource

Answer 13

Fn::Base64

Question 14

Function that allows you to substitute things within text based on runtime information

Answer 14

Fn::Sub

Question 15

Function used to automatically configure the network ranges subnets use within a ClouDFormation template

Answer 15

Fn:Cidr

Question 16

Function used to retrieve any attribute associated with the resource

Answer 16

!GetAtt

Question 17

Object within a template which maps keys to values allowing lookup

Answer 17

CloudFormation Mappings

Question 18

Function which are used to retrieve a given amazon machine image ID

Answer 18

!FindInMap

Question 19

declares output values that you can import into other stacks, return in response, or view on the AWS CloudFormation Console

Answer 19

Outputs

Question 20

statements that define the circumstances under which entities are created or configured, evaluated based on predefined pseudo parameters or input parameter values that you specify when you create or update a stack

Answer 20

Conditions

Question 21

attribute you can specify that the creation of a specific resource follows another and ensure that the resource is created only after the creation of the resource specified

Answer 21

DependsOn

Question 22

can be used together to prevent the status if a resource from reaching create complete until AWS CloudFormation receives a specified number of success signals or the timeout period is exceeded

Answer 22

CreationPolicy, WaitConditions and cfn-signal

Question 23

stacks that allow for a hierarchy of related templates to be combined to form a single product used to overcome the resource limit of one stack when everything created is lifecycle linked

Answer 23

Nested Stack

Question 24

stacks that create modular templates which allow code to be reused

Answer 24

Nested Stack

Question 25

Allow one stack to reference another. Outputs in one stack reference logical resources or attributes in that stack can be used in another stack

Answer 25

Cross stack references

Question 26

Can be used to reference exported values from one stack into another stack

Answer 26

!ImportValue

Question 27

Feature of CloudFormation allowing infrastructure to be deployed and managed across multiple regions and multiple accounts from a single location

Answer 27

StackSets

Question 28

Reference to stacks running in specific regions in specific AWS accounts (Container for an individual stack)

Answer 28

Stack Instances

Question 29

Accounts that stack sets target to deploy resources into

Answer 29

Target Accounts

Question 30

Defines how many individual AWS accounts stacks are being deployed into at one time (If you have 10 accounts and set the value to 2, then 2 deployments will happen to 2 accounts 5 times)

Answer 30

Concurrent accounts

Question 31

Defines the amount of individual deployments that can fail before the stack set is viewed as failed

Answer 31

Failure Tolerance

Question 32

Allows you to remove stack instances or stacks from a target account by default when deleting stack instances stacks are deleted but can be toggled to be retained

Answer 32

Retain Stacks

Question 33

attribute you can preserve or (in some cases) backup each resource when its stack is deleted

Answer 33

Deletion Policy

Question 34

Allows an IAM role to be passed into the stack via PassRole, A stack uses this role, rather than the identity interacting with the stack to create, update and delete AWS resources

Answer 34

Stack Role

Question 35

Tools which allow a desired state configuration management system to be implemented within CloudFormation that are stored within templates

Answer 35

CloudFormationInit

Question 36

helper tool that detects changes in resource metadata and runs user-specified actions when a change is detected

Answer 36

cfn-hup helper

Question 37

allow you to preview how proposed changes to a stack might impact your running resources, for example, whether your changes will delete or replace any critical resources

Answer 37

ChangeSets

Question 38

enable you to write custom provisioning logic in templates that AWS CloudFormation runs anytime you create, update (if you changed the custom resource), or delete stacks

Answer 38

Custom Resources