DOP-C02 Practice Question 80: Config Remediation SSM Automation Document
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 8 · question 10 of 10
A company uses an AWS Config managed rule to detect Amazon EBS volumes that are not encrypted. When the rule marks a volume noncompliant, the team wants AWS Config itself, with no separate event bus rule or custom Lambda function to invoke the fix, to automatically run a Systems Manager Automation document that snapshots the volume, creates an encrypted copy, and swaps it in, and to give up after a bounded number of attempts if the fix keeps failing.
Which configuration achieves this?
Show answer and explanation
Answer:
AWS Config supports remediation configurations attached directly to a rule: the target type is an SSM Automation document, and setting the remediation to automatic means Config itself starts the Automation execution as soon as a resource is evaluated as noncompliant, with no intermediate EventBridge rule or Lambda function needed. An AutomationAssumeRole is required for automatic remediation so Automation has permission to act, and MaximumAutomaticAttempts together with RetryAttemptSeconds bounds how many automatic retries are made within a time window before Config stops and flags a remediation exception, satisfying the "give up after a bounded number of attempts" requirement.
Option A duplicates functionality Config already provides natively and adds an unnecessary integration layer to build, secure, and operate.
Option B builds an entirely custom pipeline out of SNS and Lambda that reimplements what a native remediation configuration already does, with more moving parts to maintain.
Option D describes a RemediationException, which is a real Config concept, but it means the opposite of what is being asked: it records that a specific resource is deliberately excluded from remediation (for example, after repeated failures), it does not trigger remediation to run.
Reference: Remediating noncompliant AWS resources by using AWS Config Remediation