Exam AWS Certified SysOps Administrator - Associate topic 1 question 388 discussion

its c and e

D/E look weird. one server application have issue, you redeploy all instance??

CD. Why not A? Cloud watch agent cannot restart a service which is what answer A states (not server). Systems Manager State Manager can ensure that the service is running as expected and can take corrective actions if it isn't. By scheduling the check every 5 minutes, the service can be quickly restarted if it crashes, effectively automating the recovery process.By using EC2 user data to deploy a script that periodically checks and ensures the service is running, you can achieve a self-recovery mechanism for the application. Since the script runs on the instance itself, it can restart the service without the need for external intervention. YOUR WELCOME

Vote C,D A is esclused, because CloudWatch doesn't seem restart process, but usally is used for restart the EC2 instance. B is esclused, because the lambda need login every time and in this case don't see any check if the service is running or not E is esclused, because this solutionn assicured that the service is running in initial phase, but after there isn't check if the service is running or not Remain C e D

CD seems right because : A. Install the Amazon CloudWatch agent on the EC2 instances. Configure the CloudWatch agent to monitor the service. Set the CloudWatch action to restart if the service health check fails. While CloudWatch can monitor the service, it does not have the built-in capability to restart services directly on EC2 instances. Additional custom integration would be required to perform restarts, making it less straightforward than the chosen solutions.

AC seems right

I think you all ignored the question request. It asks for two solutions, meaning each one should be valid. That being said, let's review the answers. -B: it doesn't give a complete solution. It is only will restart the service every 5. Min this doesn't apply to the question "automate recovery IF the service crashes on any of the EC2 instances." -E: In my opinion, this option is the same as B since it will guarantee the service is running on the startup; however, who knows what will happen next? -I think A is valid and straightforward, so it is either AC or AD I will go with "AD" because the instances in the ASG might change over time, so I don't know if this will affect the tags mentioned in the C option.

A and C

answer is AE Cloudwatch agent will restart Server if service is not running (A), server will restart with the service running(E), I don't see why it would be C if you are already monitoring with Cloudwatch agent, the agent literally has the ability to trigger a sns topic that can invoke the lambda function. . .

Maybe C and D

A and C are straight forward however is too complex. Use Systems Manager state - >Tag the EC2 instances for targeted management.>Use AWS Systems Manager State Manager to create an association that uses the AWS-RunShellScript document.>Configure the association to run a script that checks if the service is running and starts the service if it's not.>Schedule the association to run at regular intervals (e.g., every 5 minutes) to ensure continuous monitoring and recovery.