A stack was provisioned by CloudFormation, but an engineer later edited a security group rule directly in the console during an incident. The team now wants CloudFormation to report which managed resources no longer match their template definitions so the configuration can be reconciled. Which CloudFormation feature surfaces these out-of-band changes?
- ARun drift detection on the stack, which compares each managed resource against its template definition and reports the properties that differ. Correct
- BCreate a change set for the stack, which previews how a newly submitted template would change the deployed resources before you execute it.
- CEnable a stack policy on the stack, which only governs which resources a subsequent stack update is permitted to modify and changes nothing else.
- DTurn on rollback triggers on the stack, which monitor CloudWatch alarms during an update and roll the whole stack back automatically on failure.
Why A is correct: Drift detection is purpose-built to compare live resource configuration with the expected template values and flag any property that was changed outside CloudFormation, which is exactly what reconciling a manual console edit needs.
Why B is wrong: A change set diffs a new template you submit against the deployed stack; it does not inspect the live resource state, so a manual console edit with no template change produces no entries.
Why C is wrong: A stack policy only restricts which resources an update may modify; it performs no comparison and generates no report of out-of-band changes made through the console.
Why D is wrong: Rollback triggers watch CloudWatch alarms during a stack operation to roll back on failure; they never inspect resource configuration for manual edits, so they cannot surface drift.