What is one key difference between an Amazon EBS-backed and an instance-store backed instance?
A.
Amazon EBS-backed instances can be stopped and restarted.
B.
Instance-store backed instances can be stopped and restarted.
C.
Auto scaling requires using Amazon EBS-backed instances.
D.
Virtual Private Cloud requires EBS backed instances.
Explanation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device
A
0
0
Correct answer is A
0
0
A
0
0
A is right
1
0
Why A? Can someone reference a reason for choosing A?
0
0
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device
0
0
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html
0
0
Characteristic Amazon EBS-Backed Amazon Instance Store-Backed
Boot time
Usually less than 1 minute
Usually less than 5 minutes
Size limit
16 TiB
10 GiB
Root device volume
Amazon EBS volume
Instance store volume
Data persistence
By default, the root volume is deleted when the instance terminates.* Data on any other Amazon EBS volumes persists after instance termination by default. Data on any instance store volumes persists only during the life of the instance.
Data on any instance store volumes persists only during the life of the instance. Data on any Amazon EBS volumes persists after instance termination by default.
Upgrading
The instance type, kernel, RAM disk, and user data can be changed while the instance is stopped.
Instance attributes are fixed for the life of an instance.
Charges
You’re charged for instance usage, Amazon EBS volume usage, and storing your AMI as an Amazon EBS snapshot.
You’re charged for instance usage and storing your AMI in Amazon S3.
AMI creation/bundling
Uses a single command/call
Requires installation and use of AMI tools
Stopped state
Can be placed in stopped state where instance is not running, but the root volume is persisted in Amazon EBS
Cannot be in stopped state; instances are running or terminated
1
0