The company uses AWS Organizations to manage its accounts. For the production account, a SysOps administrator must ensure that all data is backed up daily for all current and future Amazon EC2…

Question

Options

• ACreate a backup plan in AWS Backup. Assign resources by resource ID, selecting all existing
• BCreate a backup plan in AWS Backup. Assign resources by tags. Ensure that all existing EC2 and
• CCreate a lifecycle policy in Amazon Data Lifecycle Manager (Amazon DLM). Assign all resources
• DCreate a lifecycle policy in Amazon Data Lifecycle Manager (Amazon DLM). Assign all resources

• A
  14% (3)
• B
  71% (15)
• C
  10% (2)
• D
  5% (1)

Explanation

AWS Backup supports both EC2 and EFS natively. (Amazon DLM does not support EFS backups - that rules out C and D right away.) Using tags instead of listing individual resource IDs means you don’t have to edit the plan every time someone launches a new instance or creates a new file system. Adding an SCP that enforces tagging at creation guarantees that all future resources are automatically included in backups. You can set the plan to run daily and expire after 30 days - exactly what’s required.

No community discussion yet for this question.