Practice Test 2 | AWS Certified Solutions Architect Associate | SAA-C03 | Dumps | Mock Test

Correct Answer: A and B

Create Alarms That Stop, Terminate, Reboot, or Recover an Instance 

Using Amazon CloudWatch alarm actions, you can create alarms that automatically stop, terminate, reboot or recover your instances. You can use the stop or terminate actions to save money when you no longer need an instance to be running. You can use the reboot and recover actions to automatically reboot those instances or recover them onto new hardware if a system impairment occurs.

The AWSServiceRoleForCloudWatchEvents service-linked role enables AWS to perform alarm actions on your behalf. The first time you create an alarm in the AWS Management Console, the IAM CLI, or the IAM API, CloudWatch creates the service-linked role for you.

There are a number of scenarios in which you might want to automatically stop or terminate your instance. For example, you might have instances dedicated to batch payroll processing jobs or scientific computing tasks that run for a period of time and then complete their work. Rather than letting those instances sit idle (and accrue charges), you can stop or terminate them, which could help you to save money. The main difference between using the stop and the terminate alarm actions is that you can easily restart a stopped instance if you need to run it again later, and you can keep the same instance ID and root volume. However, you cannot restart a terminated instance instead, you must launch a new instance.

You can add the stop, terminate, reboot or recover actions to any alarm that is set on an Amazon EC2 per-instance metric, including basic and detailed monitoring metrics provided by Amazon CloudWatch (in the AWS/EC2 namespace), as well as any custom metrics that include the InstanceId dimension, as long as its value refers to a valid running Amazon EC2 instance.

For more information on Amazon EC2, please visit the following URL:

• https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-ug.pdf (Page 535)

• Option C is incorrect as SQS cannot be used for monitoring.
• Option D is incorrect as AWS Lambda cannot be used for monitoring.
• Option A is correct. Using Cloudwatch events metrics we can monitor the changes in state for EC2 instances as given in the link.

Please refer the below link for more information on Cloudwatch logs:

https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/CloudWatch-Events-Monitoring-CloudWatch-Metrics.html

• Option B is correct. Using Cloudwatch logs, the changes in state for EC2 instances can be recorded as given in the link.

Please refer the below link for more information on Cloudwatch logs:

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/acw-ug.pdf

Therefore the following options are correct:

A. Use Cloudwatch logs to store the state change of the instances
B.Create an Amazon CloudWatch alarm that monitors an Amazon EC2 instance