Parameters for customization in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a parameter in AWS CloudFormation template.

AWS

"Parameters": {
  "InstanceType": {
    "Type": "[1]"
  }
}

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

AString

BNumber

CList

DBoolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using Number type for instance type which is text.

Using List type when only a single value is needed.

The Type of a parameter defines the kind of value it accepts. String is the most common type for instance types.

2fill in blank

medium

Complete the code to set a default value for a parameter in AWS CloudFormation.

AWS

"Parameters": {
  "InstanceType": {
    "Type": "String",
    "Default": "[1]"
  }
}

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

Ac5.xlarge

Bt2.micro

Cm5.large

Dt2.large

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing an instance type that is too large or uncommon as default.

Leaving the default value empty.

The Default value sets the parameter's value if no other value is provided. t2.micro is a common default instance type.

3fill in blank

hard

Fix the error in the parameter definition to allow only specific instance types.

AWS

"Parameters": {
  "InstanceType": {
    "Type": "String",
    "AllowedValues": [1]
  }
}

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

A["t2.micro", "t2.small", "t2.medium"]

B"t2.micro, t2.small, t2.medium"

C{"t2.micro", "t2.small", "t2.medium"}

Dt2.micro, t2.small, t2.medium

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a list for AllowedValues.

Using curly braces instead of square brackets.

The AllowedValues property must be a JSON array of strings listing valid values.

4fill in blank

hard

Fill both blanks to define a parameter with a description and a constraint on allowed values.

AWS

"Parameters": {
  "EnvironmentType": {
    "Type": "String",
    "Description": "[1]",
    "AllowedValues": [2]
  }
}

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

AType of environment (dev, test, prod)

BList of environments

C["dev", "test", "prod"]

D["development", "testing", "production"]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a vague or missing description.

Using incorrect format for AllowedValues.

The Description explains the parameter's purpose. AllowedValues restricts the input to listed options.

5fill in blank

hard

Fill all three blanks to define a parameter with a default, description, and allowed values.

AWS

"Parameters": {
  "KeyName": {
    "Type": "String",
    "Description": "[1]",
    "Default": "[2]",
    "AllowedValues": [3]
  }
}

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

AName of an existing EC2 KeyPair to enable SSH access

Bmy-key-pair

C["my-key-pair", "default-key", "admin-key"]

DList of key pairs

Attempts:

3 left

💡 Hint

Common Mistakes

Default value not included in AllowedValues.

Description missing or unclear.

The Description explains the parameter. Default sets a fallback value. AllowedValues restricts to valid key pair names.

Practice

1. What is the main purpose of using Parameters in AWS CloudFormation templates?

easy

A. To monitor cloud resource usage

B. To store large files in the cloud

C. To customize the template without changing its code

D. To create new AWS services automatically

Solution

1. Step 1: Understand the role of Parameters

   Parameters allow users to input values when launching a template, so the same template can be reused with different settings.

2. Step 2: Compare options with Parameters purpose

   Only To customize the template without changing its code describes customization without changing the template code, which is the key use of Parameters.

3. Final Answer:

   To customize the template without changing its code -> Option C

4. Quick Check:

   Parameters = Customize without code change [OK]

Hint: Parameters let you change settings without editing code [OK]

Common Mistakes:

• Thinking Parameters create resources automatically
• Confusing Parameters with monitoring tools
• Assuming Parameters store files

2. Which of the following is the correct syntax to define a string parameter named InstanceType with a default value of t2.micro in a CloudFormation template?

easy

A. "InstanceType": {"Default": "t2.micro"}

B. "InstanceType": {"Type": "Number", "Default": "t2.micro"}

C. "InstanceType": {"Type": "String", "Value": "t2.micro"}

D. "InstanceType": {"Type": "String", "Default": "t2.micro"}

Solution

1. Step 1: Identify correct parameter syntax

   Parameters require a Type and optionally a Default. The Type for instance types is String, and Default sets the default value.

2. Step 2: Check each option

   "InstanceType": {"Type": "String", "Default": "t2.micro"} correctly uses "Type": "String" and "Default": "t2.micro". "InstanceType": {"Type": "Number", "Default": "t2.micro"} wrongly uses Number type. "InstanceType": {"Type": "String", "Value": "t2.micro"} uses "Value" which is invalid. "InstanceType": {"Default": "t2.micro"} misses the Type field.

3. Final Answer:

   "InstanceType": {"Type": "String", "Default": "t2.micro"} -> Option D

4. Quick Check:

   Parameter syntax needs Type and Default [OK]

