Cooldown periods in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a cooldown period of 300 seconds for an Auto Scaling group.

AWS

AutoScalingGroup:
  Type: AWS::AutoScaling::AutoScalingGroup
  Properties:
    Cooldown: [1]

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

A300

B0

C30

D600

Attempts:

3 left

💡 Hint

Common Mistakes

Using too short cooldown like 30 seconds may cause rapid scaling.

Setting cooldown to 0 disables cooldown, which is usually not recommended.

The cooldown period is set in seconds. Setting it to 300 means the group waits 5 minutes before another scaling activity.

2fill in blank

medium

Complete the code to add a cooldown period to a scaling policy in AWS CloudFormation.

AWS

MyScalingPolicy:
  Type: AWS::AutoScaling::ScalingPolicy
  Properties:
    Cooldown: [1]

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

A60

B0

C10

D300

Attempts:

3 left

💡 Hint

Common Mistakes

Setting cooldown too low can cause scaling thrashing.

Setting cooldown to zero disables cooldown, which can cause issues.

The Cooldown property defines the wait time after a scaling activity. 300 seconds is a typical cooldown period.

3fill in blank

hard

Fix the error in the cooldown period value to ensure it is valid for an Auto Scaling group.

AWS

AutoScalingGroup:
  Type: AWS::AutoScaling::AutoScalingGroup
  Properties:
    Cooldown: [1]

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

A300

B-100

Cfive minutes

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using negative numbers for cooldown.

Using text strings instead of numbers.

Cooldown must be a non-negative integer in seconds. '300' is valid, negative or string values are invalid.

4fill in blank

hard

Fill both blanks to correctly configure cooldown and min adjustment step in a scaling policy.

AWS

ScalingPolicy:
  Type: AWS::AutoScaling::ScalingPolicy
  Properties:
    Cooldown: [1]
    MinAdjustmentStep: [2]

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

A300

B1

C5

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting MinAdjustmentStep to zero disables scaling steps.

Setting cooldown too low causes rapid scaling.

Cooldown is set to 300 seconds to allow stabilization. MinAdjustmentStep of 5 means scaling changes happen in steps of 5 units.

5fill in blank

hard

Fill all three blanks to configure a scaling policy with cooldown, adjustment type, and scaling adjustment.

AWS

ScalingPolicy:
  Type: AWS::AutoScaling::ScalingPolicy
  Properties:
    Cooldown: [1]
    AdjustmentType: [2]
    ScalingAdjustment: [3]

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

A200

BChangeInCapacity

C3

DPercentChangeInCapacity

Attempts:

3 left

💡 Hint

Common Mistakes

Using PercentChangeInCapacity with a small integer scaling adjustment.

Setting cooldown too low or too high.

Cooldown is 200 seconds to wait between scaling actions. AdjustmentType 'ChangeInCapacity' means the scaling adjustment is an absolute number. ScalingAdjustment of 3 means add or remove 3 instances.

Practice

1. What is the main purpose of a cooldown period in AWS Auto Scaling?

easy

A. To pause scaling actions and let the system stabilize

B. To speed up the scaling process

C. To permanently stop scaling activities

D. To reset the scaling policies automatically

Solution

1. Step 1: Understand cooldown period function

   Cooldown periods temporarily pause scaling actions to avoid rapid changes.

2. Step 2: Identify the purpose in AWS Auto Scaling

   This pause helps the system stabilize before another scaling action happens.

3. Final Answer:

   To pause scaling actions and let the system stabilize -> Option A

4. Quick Check:

   Cooldown period = pause scaling [OK]

Hint: Cooldown means wait before next scaling [OK]

Common Mistakes:

• Thinking cooldown speeds up scaling
• Confusing cooldown with stopping scaling permanently
• Assuming cooldown resets policies

2. Which of the following is the correct way to set a cooldown period of 300 seconds in an AWS Auto Scaling group using AWS CLI?

easy

A. aws autoscaling configure-group --name my-asg --cooldown 300

B. aws autoscaling update-auto-scaling-group --auto-scaling-group-name my-asg --default-cooldown 300

C. aws autoscaling create-cooldown --name my-asg --seconds 300

D. aws autoscaling set-cooldown --group my-asg --time 300

Solution

1. Step 1: Recall AWS CLI command for cooldown

   The correct command uses 'update-auto-scaling-group' with '--default-cooldown' option.

2. Step 2: Match the correct syntax

   aws autoscaling update-auto-scaling-group --auto-scaling-group-name my-asg --default-cooldown 300 matches the official syntax to set cooldown to 300 seconds.

3. Final Answer:

   aws autoscaling update-auto-scaling-group --auto-scaling-group-name my-asg --default-cooldown 300 -> Option B

4. Quick Check:

   Correct CLI syntax = aws autoscaling update-auto-scaling-group --auto-scaling-group-name my-asg --default-cooldown 300 [OK]

Hint: Use update-auto-scaling-group with --default-cooldown [OK]

Common Mistakes:

• Using non-existent commands like set-cooldown
• Wrong parameter names like --time or --seconds
• Confusing create and update commands

3. Consider this AWS Auto Scaling group with a cooldown period of 180 seconds. If a scale-out event happens at 12:00:00 and another scale-out event triggers at 12:02:00, what will happen?

medium

A. The second scale-out will be ignored because cooldown is active

B. The second scale-out will proceed because cooldown ended

C. Both scale-outs happen simultaneously

D. The cooldown period resets to 180 seconds at 12:02:00

Solution

1. Step 1: Calculate cooldown end time

   Cooldown starts at 12:00:00 and lasts 180 seconds (3 minutes), so ends at 12:03:00.

2. Step 2: Compare second event time with cooldown

   The second event at 12:02:00 is before cooldown ends, so it should be ignored.

3. Step 3: Re-examine options carefully

   The second scale-out will be ignored because cooldown is active says second scale-out ignored, but cooldown is active until 12:03:00, so correct.

4. Final Answer:

   The second scale-out will be ignored because cooldown is active -> Option A

5. Quick Check:

   Cooldown active = ignore scale-out [OK]

Hint: Cooldown blocks actions until time ends [OK]

Common Mistakes:

• Assuming cooldown ends before 180 seconds
• Thinking cooldown resets on new event
• Believing multiple scale-outs happen simultaneously

4. You set a cooldown period of 120 seconds on your Auto Scaling group, but you notice scaling actions still happen too quickly. What is the most likely cause?

medium

A. Cooldown periods do not affect scaling speed

B. Cooldown period is set in minutes, not seconds

C. Cooldown period is too short for your application startup time

D. You need to disable cooldown to slow scaling

Solution

1. Step 1: Understand cooldown relation to app startup

   Cooldown should be long enough to let new instances start and stabilize.

2. Step 2: Identify cause of quick scaling

   If cooldown is shorter than startup time, scaling triggers again too soon.

3. Final Answer:

   Cooldown period is too short for your application startup time -> Option C

4. Quick Check:

   Cooldown < startup time = fast scaling [OK]

Hint: Match cooldown to app startup time [OK]

Common Mistakes:

• Confusing seconds with minutes in cooldown
• Thinking cooldown disables scaling
• Believing cooldown has no effect on scaling speed

5. You have an application with a startup time of 5 minutes and a shutdown time of 2 minutes. What is the best cooldown period setting for your AWS Auto Scaling group to avoid rapid scaling actions?

hard

A. Set cooldown to 300 seconds (5 minutes) to cover startup time

B. Set cooldown to 120 seconds (2 minutes) to cover shutdown time

C. Set cooldown to 60 seconds to speed up scaling

D. Set cooldown to 600 seconds (10 minutes) to cover both startup and shutdown

Solution

1. Step 1: Identify relevant cooldown duration

   Cooldown should cover the longest time the system needs to stabilize after scaling.

2. Step 2: Compare startup and shutdown times

   Startup is 5 minutes, shutdown is 2 minutes, so total 7 minutes to be safe.

3. Step 3: Choose cooldown that covers both safely

   Setting cooldown to 10 minutes (600 seconds) covers both startup and shutdown comfortably.

4. Final Answer:

   Set cooldown to 600 seconds (10 minutes) to cover both startup and shutdown -> Option D

5. Quick Check:

   Cooldown ≥ startup + shutdown time [OK]

Hint: Cooldown ≥ startup + shutdown time for safety [OK]

Common Mistakes:

• Setting cooldown too short for startup time
• Ignoring shutdown time in cooldown
• Choosing cooldown shorter than app needs