A company needs to keep user transaction data in an Amazon DynamoDB table. The company must retain the data for 7 years. What is the MOST operationally efficient solution that meets these requirements?
A.
Use DynamoDB point-in-time recovery to back up the table continuously.
B.
Use AWS Backup to create backup schedules and retention policies for the table.
C.
Create an on-demand backup of the table by using the DynamoDB console. Store the backup in an Amazon S3 bucket. Set an S3 Lifecycle configuration for the S3 bucket.
D.
Create an Amazon EventBridge (Amazon CloudWatch Events) rule to invoke an AWS Lambda function. Configure the Lambda function to back up the table and to store the backup in an Amazon S3 bucket. Set an S3 Lifecycle configuration for the S3 bucket.
Answer is B
"Amazon DynamoDB offers two types of backups: point-in-time recovery (PITR) and on-demand backups. (==> D is not the answer)
PITR is used to recover your table to any point in time in a rolling 35 day window, which is used to help customers mitigate accidental deletes or writes to their tables from bad code, malicious access, or user error. (==> A isn't the answer)
On demand backups are designed for long-term archiving and retention, which is typically used to help customers meet compliance and regulatory requirements.
This is the second of a series of two blog posts about using AWS Backup to set up scheduled on-demand backups for Amazon DynamoDB. Part 1 presents the steps to set up a scheduled backup for DynamoDB tables from the AWS Management Console." (==> Not the DynamoBD console and C isn't the answer either)
https://aws.amazon.com/blogs/database/part-2-set-up-scheduled-backups-for-amazon-dynamodb-using-aws-backup/
Dynamo backups cannot be scheduled or sent to S3, so answer should be B)
1) https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/BackupRestore.html
2) https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Backup.Tutorial.html
The most operationally efficient solution that meets these requirements would be to use option B, which is to use AWS Backup to create backup schedules and retention policies for the table.
AWS Backup is a fully managed backup service that makes it easy to centralize and automate the backup of data across AWS resources. It allows you to create backup policies and schedules to automatically back up your DynamoDB tables on a regular basis. You can also specify retention policies to ensure that your backups are retained for the required period of time. This solution is fully automated and requires minimal maintenance, making it the most operationally efficient option.
Option A, using DynamoDB point-in-time recovery, is also a viable option but it requires continuous backup, which may be more resource-intensive and may incur higher costs compared to using AWS Backup.
Option C, creating an on-demand backup of the table and storing it in an S3 bucket, is also a viable option but it requires manual intervention and does not provide the automation and scheduling capabilities of AWS Backup.
Option D, using Amazon EventBridge (CloudWatch Events) and a Lambda function to back up the table and store it in an S3 bucket, is also a viable option but it requires more complex setup and maintenance compared to using AWS Backup.
Anytime the "Operational efficiency"comes into picture, one should consider the options with serverless or managed services. DynamoDB is a serverlessservice, and AWS Backup is a managed service. Others involve operational work in terms of maintenance of backups etc.
Agreed with option B is the right one. AWS backup retention goes from 1 day to 100 years (or even indefinitely, if you do not enter a retention period), so will meet the requirements.
Well a 7 years TTL on the dynamoDB records could be the simpliest to answer the question, so B for the "retention policies". And since the B also propose AWS backup with a retention time at 7 years, why not.
The key advantages of using AWS Backup are:
Fully managed backup service requiring minimal operational overhead
Built-in scheduling, retention policies, and backup monitoring
Supports point-in-time restore for DynamoDB
Automated and scalable solution
B - is the answer because its easy to setup via AWS Backup & It indicates the keyword "MOST Operational Efficient". Other answers are indicating Cost efficient
AWS Backup is a fully managed backup service that simplifies the process of creating and managing backups across various AWS services, including DynamoDB. It allows you to define backup schedules and retention policies to automatically take backups and retain them for the desired duration. By using AWS Backup, you can offload the operational overhead of managing backups to the service itself, ensuring that your data is protected and retained according to the specified retention period.
This solution is more efficient compared to the other options because it provides a centralized and automated backup management approach specifically designed for AWS services. It eliminates the need to manually configure and maintain backup processes, making it easier to ensure data retention compliance without significant operational effort.
A
PITR is used to recover your table to any point in time in a rolling 35 day window, which is used to help customers mitigate accidental deletes or writes to their tables from bad code, malicious access, or user error. (==> A is the answer)
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
123jhl0
Highly Voted 2 years, 3 months agoLuckyAro
2 years agoMutiverseAgent
1 year, 7 months agoapp12
1 year agoBuruguduystunstugudunstuy
Highly Voted 2 years, 1 month agoBuruguduystunstugudunstuy
2 years, 1 month agoDharmarajan
Most Recent 1 week, 1 day agosatyaammm
1 month agoPaulGa
4 months, 3 weeks agoOctavioBatera
10 months, 3 weeks agocheroh_tots
11 months, 3 weeks ago1dfed2b
11 months agopsyll0n
1 year agoawsgeek75
1 year agoawsgeek75
1 year, 1 month agoviru
1 year, 1 month agoMikado211
1 year, 2 months agoGuru4Cloud
1 year, 5 months agotamefi5512
1 year, 7 months agocookieMr
1 year, 7 months agoRahul2212
1 year, 7 months agoAbrar2022
1 year, 8 months ago