A user is running a batch process on EBS backed EC2 instances. The batch process starts a few instances to
process hadoop Map reduce jobs which can run between 50 – 600 minutes or sometimes for more time. The
user wants to configure that the instance gets terminated only when the process is completed. How can the
user configure this with CloudWatch?
A.
Setup the CloudWatch action to terminate the instance when the CPU utilization is less than 5%
B.
Setup the CloudWatch with Auto Scaling to terminate all the instances
C.
Setup a job which terminates all instances after 600 minutes
D.
It is not possible to terminate instances automatically
Explanation:
Amazon CloudWatch alarm watches a single metric over a time period that the user specifies and performs
one or more actions based on the value of the metric relative to a given threshold over a number of time
periods. The user can setup an action which terminates the instances when their CPU utilization is below a
certain threshold for a certain period of time. The EC2 action can either terminate or stop the instance as part
of the EC2 action.
Hi, the wright answer is not D but A, please correct that.
The Explanation is right.
Thanks,
Frank
0
0
I think so too. Right explanation but wrong answer chosen. A is still suspecious thought. What if EMR is doing minimal CPU usage job
0
0
Frank is right the most plausible Answer is A (see explanation)
0
0
http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/UsingAlarmActions.html
A
0
0
A is correct
0
0
I am a bit suspicious about this one. It is entirely possible that the CPU utilization may fall below 5% even when the job is running because it is performing a task that is not CPU intensive or it may briefly be waiting on another instance to supply some info, etc. CPU can dip below 5% in the middle of the job, can’t it?
0
0
I feel like D might be the best choice here. I’d recommend the use of a custom Cloudwatch metric to monitor this one but that is not one of the offered choices.
0
0
Venkat,
The statement simply does not stand. “It is not possible to terminate instances automatically”. This is a false statement as per the provided link.
A. This is doable with CW. You can argue all day that it’s not the best way, but the question does not ask for best. “How can the User configure this with CloudWatch?”
B. Instances are not part of an ASG.
C. Wrong as jobs can run past 600 minutes
D. Statement is false.
0
0
A is still probably right, if you are terminating only the instances whose CPU is les than 5%. As the batch process launches more than one instance, so even if after the work load is towards end and one instance gets terminated the others might still carry on and finish the left over job before dropping their CPU to 5% and getting terminated..
0
0
only one instance should get terminated, D mentions terminating all instances so i’d go with A
0
0
a
0
0
A
0
0