A company needs to create a daily Amazon Machine Image (AMI) of an existing Amazon Linux EC2 instance that hosts the operating system, application, and database on multiple attached Amazon Elastic…

Question

Options

• ACreate an AWS Lambda function to call the CreateImage API operation with the EC2 instance ID
• BCreate an AWS Lambda function to call the CreateImage API operation with the EC2 ins ance ID
• CUse AWS Backup to create a backup plan with a backup rule that runs daily.
• DUse AWS Backup to create a backup plan with a backup rule that runs daily.

• A
  3% (1)
• B
  15% (5)
• C
  74% (25)
• D
  9% (3)

Explanation

AWS Backup (option C) is the correct choice because it is the purpose-built, managed service for creating consistent backups of EC2 instances with multiple attached EBS volumes - it coordinates snapshot creation across all volumes simultaneously to guarantee file system integrity, and natively supports daily scheduling via backup plans without custom code.

Options A and B are wrong for the same reason (B is just A with a typo): calling CreateImage via Lambda is a DIY approach that, without careful configuration, does not guarantee consistency across multiple EBS volumes - particularly dangerous when a database is involved, since in-flight writes across volumes can leave the backup in an inconsistent state. A managed service (AWS Backup) is always preferred over a custom Lambda for this use case.

Option D is a duplicate of C - it is identical text and therefore also correct in theory, but on a real exam only one option would be distinct; C is the intended answer.

Memory tip: Think of AWS Backup as the "set it and forget it" solution - whenever an exam question mentions multi-volume consistency, file system integrity, or daily automated backups of EC2/EBS, AWS Backup with a backup plan is the clean, managed answer over any Lambda-based workaround.

No community discussion yet for this question.