ExamTopics Logo
Mail Usteam@examtopics.com
Menu
Amazon Discussions
exam questions

Exam AWS Certified Solutions Architect - Associate SAA-C03 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Associate SAA-C03 exam
Go to Exam

Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 71 discussion

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C03
Question #: 71
Topic #: 1
[All AWS Certified Solutions Architect - Associate SAA-C03 Questions]

A company runs a shopping application that uses Amazon DynamoDB to store customer information. In case of data corruption, a solutions architect needs to design a solution that meets a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 1 hour.
What should the solutions architect recommend to meet these requirements?

  • A. Configure DynamoDB global tables. For RPO recovery, point the application to a different AWS Region.
  • B. Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.
  • C. Export the DynamoDB data to Amazon S3 Glacier on a daily basis. For RPO recovery, import the data from S3 Glacier to DynamoDB.
  • D. Schedule Amazon Elastic Block Store (Amazon EBS) snapshots for the DynamoDB table every 15 minutes. For RPO recovery, restore the DynamoDB table by using the EBS snapshot.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
Community vote distribution
B (100%)
by priya2224 at Oct. 16, 2022, 2:37 p.m.
Disclaimers:
  • - ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
  • - Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Chosen Answer:
This is a voting comment. You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
123jhl0
Highly Voted 2 years, 6 months ago
Selected Answer: B
A - DynamoDB global tables provides multi-Region, and multi-active database, but it not valid "in case of data corruption". In this case, you need a backup. This solutions isn't valid. **B** - Point in Time Recovery is designed as a continuous backup juts to recover it fast. It covers perfectly the RPO, and probably the RTO. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.html C - A daily export will not cover the RPO of 15min. D - DynamoDB is serverless... so what are these EBS snapshots taken from???
upvoted 48 times
LionelSid
2 years, 2 months ago
Yes, it is possible to take EBS snapshots of a DynamoDB table. The process for doing this involves the following steps: Create a new Amazon Elastic Block Store (EBS) volume from the DynamoDB table. Stop the DynamoDB service on the instance. Detach the EBS volume from the instance. Create a snapshot of the EBS volume. Reattach the EBS volume to the instance. Start the DynamoDB service on the instance. You can also use AWS Data pipeline to automate the above process and schedule regular snapshots of your DynamoDB table. Note that, if your table is large and you want to take a snapshot of it, it could take a long time and consume a lot of bandwidth, so it's recommended to use the Global Tables feature from DynamoDB in order to have a Multi-region and Multi-master DynamoDB table, and you can snapshot each region separately.
upvoted 4 times
piavik
2 years ago
What is "DynamoDB service on the instance" ?
upvoted 2 times
...
pentium75
1 year, 4 months ago
DynamoDB is a native cloud service, there is no "instance" that you could "stop", or detach an "EBS volume" from.
upvoted 1 times
...
...
...
Buruguduystunstugudunstuy
Highly Voted 2 years, 4 months ago
Selected Answer: B
The best solution to meet the RPO and RTO requirements would be to use DynamoDB point-in-time recovery (PITR). This feature allows you to restore your DynamoDB table to any point in time within the last 35 days, with a granularity of seconds. To recover data within a 15-minute RPO, you would simply restore the table to the desired point in time within the last 35 days. To meet the RTO requirement of 1 hour, you can use the DynamoDB console, AWS CLI, or the AWS SDKs to enable PITR on your table. Once enabled, PITR continuously captures point-in-time copies of your table data in an S3 bucket. You can then use these point-in-time copies to restore your table to any point in time within the retention period. ***CORRECT*** Option B. Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.
upvoted 14 times
Buruguduystunstugudunstuy
2 years, 4 months ago
***WRONG*** Option A (configuring DynamoDB global tables) would not meet the RPO requirement, as global tables are designed to replicate data to multiple regions for high availability, but they do not provide a way to restore data to a specific point in time. Option C (exporting data to S3 Glacier) would not meet the RPO or RTO requirements, as S3 Glacier is a cold storage service with a retrieval time of several hours. Option D (scheduling EBS snapshots) would not meet the RPO requirement, as EBS snapshots are taken on a schedule, rather than continuously. Additionally, restoring a DynamoDB table from an EBS snapshot can take longer than 1 hour, so it would not meet the RTO requirement.
upvoted 7 times
...
...
satyaammm
Most Recent 3 months, 3 weeks ago
Selected Answer: B
DynamoDB Point-In-Time-Recovery is the most suitable option here for recovering an oject.
upvoted 1 times
...
PaulGa
7 months, 1 week ago
Selected Answer: B
Ans B - just use the built-in DynamoDB PITR... simples...
upvoted 1 times
...
ManikRoy
1 year ago
Selected Answer: B
With point-in-time recovery, you can restore that table to any point in time during the last 35 days. After you enable point-in-time recovery, you can restore to any point in time from five minutes before the current time until 35 days ago. DynamoDB maintains incremental backups of your table.
upvoted 2 times
...
awsgeek75
1 year, 3 months ago
Selected Answer: B
A: Scalability across regions which is not required C: Glacier exports and backup restore won't meet 1 hour RPO time D EBS for DynamoDB table? Sounds impractical B: DynamoDB point-in-time recovery is for this scenario. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.html
upvoted 2 times
...
Guru4Cloud
1 year, 8 months ago
Selected Answer: B
The best option to meet the RPO of 15 minutes and RTO of 1 hour is B) Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time. The key points: DynamoDB point-in-time recovery can restore to any point in time within the last 35 days. This supports an RPO of 15 minutes. Restoring from a point-in-time backup meets the 1 hour RTO. Point-in-time recovery is specifically designed to restore DynamoDB tables with second-level granularity.
upvoted 1 times
...
cookieMr
1 year, 10 months ago
A. Global tables provide multi-region replication for disaster recovery purposes, they may not meet the desired RPO of 15 minutes without additional configuration and potential data loss. C. Exporting and importing data on a daily basis does not align with the desired RPO of 15 minutes. D. EBS snapshots can be used for data backup, they are not directly applicable to DynamoDB and cannot provide the desired RPO and RTO without custom implementation. In comparison, option B utilizing DynamoDB's built-in point-in-time recovery functionality provides the most straightforward and effective solution for meeting the specified RPO of 15 minutes and RTO of 1 hour. By enabling PITR and restoring the table to the desired point in time, the company can recover the customer information with minimal data loss and within the required time frame.
upvoted 3 times
...
Abrar2022
1 year, 11 months ago
The answer is in the question. Read the question again!!! Option B. Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.
upvoted 1 times
...
[Removed]
2 years ago
If there is anyone who is willing to share his/her contributor access, then please write to vinaychethi99@gmail.com
upvoted 1 times
...
career360guru
2 years, 4 months ago
Selected Answer: B
Option B
upvoted 1 times
...
Shasha1
2 years, 4 months ago
B is correct DynamoDB point-in-time recovery allows the solutions architect to recover the DynamoDB table to a specific point in time, which would meet the RPO of 15 minutes. This feature also provides an RTO of 1 hour, which is the desired recovery time objective for the application. Additionally, configuring DynamoDB point-in-time recovery does not require any additional infrastructure or operational effort, making it the best solution for this scenario. Option D is not correct because scheduling Amazon EBS snapshots for the DynamoDB table every 15 minutes would not meet the RPO or RTO requirements. While EBS snapshots can be used to recover data from a DynamoDB table, they are not designed to provide real-time data protection or recovery capabilities
upvoted 1 times
...
Wpcorgan
2 years, 5 months ago
B is correct
upvoted 1 times
...
SimonPark
2 years, 5 months ago
Selected Answer: B
B is the answer
upvoted 1 times
...
BoboChow
2 years, 6 months ago
Selected Answer: B
I think DynamoDB global tables also work here, but Point in Time Recovery is a better choice
upvoted 1 times
...
Kikiokiki
2 years, 6 months ago
I THINK B. https://dynobase.dev/dynamodb-point-in-time-recovery/
upvoted 1 times
...
priya2224
2 years, 6 months ago
answer is D
upvoted 1 times
123jhl0
2 years, 6 months ago
DynamoDB is serverless, so no storage snapshots available. https://aws.amazon.com/dynamodb/
upvoted 2 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
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.

SaveCancel
exam
Someone Bought Contributor Access for:
MS-700
Prague, 1 minute ago