Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam AWS Certified Security - Specialty All Questions

View all questions & answers for the AWS Certified Security - Specialty exam

Exam AWS Certified Security - Specialty topic 1 question 77 discussion

Exam question from Amazon's AWS Certified Security - Specialty
Question #: 77
Topic #: 1
[All AWS Certified Security - Specialty Questions]

Example.com hosts its internal document repository on Amazon EC2 instances. The application runs on EC2 instances and previously stored the documents on encrypted Amazon EBS volumes. To optimize the application for scale, example.com has moved the files to Amazon S3. The security team has mandated that all the files are securely deleted from the EBS volume, and it must certify that the data is unreadable before releasing the underlying disks.
Which of the following methods will ensure that the data is unreadable by anyone else?

  • A. Change the volume encryption on the EBS volume to use a different encryption mechanism. Then, release the EBS volumes back to AWS.
  • B. Release the volumes back to AWS. AWS immediately wipes the disk after it is deprovisioned.
  • C. Delete the encryption key used to encrypt the EBS volume. Then, release the EBS volumes back to AWS.
  • D. Delete the data by using the operating system delete commands. Run Quick Format on the drive and then release the EBS volumes back to AWS.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
McBTTF
Highly Voted 3 years, 1 month ago
Answer is D: Amazon EBS volumes are presented to you as raw unformatted block devices that have been wiped prior to being made available for use. Wiping occurs immediately before reuse so that you can be assured that the wipe process completed. If you have procedures requiring that all data be wiped via a specific method, such as those detailed in NIST 800-88 (“Guidelines for Media Sanitization”), you have the ability to do so on Amazon EBS. You should conduct a specialized wipe procedure prior to deleting the volume for compliance with your established requirements.
upvoted 33 times
McBTTF
3 years, 1 month ago
https://d0.awsstatic.com/whitepapers/aws-security-whitepaper.pdf
upvoted 1 times
...
EA_Practice
3 years ago
however, nothing "specialized" among the wipe options presented in D.
upvoted 1 times
...
scuzzy2010
3 years ago
I agree. As per the question "The security team has mandated that all the files are securely deleted from the EBS volume, and it must certify that the data is unreadable before releasing the underlying disks." - Only D DELETES the Data before releasing the disk.
upvoted 3 times
...
...
josellama2000
Highly Voted 3 years, 1 month ago
Correct is B A is incorrect. Double encrypting the data is useless B is correct. AWS automatically wipes out the volume after the customer release the volume, it also deleted the encryption key. So data recoverable level is low. C is incorrect. The encryption key is automatically delete after releasing the volume D is incorrect. OS's delete and quick-format are useless because data can be recover easily. Note- Any specialized wipe procedure like DoD 5220.22-M or NIST-800-88 must be executed prior to deleting the volume
upvoted 25 times
examacc
3 years, 1 month ago
In my opinion C is correct. As volume has encrypted dek with it. It will stay till AWS allocates it some one. Only plain text key is deleted immidiately as that is held in memory
upvoted 4 times
Reza215r
3 years, 1 month ago
how do you delete the key if it's an aws managed key?
upvoted 5 times
...
DahMac
3 years ago
No where did it say the volumes were encrypted.
upvoted 1 times
CloudMasterGuru
3 years ago
Seems you have not read the question in full: "The application runs on EC2 instances and previously stored the documents on encrypted Amazon EBS volumes"
upvoted 2 times
...
...
SachinJ
3 years ago
You can not delete the key but can schedule it for deletion. Also what if it is being shared by other disks/data.
upvoted 3 times
...
...
examacc
3 years, 1 month ago
AWS do not delete data immidiately. It is deleted before allocation. Only memory is scrubbed before returned to pool.
upvoted 5 times
...
continent34
3 years ago
Cannot be B if they want data unreadable before releasing the underlying disks.
upvoted 4 times
...
CloudMasterGuru
3 years ago
AWS does not immediately wipes the disk after it is deprovisioned. AWS wipes the disk before re-using it for other.
upvoted 4 times
...
...
Arad
Most Recent 5 months, 2 weeks ago
Selected Answer: D
Correct answer is D.
upvoted 1 times
...
virtual
8 months, 1 week ago
Selected Answer: C
C - Delete the encryption key used to encrypt the EBS volume. Then, release the EBS volumes back to AWS When releasing EBS, if encryption key is destroyed, then when it comes to attach EBS again, you'll not be able to decrypt data anymore, so I think C is the best answer.
upvoted 1 times
virtual
2 weeks, 1 day ago
Sorry ! Finally, correct answer is B, because the KMS key is in memory. No need to delete it because when releasing EBS and mounting elsewhere, it would not be readable anymore.
upvoted 1 times
...
...
bkbaws
8 months, 2 weeks ago
Selected Answer: B
The problem with C is the key would have to be customer managed, and you would have to have a different key for every volume, the questions says nothing about CMKs. A quick format (D) does nothing - it does not overwrite data in either Windows or Linux.
upvoted 1 times
...
Kitman
1 year, 4 months ago
Selected Answer: C
Answer is C
upvoted 2 times
...
Trap_D0_r
1 year, 6 months ago
Selected Answer: C
Answer is C: Read the full context of the question: example.com used to use EBS but has switched to S3. This is a one-off event to securely release a bunch of EBS data that now lives on S3. Therefore, the 7 day charge to delete the key is perfectly acceptable to protect the data. The ONLY answer provided that *SECURELY* destroys all the data on those volumes *BEFORE* releasing them is deleting the encryption key--in this context, destroying the key is equivalent to destroying the files, since there is no way to recover them.
upvoted 4 times
...
peddyua
1 year, 8 months ago
Selected Answer: C
When an Amazon EBS volume is deleted or released, the data on the volume is not immediately erased. Instead, the space that was occupied by the data is marked as available for use, but the actual data may still be present on the physical media. To ensure that the data is completely wiped and is not accessible by anyone else, AWS uses a process called "secure erase". AWS recommends that customers take steps to ensure that sensitive data is not stored on EBS volumes or any other storage device for longer than necessary. When the data is no longer required, the volume should be deleted or released, and if necessary, the data should be securely erased using the secure erase feature provided by AWS. I'll go with C
upvoted 2 times
...
razguru
1 year, 9 months ago
Guys objective of this cert is to get knowledge of AWS managed services, offerings and convey to community. Technically it make more sense to zero fill the drive and then release but if you think from AWS EBS offering preservative, AWS is advertising that we do this wipe and cleanup by our-self when volume is deleted, so right option from AWS exam point of view is "B".
upvoted 1 times
...
skillz2investor
1 year, 11 months ago
Selected Answer: B
B is correct answer. AWS wipes data before reuse.
upvoted 2 times
...
arae
2 years ago
Answer is C After you remove the EBS volume, its gone and no one else can access it so C makes perfect sense because your are deleteing the keys to encrypt the data then AWS will delete the volume after you have detached it and it cant be attached to anything else https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-deleting-volume.html
upvoted 1 times
...
plpatankar
2 years, 2 months ago
Selected Answer: C
A. Changing encryption is unnecessary. B. AWS wipes data but before re-use. Here requirement that data is unreadable before releasing. C. Sound reasonable as if encryption key is deleted, encrypted data key stored on EBS can't be recovered and hence data can't be recovered. D. OS delete command will not help, specialised wipe procedure is needed instead.
upvoted 1 times
...
sapien45
2 years, 2 months ago
Selected Answer: D
If my managers explicitely ask me to ensure that '' all the files are securely deleted from the EBS volume, and it must certify that the data is unreadable before releasing the underlying disks'' they would be quite unhappy if I released directly the disks to AWS, without deleting the data prior to that.
upvoted 2 times
...
dcasabona
2 years, 3 months ago
Selected Answer: C
Option B is correct, but option C is more complete and secure. In my option option D is incorrect because if you just delete data and quick format you can recover data using specialized tool. In order avoid that you should degauss the disk.
upvoted 1 times
...
trongod05
2 years, 4 months ago
Selected Answer: C
I chose the answer C based on the only question asked. "Which of the following approaches will assure that no one else can read the data?" If you delete the key, no one else can read the data.
upvoted 1 times
...
mongiam
2 years, 6 months ago
Selected Answer: C
if the key is deleted, data will be not accessible to anyone. hence, deleting a key is equivalent to deletion of data. This is a full-proof solution. hence, C.
upvoted 1 times
...
ceros399
2 years, 7 months ago
C - (CORRECT) if you delete the key, no one will ever be able to read from it B -Wrong, Amazon wipes the EBS the moment before assigning it to a new customer. D - Quick format doesn't zero-out the drive.
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...