which the database cannot be written to and results in …

Which procedure for backing up a relational database on EC2 that is using a set of RAlDed
EBS volumes for storage minimizes the time during which the database cannot be written to
and results in a consistent backup?

A.
1. Detach EBS volumes, 2. Start EBS snapshot of volumes, 3. Re-attach EBS volumes

B.
1. Stop the EC2 Instance. 2. Snapshot the EBS volumes

C.
1. Suspend disk I/O, 2. Create an image of the EC2 Instance, 3. Resume disk I/O

D.
1. Suspend disk I/O, 2. Start EBS snapshot of volumes, 3. Resume disk I/O

E.
1. Suspend disk I/O, 2. Start EBS snapshot of volumes, 3. Wait for snapshots to complete, 4.
Resume disk I/O

Explanation:
https://aws.amazon.com/cn/premiumsupport/knowledge-center/snapshot-ebs-raid-array/
To create an “application-consistent” snapshot of your RAID array, stop applications from
writing to the RAID array, and flush all caches to disk. Then ensure that the associated EC2
instance is no longer writing to the RAID array by taking steps such as freezing the file
system, unmounting the RAID array, or *shutting down the associated EC2 instance*. After
completing the steps to halt all I/O, take a snapshot of each EBS volume.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-detaching-volume.html
You can detach an Amazon EBS volume from an instance explicitly or by terminating the
instance. However, if the instance is running, you must first unmount the volume from the
instance.”