To protect against ransomware attacks, enabling server-side encryption (option B) is more relevant. It ensures that the data stored in the bucket is encrypted at rest, making it difficult for attackers to gain access to sensitive information even if they manage to infiltrate the system. Additionally, implementing strong access controls, monitoring for unusual activity, and regularly backing up data are other important measures to protect against ransomware attacks.
change to C
Enabling Amazon S3 versioning allows you to preserve, retrieve, and restore every version of every object in your bucket. If malicious activity, such as ransomware, were to occur, enabling versioning can help you recover the previous versions of your objects and restore them to their original state before the attack. This is a valuable feature for data protection and recovery in case of accidental or malicious data modifications.
C is WRONG!!! --- The answer is D.
Versioning is a means of keeping multiple variants of an object IN THE SAME bucket.
Replication actually transports your data into another bucket in another region even into another AWS account..
C seems good option here. Bucket versioning (although removing delete marker is possible but will add more calls), and/or turning on object lock. Using cloudtrail we can get details on object PUT, GET, and DELETE actions. In addition turn on Guardduty for s3 protection
Correct Answer: C
https://docs.aws.amazon.com/wellarchitected/latest/financial-services-industry-lens/use-amazon-s3-object-lock.html
"In conjunction with S3 Versioning, which protects objects from being overwritten, you’re able to ensure that objects remain immutable for as long as S3 Object Lock protection is applied. "
Answer: C
Reason: When versioning is enabled for a bucket, each new operation on the object inside the bucket creates a new version for it. Even encrypting an existing object will create a new version of it while the previous version would be un-encrypted and un-modified. This defeats ransomware infections as each time the object is encrypted, a new encrypted copy of the object is created while the previous one is preserved.
Number one defense against Ransomware is "BACKUP" and "BACKUP". The interest of the intruder is not to read your data but to deny you access. They could still encrypt encrypted data.
Ans is C - With Visioning
B, Even if someone access file it will be encrypted and they cannot use it to ransom.
I don't think C is correc. What if latest version is totally different from last version ?
I don't think B is correct. Encryption just prevent attackers to make sense of your data but won't prevent fron encrypting the encrypted data.
For me it is between A and C.
C looks a better option to me. Since we can have multiple versions of objects, so they can be protected and also easily recovered in case if we need to.
C should be correct if you have versioning enabled and you remove all files or someone will encrypt the files you still have old version in bucket. You are not able remove the bucket from cli or list the versioned files. To see or remove the files you have to log to s3 bucket via console. I just saw on udemy from example. If you want be doble sure MFA enable will prevent deletation versioned files from aws console
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.
aksliveswithaws
Highly Voted 2 years, 7 months agoalbert_kuo
Most Recent 10 months, 1 week agoalbert_kuo
8 months, 3 weeks agoCyril_the_Squirl
2 years, 6 months agoplaster
2 years, 6 months agoTroyMcLure
2 years, 6 months agofqnn
2 years, 6 months agoGrizzlyBear
2 years, 6 months agoThabo_Ramoshai
2 years, 6 months agoPolu
2 years, 6 months agomrbreeze
2 years, 6 months agorathimonika
2 years, 6 months agorewiga
2 years, 6 months agoSHoKMaSTeR
2 years, 6 months agoGolddust
2 years, 6 months agoKt45
2 years, 6 months agoAWS_Noob
2 years, 6 months agosen12
2 years, 6 months agoPyt
2 years, 7 months agoeric20
2 years, 7 months ago