SAA-C03 · Question #799
A financial company is migrating its banking applications to a set of AWS accounts managed by AWS Organizations. The applications will store sensitive customer data on Amazon Elastic Block Store…
The correct answer is A. Enable AWS Config rules for each organizational unit (OU) in Organizations to monitor EBS. AWS Config supports organization-wide rules that can automatically monitor and enforce EBS snapshot permissions across all accounts in an AWS Organization, preventing public sharing with minimal operational overhead.
Question
A financial company is migrating its banking applications to a set of AWS accounts managed by AWS Organizations. The applications will store sensitive customer data on Amazon Elastic Block Store (Amazon EBS) volumes. The company will take regular snapshots for backup purposes. The company wants to implement controls across all AWS accounts to prevent sharing EBS snapshots publicly. Which solution will meet these requirements with the LEAST operational overhead?
Options
- AEnable AWS Config rules for each organizational unit (OU) in Organizations to monitor EBS
- BEnable block public access for EBS snapshots at the organization level.
- CCreate an IAM policy in the root account of the organization that prevents users from modifying
- DUse AWS CloudTrail to track snapshot permission changes.
How the community answered
(46 responses)- A78% (36)
- B2% (1)
- C13% (6)
- D7% (3)
Explanation
AWS Config supports organization-wide rules that can automatically monitor and enforce EBS snapshot permissions across all accounts in an AWS Organization, preventing public sharing with minimal operational overhead.
Community Discussion
No community discussion yet for this question.