Hint: Parameters need Type and Default keys for customization [OK]

Common Mistakes:

• Using 'Value' instead of 'Default'
• Setting wrong Type like Number for strings
• Omitting the Type field

3. Given this parameter definition in a CloudFormation template:

"Parameters": {
  "EnvType": {
    "Type": "String",
    "AllowedValues": ["dev", "test", "prod"],
    "Default": "dev"
  }
}

What happens if a user tries to launch the stack with EnvType set to stage?

medium

A. The stack uses the default value 'dev' instead

B. The stack creation fails due to invalid parameter value

C. The stack accepts 'stage' and creates resources

D. The stack ignores the parameter and prompts again

Solution

1. Step 1: Understand AllowedValues effect

   The AllowedValues list restricts parameter inputs to only those values. Any value outside causes an error.

2. Step 2: Analyze input 'stage'

   'stage' is not in ["dev", "test", "prod"], so the stack creation will fail with a validation error.

3. Final Answer:

   The stack creation fails due to invalid parameter value -> Option B

4. Quick Check:

   AllowedValues restrict inputs = failure if invalid [OK]

Hint: AllowedValues block invalid inputs causing stack failure [OK]

Common Mistakes:

• Assuming default is used when invalid input given
• Thinking stack ignores invalid parameters
• Believing stack accepts any string

4. You have this parameter snippet:

"Parameters": {
  "DBPassword": {
    "Type": "String",
    "NoEcho": true
  }
}

What is the purpose of NoEcho here, and what common mistake might cause it to fail?

medium

A. NoEcho hides the parameter value in console; mistake is forgetting to set Type

B. NoEcho encrypts the value; mistake is using wrong parameter name

C. NoEcho hides the value in logs; mistake is setting NoEcho to false

D. NoEcho makes parameter optional; mistake is missing Default

Solution

1. Step 1: Understand NoEcho purpose

   NoEcho hides sensitive parameter values (like passwords) from being displayed in the AWS console or logs.

2. Step 2: Identify common mistake

   For NoEcho to work, the parameter must have a Type defined. Forgetting Type causes template errors.

3. Final Answer:

   NoEcho hides the parameter value in console; mistake is forgetting to set Type -> Option A

4. Quick Check:

   NoEcho hides sensitive info; Type is required [OK]

Hint: NoEcho hides secrets; always define Type [OK]

Common Mistakes:

• Not defining Type with NoEcho
• Assuming NoEcho encrypts data
• Setting NoEcho false expecting hiding

5. You want to create a CloudFormation template that asks for a list of availability zones but only allows zones in us-east-1. Which parameter configuration correctly enforces this restriction and allows multiple zones?

hard

A. "Parameters": { "AZList": { "Type": "List", "AllowedValues": ["us-east-1a", "us-east-1b", "us-east-1c"] } }

B. "Parameters": { "AZList": { "Type": "CommaDelimitedList" } }

C. "Parameters": { "AZList": { "Type": "List<String>", "Default": "us-east-1a,us-east-1b" } }

D. "Parameters": { "AZList": { "Type": "String", "AllowedValues": ["us-east-1a", "us-east-1b", "us-east-1c"] } }

Solution

1. Step 1: Identify parameter type for multiple AZs

   To accept multiple availability zones, use the type List with AWS::EC2::AvailabilityZone::Name for validation.

2. Step 2: Check AllowedValues for region restriction

   AllowedValues limits input to only the specified zones in us-east-1.

3. Step 3: Evaluate options

   "Parameters": { "AZList": { "Type": "List", "AllowedValues": ["us-east-1a", "us-east-1b", "us-east-1c"] } } uses correct List type and AllowedValues. "Parameters": { "AZList": { "Type": "CommaDelimitedList" } } uses CommaDelimitedList but lacks AllowedValues restriction. "Parameters": { "AZList": { "Type": "List<String>", "Default": "us-east-1a,us-east-1b" } } lacks AllowedValues restriction. "Parameters": { "AZList": { "Type": "String", "AllowedValues": ["us-east-1a", "us-east-1b", "us-east-1c"] } } uses String type which accepts only one value.

4. Final Answer:

   "Parameters": { "AZList": { "Type": "List", "AllowedValues": ["us-east-1a", "us-east-1b", "us-east-1c"] } } -> Option A

5. Quick Check:

   List type + AllowedValues restrict multiple inputs [OK]

Hint: Use List type with AllowedValues for multiple restricted inputs [OK]

Common Mistakes:

• Using String type for multiple values
• Using CommaDelimitedList without proper validation
• Not restricting AllowedValues to region zones