A company is developing an application that runs on Amazon EC2 instances. Currently, the data that the application generates is temporary. However, the company needs to persist the data, even if the EC2 instances are terminated.
A data engineer must launch new EC2 instances from an Amazon Machine Image (AMI) and configure the instances to preserve the data.
Which solution will meet this requirement?
To ensure the data is preserved even if the EC2 instances are terminated, you should launch new EC2 instances by using an AMI backed by an EC2 instance store volume and attach an Amazon Elastic Block Store (Amazon EBS) volume to contain the application data. EBS volumes are network-attached storage that persist independently of the life of an EC2 instance. Therefore, data on an EBS volume remains intact even after the EC2 instance terminates, provided the DeleteOnTermination attribute is set to false for the EBS volume, which is the default behavior for non-root EBS volumes.
CCCCCCC - you need to attach an extra EBS volume When an instance terminates, the value of the DeleteOnTermination attribute for each attached EBS volume determines whether to preserve or delete the volume. By default, the DeleteOnTermination attribute is set to True for the root volume. ref: https://repost.aws/knowledge-center/deleteontermination-ebs
B: the root EBS volume will be deleted on termination by default. C: the EBS is independent from EC2 Termination
Amazon EBS volumes provide persistent block storage for EC2 instances. Data written to an EBS volume is independent of the EC2 instance lifecycle. Even if the EC2 instance is terminated, ***the data on the EBS volume remains intact***. Launching new EC2 instances from an AMI backed by an EBS volume containing the application data ensures the data persists across instance restarts or terminations
C is correct
C - Looks better, because it will save data in all cases
And "Delete on Termination" flag by defaults sets to true, so better to use additional volume for application data
This question is more for practitioner exam :)
ccccccc
Can someone explain why C is NOT right?
Amazon EBS volumes are network-attached, and they persist independently of the life of an EC2 instance. By using an AMI backed by an Amazon EBS volume, the root device for the instance is an EBS volume, which means the data will persist.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/preserving-volumes-on-termination.html Root volume By default, when you launch an instance the DeleteOnTermination attribute for the root volume of an instance is set to true. Therefore, the default is to delete the root volume of the instance when the instance terminates. Non-root volume By default, when you attach a non-root EBS volume to an instance, its DeleteOnTermination attribute is set to false. Therefore, the default is to preserve these volumes. Answer is C
its C!!! B with default setting will delete the EBS volume on termination
launch EC2 using AMI with root EBS that contains data
Voting for B