Exam AWS-SysOps topic 1 question 558 discussion

Lambda needs to programatically determine which instances it needs to shutdown. Cloudwatch can initiate the lambda but not determine these are the instances that needs to be shutdown. For this lambda has to use tags.

I'd say D because its asking how to identify corrupted servers. Lambda is used here to intentionally to stop instances. I'm guessing it's asking for how to identify which instances are corrupt when the instances are started again. The instances probably would start normally, however the custom application data stored on the instance is probably what is corrupt. These instances can be identified with custom cloud watch metrics embedded with the application.

By assigning a specific tag to the EC2 instances that should not be stopped, the Administrator can modify the Lambda function to include a filter based on that tag. This way, the function will only stop the instances that do not have the designated tag, leaving the critical instances untouched.

Question states "Due to the nature of the programs running on certain servers......" You can use tags to select the certain servers.

Keyword is to "Identify" the corrupted instances Answer C: We use "resource tagging" to tag the corrupted instances

Answer: C, Based on the tagging, we can exclude the critical servers from the auto shutdown activity, and can be viewable from the cloud trail as well. A: This is for recording the configuration D: Cloudwatch will use CloudEvent to trigger the Lamdba function nothing else.

Answer D. You can view the EC2 status with EC2 console, CLI or CloudWatch dashboard or CloudWatch logs. Since the other options are not mentioned, CloudWatch is the one. Check this out. https://aws.amazon.com/premiumsupport/knowledge-center/start-stop-lambda-cloudwatch/

A https://docs.aws.amazon.com/lambda/latest/dg/services-config.html

Maybe I misunderstand the question. But a simple solution would be to use Cloudwatch to monitor Instance status. If the volume becomes corrupted or failed to boot you can take action?

I'll go with Taggin, cuz nothing from other choices can tell Lambda which EC2 to work on

Going with C, the questions ask how to determine the instances which are corrupt. How you gonna determine which one is corrupt, you need to restart the instances to find out. Tagging will determine which EC2 instance will not restart. Its run time error not the config so I believe config does not help...

The question says, how to identity the failed instances? AWS config monitors only the changes done on the environment. AWS tagging wont be useful to identity the failed instances, unless we know what instances they are and they are tagged, which is not the scenario in this case. So I will go with option A

The question is how to identify these Ec2 Instances which means the dependency between applications or configuration or servers side. The possible answers are A and C. But C wont help you to understand the issues. so the Best answer is A for the below reason. AWS Config provides a detailed view of the configuration of AWS resources in your AWS account. This includes how the resources are related to one another and how they were configured in the past so that you can see how the configurations and relationships change over time. An AWS resource is an entity you can work with in AWS, such as an Amazon Elastic Compute Cloud (EC2) instance, an Amazon Elastic Block Store (EBS) volume, a security group, or an Amazon Virtual Private Cloud (VPC)

Only my view... i think the answer is A. If there is corruption the server.. config on the server is corrupted.. which mean if you audit using Config you should be able to identify the failed servers..

C is correct