A company runs an application on Amazon EC2 instances that currently generates temporary data. The company now needs the application data to persist even if the EC2 instances are terminated. A data engineer must launch new EC2 instances from an AMI and configure them to preserve the data. Which approach satisfies this requirement?

The correct approach is to launch new EC2 instances using an AMI backed by an instance store volume and attach an Amazon EBS volume for application data. This is because instance store volumes are temporary and data is lost when the instance stops or terminates. EBS volumes, however, are persistent block storage that can be detached from one instance and reattached to another, ensuring data persistence even if the EC2 instance is terminated. Incorrect options: An AMI backed by an EC2 instance store volume containing application data would lose that data upon instance termination. An AMI backed by a root EBS volume containing application data would preserve the root volume, but the question implies the application data is separate and needs to persist across instance changes, not just within the root volume. Attaching an additional EC2 instance store volume for application data would still result in data loss upon instance termination, as instance store volumes are ephemeral.