SOA-C02 practice question 4 of 10

[Monitoring, Reporting, and Automation] A SysOps administrator must ensure that all of a company's current and future Amazon S3 buckets have logging enabled If an S3 bucket does not have logging enabled an automated process must enable logging for the S3 bucket. Which solution will meet these requirements?

Full set: 557 questions
Answer options
A: Use AWS Trusted Advisor 10 perform a check for S3 buckets that do not have logging enabled Configure the check to enable logging for S3 buckets that do not have logging enabled.
B: Configure an S3 bucket policy that requires all current and future S3 buckets to have logging enabled
C: Use the s3-bucket-logging-enabled AWS Config managed rule. Add a remediation action that uses an AWS Lambda function to enable logging.
D: Use the s3-bucket-logging-enabled AWS Config managed rule. Add a remediation action that uses the AWS-ConfigureS3BucketLoggmg AWS Systems Manager Automation runbook to enable logging. Correct answer
Correct Answer:
D. Use the s3-bucket-logging-enabled AWS Config managed rule. Add a remediation action that uses the AWS-ConfigureS3BucketLoggmg AWS Systems Manager Automation runbook to enable logging.
Explanation

AWS Config continuously tracks resource configurations and evaluates them against desired governance states. The s3-bucket-logging-enabled managed rule specifically and natively checks if server access logging is enabled for all Amazon S3 buckets. To fulfill the automated remediation mandate efficiently without writing custom code, this Config rule should be paired with a native remediation action utilizing AWS Systems Manager (SSM) Automation. The managed SSM document AWS-ConfigureS3BucketLogging dynamically enables server access logging on any non-compliant bucket flagged by AWS Config. This serverless, configuration-driven approach guarantees that both current and future S3 buckets automatically remediate themselves natively, eliminating the need to maintain custom scripting or Lambda functions.

Why Incorrect

A: AWS Trusted Advisor can check whether S3 logging is enabled but lacks the built-in capability to automatically execute remediation actions. B: S3 bucket policies can enforce conditions like native encryption requirements, but they cannot actively configure the bucket to enable access logging internally. C: While a custom Lambda function could perform remediation, utilizing the native AWS Systems Manager Automation runbook completely eliminates the operational overhead of custom code.

References

AWS Config Developer Guide, "s3-bucket-logging-enabled" (Document ID: config/latest/developerguide/s3-bucket-logging-enabled.html)

AWS Systems Manager User Guide, "AWS-ConfigureS3BucketLogging" (Document ID: systems-manager/latest/userguide/automation-awscfg.html)

Scroll to Top