Methods for Enhanced Business Agility and Data Durability in AWS

Correct Answer: A, B.

Requirements:

Business Continuity.

boot agility of the business.

ensure data durability.

This means we need to enhance the availability of the data stored in EBS.

Option A is CORRECT because the lifecycle policies can create EBS snapshots using a schedule.

Option B is CORRECT because the method can create manual data backups for the EBS volumes.

Option C is incorrect because there is no such feature.

Option D is incorrect because data encryption pertains to security and is not asked in our question.

Sure, here is a detailed explanation of the options you have been presented with:

A. Use lifecycle policies for the EBS snapshots.

Amazon EBS (Elastic Block Store) provides persistent block-level storage volumes for use with Amazon EC2 instances in the AWS Cloud. With EBS, you can create point-in-time snapshots of your EBS volumes, which are stored in Amazon S3. You can use these snapshots as a backup, to create a new EBS volume, or to migrate data across regions.

Lifecycle policies allow you to automate the management of your EBS snapshots. You can define rules to automate the creation, retention, and deletion of snapshots, based on their age or other criteria. By using lifecycle policies, you can ensure that your snapshots are managed consistently, and that they are deleted when they are no longer needed. This can help you to reduce costs, and to ensure that you have access to the data you need in the event of a disaster.

B. Create manual EBS Snapshots.

Creating manual EBS snapshots is a simple way to back up your data. You can create a snapshot of your EBS volume at any time, and use it to restore your data later. Manual snapshots can be created using the AWS Management Console, the AWS CLI, or the AWS SDKs. When you create a manual snapshot, you can add a description to help you identify it later, and you can choose whether to make it public or private.

However, manual snapshots can be time-consuming to create, and they may not be created on a regular basis. This means that you may not have access to the most recent data in the event of a disaster.

C. EBS volume read replica.

An EBS volume read replica is a copy of an EBS volume that is automatically created and updated in another Availability Zone within the same region. Read replicas can be used to improve the performance of read-intensive workloads, and to provide high availability in the event of a disaster.

However, read replicas are not a backup solution. They do not provide point-in-time recovery, and they may not be available in the event of a region-wide disaster.

D. EBS volume encryption.

EBS volume encryption provides encryption for your EBS volumes at rest. Encryption can help you to protect your data from unauthorized access, and to meet compliance requirements. EBS encryption is easy to use, and it does not require any changes to your applications.

However, EBS encryption does not provide protection against data loss or corruption. You will still need to back up your data regularly, and to test your backups to ensure that you can recover your data in the event of a disaster.

So, in summary, the two options that can be taken are:

1. Use lifecycle policies for the EBS snapshots.
2. Create manual EBS Snapshots.

Both options provide a way to back up your critical data stored on EBS volumes, and ensure data durability. Using lifecycle policies for EBS snapshots can help you to automate the management of your snapshots, while creating manual snapshots can provide you with more control over when and how your data is backed up.