Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
AWS philosophy: "An account is a container". This philosophy emerged with "Landingzone"(Control Tower) and Organsations .... lots and lots of reInvent talks over years about that. One single account is used by everyone, second account is accessible only by the security team. Account is fenced, versioned plus retenion period deletes. If you think "account as Container" pattern, it starts to make sense. Yes, one could still gain access to the original account and data could leak - this true for all answers. But big picture it makes sense. So its A
Big picture would be to implement the pattern for other things as well. With that one would end up with separation of privileges. That would address the additional "what if's". Maybe think of it as a first step that is focused on the Bucket. Then it starts to make sense. There is no answer that covers Big Picture(the all and everything) because that is out of scope. None of the answers does!
A is the answer : for D- GuardDuty alerts after threats—it does not prevent deletion or modification. No mention of object lock, versioning, or backup/replication. An attacker with sufficient credentials could still erase evidence and data.