A company hosts critical data in an S3 bucket. Even though they have assigned the appropriate permissions to the bucket, they are still worried about data deletion. What measures can be taken to…

Question

Options

• AEnable versioning on the S3 bucket
• BEnable data at rest for the objects in the bucket
• CEnable MFA Delete in the bucket policy
• DEnable data in transit for the objects in the bucket

• A
  74% (26)
• B
  14% (5)
• D
  11% (4)

Explanation

One of the AWS Security blogs mentions the followinj Versioning keeps multiple versions of an object in the same bucket. When you enable it on a bucket Amazon S3 automatically adds a unique version ID to every object stored in the bucket. At that point, a simple DELETE action does not permanently delete an object version; it merely associates a delete marker with the object. If you want to permanently delete an object version, you must specify its version ID in your DELETE request. You can add another layer of protection by enabling MFA Delete on a versioned bucket. Once you do so, you must provide your AWS accounts access keys and a valid code from the account's MFA device in order to permanently delete an object version or suspend or reactivate versioning on the bucket. Option B is invalid because enabling encryption does not guarantee risk of data deletion. Option D is invalid because this option does not guarantee risk of data deletion. https://aws.amazon.com/blogs/security/securing-access-to-aws-using-mfa-part-3/

No community discussion yet for this question.