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 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?
Use AWS Backup to create backup schedules and retention policies for the table. This is the most operationally efficient solution because it provides a fully managed service that allows you to automate backup scheduling and implement retention policies to ensure data is retained for the required 7 years. AWS Backup simplifies management, reduces operational overhead, and ensures compliance with retention requirements without requiring manual intervention.
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/
I think the answer is C because of storage time.
i think another reason for why C is not correct is the keyword "on-demand" which is not operation efficient (as this should be an ongoing practice)
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
In the very same link you shared it says that you CAN send backups to S3 https://youtu.be/4INEu_hw30Q?t=54
In the very same link you shared it says that you CAN send backups to S3 https://youtu.be/4INEu_hw30Q?t=54
i think another reason for why C is not correct is the keyword "on-demand" which is not operation efficient (as this should be an ongoing practice)
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.
B. Use AWS Backup to create backup schedules and retention policies for the table. AWS Backup is a fully managed service that makes it easy to centralize and automate the backup of data across AWS resources. It can be used to create backup schedules and retention policies for DynamoDB tables, which will ensure that the data is retained for the desired period of 7 years. This solution will provide the most operationally efficient method for meeting the requirements because it requires minimal effort to set up and manage.
B is clear
B is correct
C is correct because we have to store data in s3 and an S3 Lifecycle configuration for the S3 bucket for 7 year.and its used on-demand backup of the table by using the DynamoDB console because If you need to store backups of your data for longer than 35 days, you can use on-demand backup. On-demand provides you a fully consistent snapshot of your table data and stay around forever (even after the table is deleted).
I think you are correct
In AWSBackup Plan, you can choose 7year Retention with Daily, Weekly or Monly frequency. From operational perspective, I think B is correct.
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.
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.
Answer is simply B as it if MOST operationally efficient. Other options are "distractors" to confuse everyone.
Operational efficiency is always a managed service from AWS. AWS Backup is the right one in this case so B is right answer
Why is the answer not C?
As I see, we are looking for the most operationally efficient solution. So it's B, but the most cost effective its - C (but it isn't a question).
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.
Ans B - there are no special parameters specified for the backup (eg. PITR snapshots) so it doesn't need to be elaborate
We recommend you use AWS Backup to automatically delete the backups that you no longer need by configuring your lifecycle when you created your backup plan. https://docs.aws.amazon.com/aws-backup/latest/devguide/deleting-backups.html
AWS Backup
Option B AWS Backup
B = AWS backup
To retain data for 7 years in an Amazon DynamoDB table, you can use AWS Backup to create backup schedules and retention policies for the table. You can also use DynamoDB point-in-time recovery to back up the table continuously.
With less overhead is AWS Backups: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/backuprestore_HowItWorksAWS.html
using AWS Backup cheaper than DynamoDB point-in-time recovery
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)
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
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
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/backuprestore_HowItWorksAWS.html
https://youtu.be/g4WPLFXLwDE?si=nTWqqDcBe_Y6dtl3
Using AWS Backup is most suitable here for retaining data for 7 years.
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.