How would you deploy this change while minimizing any i…

You work for a startup that has developed a new photo-sharing application for mobile devices. Over recent months your
application has increased in popularity; this has resulted in a decrease in the performance of the application clue to the
increased load. Your application has a two-tier architecture that is composed of an Auto Scaling PHP application tier and
a MySQL RDS instance initially deployed with AWS Cloud Formation. Your Auto Scaling group has a min value of 4 and
a max value of 8. The desired capacity is now at 8 because of the high CPU utilization of the instances. After some

analysis, you are confident that the performance issues stem from a constraint in CPU capacity, although memory
utilization remains low. You therefore decide to move from the general-purpose M3 instances to the compute-optimized
C3 instances. How would you deploy this change while minimizing any interruption to your end users?

You work for a startup that has developed a new photo-sharing application for mobile devices. Over recent months your
application has increased in popularity; this has resulted in a decrease in the performance of the application clue to the
increased load. Your application has a two-tier architecture that is composed of an Auto Scaling PHP application tier and
a MySQL RDS instance initially deployed with AWS Cloud Formation. Your Auto Scaling group has a min value of 4 and
a max value of 8. The desired capacity is now at 8 because of the high CPU utilization of the instances. After some

analysis, you are confident that the performance issues stem from a constraint in CPU capacity, although memory
utilization remains low. You therefore decide to move from the general-purpose M3 instances to the compute-optimized
C3 instances. How would you deploy this change while minimizing any interruption to your end users?

A.
Sign into the AWS Management Console, copy the old launch configuration, and create a new launch configuration that specifies the
C3 instances.
Update the Auto Scaling group with the new launch configuration.
Auto Scaling will then update the instance type of all running instances.

B.
Sign into the AWS Management Console, and update the existing launch configuration with the new C3 instance type.
Add an UpdatePolicy attribute to your Auto Scaling group that specifies AutoScalingRollingUpdate.

C.
Update the launch configuration specified in the AWS CloudFormation template with the new C3 instance type.
Run a stack update with the new template.
Auto Scaling will then update the instances with the new instance type.

D.
Update the launch configuration specified in the AWS CloudFormation template with the new C3 instance type.
Also add an UpdatePolicy attribute to your Auto Scaling group that specifies AutoScalingRollingUpdate.
Run a stack update with the new template.



Leave a Reply 7

Your email address will not be published. Required fields are marked *


Sadeel Anjum

Sadeel Anjum

D

Signing in to AWS console is never a good options when talking about an automated solutions, and
We use AutoScalingRollingUpdate to avoid downtime so D is the right option.

Sam T

Sam T

Not D- cant update launch Config. Have to create New – so A

sporokh

sporokh

You’re wrong. You CAN update LC in CloudFormation. Read the question attentively.

James

James

“…update launch Config,” meaning that updating the CloudFormation as a new template in a manner of version-control, if my understanding is correct.

Coolguy

Coolguy

One simple rule of thumb,

Resources created via CFN should not be manually updated / deleted outside the stack. Next time it will fail to update the stack.

In this way you can safely eliminate option A and B