Activate the Control Tower RDS encryption guardrail and notify through EventBridge to SNS
Short answer
A Activate the Control Tower RDS encryption control and use EventBridge to route noncompliant events to an SNS topic for notification.
Question
Key Takeaways
Control Tower already exists in this organization, so activating its pre-built RDS-encryption control and wiring the resulting Config noncompliance events to SNS through EventBridge adds essentially no operational overhead (A). Writing a custom Config rule in every account (C) or deploying scheduled Lambda functions via StackSets (B) distributes custom code and maintenance across all accounts, and an hourly EC2 cron job (D) is the least efficient of all.
With AWS Control Tower already governing the landing zone and all databases running on Amazon RDS, the most operationally efficient compliance path is to activate the built-in optional control that detects unencrypted RDS storage and create an EventBridge rule that routes its noncompliant events to an SNS topic the security engineer subscribes to. No per-account custom code or scheduled jobs are needed.
Common mistake: Writing a custom AWS Config rule in every account (C)—although the guardrail itself is implemented with AWS Config, building and distributing a custom rule to every account adds overhead that Control Tower's pre-built control avoids. Deploying Lambda functions to every account through StackSets to poll encryption state (B)—this is custom code operating on a schedule rather than an event-driven compliance signal, so it is far less efficient.
Expert Analysis
Why the Answer Is Correct
The landing zone is already governed by AWS Control Tower with a dedicated audit and logging account, so the built-in control that detects whether RDS storage is encrypted can simply be activated and its findings consumed as events. Creating an EventBridge rule that filters those noncompliance events and targets an SNS topic, then subscribing the security engineer's email, delivers the required notification with no code deployed to member accounts and no polling—this is the most operationally efficient option given Control Tower is already in place.
Why the Other Options Are Wrong
B deploys Lambda functions into every account via StackSets that query encryption state on a schedule and publish custom metrics, adding code distribution and maintenance. C creates a custom Config rule in every account, which duplicates a capability Control Tower already provides as a ready control and requires rolling the rule out org-wide. D launches an EC2 instance running an hourly cron job and emails directly, which is the least automated and least reliable option. A is the most efficient.
Community Comment Notes
Community voted A (78), with C a minority (22). Commenters keyed on the phrase 'the company uses AWS Control Tower', noting that A leverages an existing Control Tower control with the least operational overhead. One commenter noted that guardrails use AWS Config underneath, which is true but does not change that A avoids deploying any custom rule or code to member accounts.
Official Reference
https://docs.aws.amazon.com/controltower/latest/userguide/strongly-recommended-controls.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
Identify 'AWS Control Tower' in the scenario as a hint to use its built-in detective controls (guardrails) rather than building custom solutions. Guardrails are managed centrally and require no code deployment to member accounts, offering the highest operational efficiency compared to StackSets or custom Lambda/Config rules.
Frequently Asked Questions
Does AWS Control Tower use AWS Config?
Why is Option C less efficient than A?
Community Votes
78% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 10 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 10
-
thanhnv142 👍 4 Answered AA is correct: we need guardraild to detect non-compliances B and D: no mention of guardrail. C: Though this option mentions guardrail, it uses AWS Config to detect non-compliances
-
vortegon 👍 4 Answered Ahttps://docs.aws.amazon.com/controltower/latest/userguide/strongly-recommended-controls.html#disallow-rds-storage-unencrypted
-
Ramdi1 👍 3 Answered ALeverages existing infrastructure: It utilizes native AWS Control Tower functionality for compliance checks and integrates seamlessly with SNS for notifications. Centralized management: Configuration and monitoring are done in the audit account, eliminating the need for individual resources in each account. Scalability: Handles future account growth without manual intervention.
-
didek1986 👍 3 Answered AA https://docs.aws.amazon.com/controltower/latest/userguide/strongly-recommended-controls.html#disallow-rds-storage-unencrypted
-
sejar 👍 3 Answered CGuardrail uses AWS Config for compliance detection
Show 5 more comments
-
DanShone 👍 3 Answered AA - least operational overhead
-
Diego1414 👍 2 Answered CAnswer: C - https://docs.aws.amazon.com/controltower/latest/userguide/strongly-recommended-controls.html#disallow-rds-storage-unencrypted
-
jamesf 👍 2 Answered AKeywords: Control Tower A company uses Amazon RDS for all databases in its AWS accounts. The company uses AWS Control Tower
-
dkp 👍 3 Answered Amost efficient way is A
-
hotblooded 👍 2 Answered CCompliance == Aws config
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DOP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full DOP-C02 Practice Test →