Bash, the Crucial Exams Chat Bot
AI Bot
Disaster Recovery and High Availability Flashcards
AWS Certified Solutions Architect Professional SAP-C02 Flashcards
| Front | Back |
| Difference between RTO and RPO | RTO is Recovery Time Objective (downtime period); RPO is Recovery Point Objective (data loss window) |
| Difference between synchronous and asynchronous replication | Synchronous replication ensures identical data in real-time; asynchronous may have a lag |
| How often should backups be updated | Depends on RPO requirements; typically daily, hourly, or real-time |
| Key elements of a disaster recovery plan | Backup systems, recovery procedures, communication plans, and testing |
| Primary benefit of multi-region deployments | Ensures high availability and minimizes service disruptions across geographic regions |
| Purpose of backups | To ensure critical data is preserved and can be restored in case of a failure or disaster |
| Role of load balancers in high availability | Distributes traffic across multiple servers to prevent overload and ensure availability |
| Steps in testing a disaster recovery plan | Simulating a failure, validating recovery processes, evaluating gaps, and improving the plan |
| What is a cold backup | A backup that is not actively connected and must be manually activated during a recovery situation |
| What is a hot standby system | A backup system that is constantly running and ready to take over in case of failure |
| What is an active-active deployment | Multiple systems actively handle requests, providing redundancy and load balancing |
| What is cloud-based disaster recovery | A strategy leveraging cloud services to store backups and enable recovery operations |
| What is data replication | Copying data across multiple storage systems for high availability and fault tolerance |
| What is fault tolerance | The ability of a system to continue operating even if one or more components fail |
| Why redundancy is important in disaster recovery | Redundancy ensures no single point of failure disrupts an entire system |
This deck includes strategies for fault tolerance, backup solutions, disaster recovery plans, and multi-region deployments to ensure continuity.