A company requires its developers to tag all Amazon Elastic Block Store (Amazon EBS) volumes in an account to indicate a desired backup frequency. This requirement Includes EBS volumes that do not require backups. The company uses custom tags named Backup_Frequency that have values of none, dally, or weekly that correspond to the desired backup frequency. An audit finds that developers are occasionally not tagging the EBS volumes. A DevOps engineer needs to ensure that all EBS volumes always have the Backup_Frequency tag so that the company can perform backups at least weekly unless a different value is specified. Which solution will meet these requirements?
Select one answer.
Marked answer: D
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Chose D1
Option D: Real-Time Enforcement: Ensures tagging compliance as soon as a volume is created or modified. Comprehensive Coverage: Captures both CreateVolume and ModifyVolume events. Minimal Overhead: Automates tagging without requiring manual audits or remediation actions
1
what will happen if dev decide to change tag to dally? AWS Systems Manager Automation runbook to apply the Backup_Frequency tag with a value of weekly
Chose B4
Only takes few minutes to login > Config > Managed rulename = BACKUP_PLAN_MIN_FREQUENCY_AND_MIN_RETENTION_CHECK A = tags everything in EC2, thats EC2::* which includes ELB/EIP/etc. Nope. Option B you can specify the tags to match & expected values = answer.
Keyboard:←→previous / next·A–Echoose·Entercheck, then next
