A start-up firm is using a Dedicated Host for the deployment of Oracle-based applications. Some of the instances on this Dedicated Host are using instance stored volume, while some are using EBS volumes. Host recovery is enabled on this Dedicated host. Due to hardware issues on a dedicated host, a replacement instance was launched. But you found that instance store-backed instances are not recovered to that host. What can be possible reasons for the Instance store-backed instance not recovered on replacement Dedicated host?

Answer options:

A.Need to open an AWS ticket for recovery of instance store-backed instances on Dedicated Host.
B.Need to perform manual recovery of instance store-backed instances on Dedicated Host following remedial steps.
C.Instance store-backed instances need to be rehosted to EBS backed volumes.
D.Manually start & stop instance so that automatic recovery can be initiated to a replacement Dedicated host.

Correct Answer – B
Instance store-backed instances are not automatically recovered on replacement Dedicated host post Host recovery. For these instances, a manual approach needs to be followed based upon remedial steps.
Option A is incorrect as No need to open AWS Ticket, Instance store-backed instances can be recovered using remedial steps to a replacement dedicated host.
Option C is incorrect. Although this will work, this is not required to be recovered to a replacement Dedicated host.
Option D is incorrect as Stopping the instance will not result in the recovery of impaired Dedicated Host.
For more information on Amazon EC2 host recovery, refer to the following URL-
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-recovery.html