DynamoDB - Backup and RecoveryWhy does DynamoDB Global Tables use asynchronous replication instead of synchronous replication across regions?ATo reduce write latency and avoid blocking writes across distant regionsBBecause synchronous replication is not technically possibleCTo ensure strong consistency across all regionsDTo prevent any data conflicts automaticallyCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand replication trade-offsSynchronous replication would increase write latency due to network delays between regions.Step 2: Analyze DynamoDB design choiceAsynchronous replication reduces latency and allows writes to complete quickly without waiting for other regions.Final Answer:To reduce write latency and avoid blocking writes across distant regions -> Option AQuick Check:Async replication reduces latency [OK]Quick Trick: Async replication reduces latency, enabling fast writes [OK]Common Mistakes:MISTAKESThinking synchronous replication is usedBelieving async ensures strong consistencyAssuming async prevents all conflicts
Master "Backup and Recovery" in DynamoDB9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More DynamoDB Quizzes Access Patterns and Query Optimization - Hot partition prevention - Quiz 10hard Access Patterns and Query Optimization - Why access patterns drive design - Quiz 14medium Access Patterns and Query Optimization - Single-table design methodology - Quiz 8hard Backup and Recovery - Point-in-time recovery (PITR) - Quiz 13medium Backup and Recovery - Why data protection is essential - Quiz 14medium Backup and Recovery - Point-in-time recovery (PITR) - Quiz 12easy DynamoDB with AWS SDK - Document client abstraction - Quiz 9hard DynamoDB with AWS SDK - Pagination with SDK - Quiz 1easy DynamoDB with Serverless - Why DynamoDB pairs with Lambda - Quiz 11easy Security and Access Control - VPC endpoints for private access - Quiz 7medium