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 DevOps Engineer - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Automation & Scale: Using AWS Config conformance packs allows you to deploy a consistent set of rules (like s3-bucket-level-public-access-prohibited) to all accounts in the organization. Tamper Proofing: When deployed via the delegated administrator or management account, member accounts cannot modify or delete the conformance pack or its rules. Centralized Notification: You can configure the AWS Config rule to trigger a Systems Manager (SSM) Automation or an EventBridge rule in the central account, which then sends a message to a central SNS topic that the SecOps team is subscribed to.
Goal: Detect and notify when Block Public Access is turned off on any S3 bucket across all AWS accounts in an organization. AWS Config tracks resource configuration changes, like changes to S3 bucket access settings. The s3-bucket-level-public-access-prohibited managed rule evaluates whether S3 buckets have Block Public Access settings enabled. Conformance packs allow deployment of these rules organization-wide in a managed way. A Systems Manager automation document can be triggered on noncompliance to publish to an SNS topic for notifications. Central management via a delegated administrator ensures member accounts can't disable the rule or notification.
To bad I can't edit, so to correct myself: PutBucketPublicAccessBlock is indeed the IAM permission and what you should filter on. And the cloudformation solution in option B also lacks the safeguard to prevent users from disabling the eventbridge rule (and therefore disabling the notification)