exam questions

Exam AWS-SysOps All Questions

View all questions & answers for the AWS-SysOps exam

Exam AWS-SysOps topic 1 question 281 discussion

Exam question from Amazon's AWS-SysOps
Question #: 281
Topic #: 1
[All AWS-SysOps Questions]

An organization has setup Auto Scaling with ELB. Due to some manual error, one of the instances got rebooted. Thus, it failed the Auto Scaling health check. Auto
Scaling has marked it for replacement. How can the system admin ensure that the instance does not get terminated?

  • A. Update the Auto Scaling group to ignore the instance reboot event
  • B. It is not possible to change the status once it is marked for replacement
  • C. Manually add that instance to the Auto Scaling group after reboot to avoid replacement
  • D. Change the health of the instance to healthy using the Auto Scaling commands
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️
After an instance has been marked unhealthy by Auto Scaling, as a result of an Amazon EC2 or ELB health check, it is almost immediately scheduled for replacement as it will never automatically recover its health. If the user knows that the instance is healthy then he can manually call the SetInstanceHealth action
(or the as-set instance- health command from CLI. to set the instance's health status back to healthy. Auto Scaling will throw an error if the instance is already terminating or else it will mark it healthy.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
albert_kuo
8 months, 3 weeks ago
Selected Answer: D
If an instance has been marked for replacement due to a failed health check triggered by a manual reboot, you can manually change the health status of the instance back to "healthy" using Auto Scaling commands. This would prevent the instance from being terminated and replaced. You can do this by issuing Auto Scaling commands to set the health status of the instance to "healthy," overriding the failed health check status.
upvoted 1 times
...
TroyMcLure
2 years, 6 months ago
Correct Answer: D
upvoted 1 times
...
mvsnogueira
2 years, 6 months ago
D https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html "After an instance has been marked unhealthy because of an Amazon EC2 or Elastic Load Balancing health check, it is almost immediately scheduled for replacement. It never automatically recovers its health. You can intervene manually by calling the SetInstanceHealth action (or the set-instance-health command) to set the instance's health status back to healthy. If the instance is already terminating, you get an error. Because the interval between marking an instance unhealthy and its actual termination is so small, attempting to set an instance's health status back to healthy with the SetInstanceHealth action (or, set-instance-health command) is probably useful only for a suspended group. For more information, see Suspending and Resuming Scaling Processes. "
upvoted 2 times
...
awscertified
2 years, 6 months ago
D. Change the health of the instance to healthy using the Auto Scaling commands
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago