Top 50 aws disaster recovery interview questions and answers for devops engineer

AWS Disaster Recovery for DevOps Engineers: Interview Questions & Answers Guide

Welcome to this comprehensive study guide designed for DevOps engineers aiming to master AWS Disaster Recovery. This guide will equip you with essential knowledge, strategies, and practical insights into building resilient systems on AWS. We'll cover key concepts like RTO and RPO, explore various AWS DR strategies, delve into crucial AWS services for DR, and provide direct answers to common AWS disaster recovery interview questions, preparing you for success.

Table of Contents

1. Understanding AWS Disaster Recovery (DR) Concepts
2. AWS Disaster Recovery Strategies for DevOps
3. Key AWS Services for DR Implementation
4. Automating and Testing AWS DR Plans
5. Security, Compliance, and Cost in AWS DR
6. Sample AWS DR Interview Questions & Answers
7. FAQ: Common AWS DR Interview Questions
8. Further Reading
9. Conclusion

Understanding AWS Disaster Recovery (DR) Concepts

Disaster Recovery (DR) on AWS is about planning and implementing strategies to ensure your applications and data remain available even after major disruptions like regional outages, data corruption, or cyberattacks. For a DevOps engineer, understanding these foundational concepts is crucial for designing robust, fault-tolerant architectures.

Two critical metrics in DR are Recovery Time Objective (RTO) and Recovery Point Objective (RPO):

• Recovery Time Objective (RTO): This is the maximum acceptable delay between the interruption of service and the restoration of service. It defines how quickly you need to be back up and running. A low RTO means you need to recover very quickly.
• Recovery Point Objective (RPO): This is the maximum acceptable amount of data loss measured in time. It defines the point in time to which your data must be recoverable. A low RPO means you can tolerate very little data loss.

Practical Action: When designing a system, always define the acceptable RTO and RPO with business stakeholders first. These metrics will dictate your choice of DR strategy and the AWS services you use.

AWS Disaster Recovery Strategies for DevOps

AWS offers several DR strategies, each balancing cost, complexity, RTO, and RPO. DevOps engineers must select the most appropriate strategy based on business requirements.

1. Backup and Restore:

   This is the most cost-effective strategy. Data is regularly backed up to a separate AWS region or an isolated location within the same region (e.g., S3 Glacier). In a disaster, data is restored, and infrastructure is provisioned from scratch. This strategy typically has higher RTO and RPO.

   Example: Backing up EBS volumes to S3 snapshots and restoring them in another region if the primary region fails.

2. Pilot Light:

   A small, minimal version of your environment is always running in the DR region, acting as a "pilot light." Core data services are replicated, and during a disaster, the necessary compute resources are quickly scaled up to restore full functionality. This offers lower RTO and RPO than backup and restore.

   Example: Having an RDS database replicated to another region, with EC2 instances only spun up during a failover event using AMIs.

3. Warm Standby:

   A scaled-down but fully functional version of your environment is continuously running in the DR region. This replica receives live data updates. In a disaster, it can be quickly scaled up to full capacity, providing faster recovery. RTO and RPO are significantly lower than Pilot Light.

   Example: Running a smaller set of EC2 instances and an RDS replica in the DR region, ready to receive traffic and scale up.

4. Multi-site Active-Active (Hot Standby):

   Your application runs simultaneously in multiple active regions, distributing traffic between them. If one region fails, traffic is seamlessly routed to the other active region(s). This provides the lowest RTO and RPO (near zero) but is the most complex and expensive strategy.

   Example: Using Amazon Route 53 with weighted routing and health checks to distribute traffic across identical deployments in two different AWS regions.

Action Item: Evaluate your application's criticality and budget constraints to determine the optimal DR strategy. Document your chosen strategy thoroughly.

Key AWS Services for DR Implementation

DevOps engineers leverage a suite of AWS services to implement and manage their disaster recovery plans. Understanding these services is vital for effective AWS Disaster Recovery.

• Amazon S3: Highly durable object storage, perfect for backups (cross-region replication).
• Amazon EBS Snapshots: Point-in-time backups of EBS volumes, easily copied across regions.
• Amazon RDS Multi-AZ & Read Replicas: Multi-AZ provides synchronous replication and automatic failover within a region; Read Replicas enable asynchronous replication, often used for cross-region DR.
• AWS Backup: A centralized backup service to automate backups across various AWS services (EBS, RDS, EC2, DynamoDB, etc.).
• AWS CloudFormation: Infrastructure as Code (IaC) to provision and manage your DR environment consistently and efficiently.
• Amazon Route 53: DNS service used for intelligent traffic routing (failover, weighted routing) to alternate regions during a disaster.
• AWS Systems Manager: Can automate operational tasks, including DR runbooks.
• AWS Elastic Disaster Recovery (DRS): Simplifies and accelerates recovery of on-premises and cloud-based applications to AWS with minimal downtime and data loss.

Code Snippet Example (Basic CloudFormation for S3 bucket with replication):

AWSTemplateFormatVersion: '2010-09-09'
Description: S3 Bucket with Cross-Region Replication for DR

Resources:
  PrimaryDRBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: your-primary-dr-bucket-2025
      VersioningConfiguration:
        Status: Enabled
      ReplicationConfiguration:
        Role: arn:aws:iam::123456789012:role/S3ReplicationRole # Replace with your IAM Role ARN
        Rules:
          - Id: PrimaryToSecondaryReplication
            Status: Enabled
            Destination:
              Bucket: arn:aws:s3:::your-secondary-dr-bucket-2025
              # Account: 123456789012 # Uncomment if replicating to different account
              # If replicating to a different region within the same account, 'Account' is not needed.

  SecondaryDRBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: your-secondary-dr-bucket-2025 # Must be in a different region
      VersioningConfiguration:
        Status: Enabled

Outputs:
  PrimaryBucketName:
    Description: Name of the primary S3 bucket
    Value: !Ref PrimaryDRBucket
  SecondaryBucketName:
    Description: Name of the secondary S3 bucket for DR
    Value: !Ref SecondaryDRBucket
    

Action Item: Familiarize yourself with the pricing models and operational overhead of each service. Design your DR architecture using Infrastructure as Code (e.g., CloudFormation) for consistency.

Automating and Testing AWS DR Plans

A DR plan is only as good as its execution. Automation and regular testing are paramount for successful AWS Disaster Recovery.

DevOps engineers should focus on:

• Automated Failover: Utilize services like Route 53 health checks, AWS Lambda, and Step Functions to detect failures and automatically initiate failover procedures.
• Infrastructure as Code (IaC): Define your entire DR environment (even dormant resources) using CloudFormation or Terraform. This ensures consistent and repeatable deployments.
• DR Drills: Regularly schedule and execute full-scale DR drills. These drills should test the entire recovery process, from detection to failover and failback. Document any issues and refine your runbooks.
• Monitoring and Alerting: Implement robust monitoring with Amazon CloudWatch and configure alerts for critical metrics and events that could indicate an impending or active disaster.

Practical Action: Plan your first DR drill. Start with a non-critical application and simulate a regional outage. Measure your actual RTO and RPO against your defined objectives.

Security, Compliance, and Cost in AWS DR

Beyond technical implementation, DevOps engineers must consider security, compliance, and cost optimization when designing AWS Disaster Recovery strategies.

• Security: Ensure that your DR environment maintains the same security posture as your primary environment. This includes IAM roles, security groups, network ACLs, data encryption at rest and in transit, and access controls for backup data.
• Compliance: Many industries have strict regulatory requirements (e.g., HIPAA, GDPR, PCI DSS) that dictate data residency, retention, and recovery capabilities. Ensure your DR strategy meets these obligations.
• Cost Optimization: DR can be expensive, especially with multi-site active-active strategies. Optimize costs by choosing the right strategy for each application, leveraging S3 Glacier for long-term backups, using reserved instances for warm standby resources, and ensuring resources are only provisioned when needed (e.g., with Pilot Light).

Action Item: Conduct a security review of your DR plan. Map your DR capabilities against any relevant compliance frameworks your organization must adhere to.

Sample AWS DR Interview Questions & Answers

Here are a few common AWS disaster recovery interview questions that a DevOps engineer might encounter, along with concise answers drawing from the concepts discussed above:

Q1: What is the difference between RTO and RPO in the context of AWS DR?
A1: RTO (Recovery Time Objective) is the maximum acceptable downtime an application can experience after a disaster. RPO (Recovery Point Objective) is the maximum acceptable amount of data loss that can occur. RTO measures time to recover, while RPO measures data freshness.

Q2: Describe the four main AWS DR strategies and when you would use each.
A2:

1. Backup & Restore: Most cost-effective, high RTO/RPO. For non-critical apps where some downtime/data loss is acceptable.
2. Pilot Light: Cheaper than warm/hot, moderate RTO/RPO. Core services replicated, compute spun up on demand. For apps needing quicker recovery than backup & restore.
3. Warm Standby: More expensive, lower RTO/RPO. Scaled-down replica always running. For business-critical apps needing faster recovery.
4. Multi-site Active-Active: Most expensive, near-zero RTO/RPO. Applications run in multiple regions simultaneously. For mission-critical applications requiring continuous availability.

Q3: How can you automate a failover process on AWS for a web application?
A3: We can use Amazon Route 53 with health checks. Route 53 monitors the health of endpoints in the primary region. If health checks fail, it automatically updates DNS records to route traffic to a pre-provisioned or quickly scaled-up environment in a secondary DR region. AWS Lambda functions and AWS Step Functions can also be used to orchestrate more complex failover procedures.

FAQ: Common AWS DR Interview Questions

Quick answers to frequently asked questions about AWS Disaster Recovery for DevOps.

Q: What is the primary benefit of using AWS for Disaster Recovery?

A: AWS provides a highly available, globally distributed, and scalable infrastructure, allowing organizations to implement robust DR plans without the significant upfront investment of on-premises solutions.

Q: Can AWS DR protect against human error?

A: Yes, many AWS DR strategies, especially those involving immutable infrastructure or regular backups (like EBS Snapshots or S3 Versioning), can help recover from accidental deletions or misconfigurations by restoring to a previous known good state.

Q: How does AWS Multi-AZ differ from cross-region DR?

A: Multi-AZ protects against failures within a single AWS region (e.g., a single Availability Zone outage) by synchronously replicating resources. Cross-region DR protects against an entire region failure by replicating resources to a geographically separate AWS region.

Q: What is AWS Elastic Disaster Recovery (DRS) primarily used for?

A: AWS Elastic Disaster Recovery (DRS) is primarily used for simplifying and accelerating the recovery of applications running on physical servers, virtual machines, or other cloud environments (including other AWS regions) to an AWS target region with minimal downtime and data loss.

Q: Why is testing your AWS DR plan crucial?

A: Testing confirms that your DR plan works as expected, identifies potential gaps or issues before a real disaster, and helps measure actual RTO/RPO, ensuring the plan meets business objectives and builds confidence in the recovery process.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the primary benefit of using AWS for Disaster Recovery?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AWS provides a highly available, globally distributed, and scalable infrastructure, allowing organizations to implement robust DR plans without the significant upfront investment of on-premises solutions."
      }
    },
    {
      "@type": "Question",
      "name": "Can AWS DR protect against human error?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, many AWS DR strategies, especially those involving immutable infrastructure or regular backups (like EBS Snapshots or S3 Versioning), can help recover from accidental deletions or misconfigurations by restoring to a previous known good state."
      }
    },
    {
      "@type": "Question",
      "name": "How does AWS Multi-AZ differ from cross-region DR?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Multi-AZ protects against failures within a single AWS region (e.g., a single Availability Zone outage) by synchronously replicating resources. Cross-region DR protects against an entire region failure by replicating resources to a geographically separate AWS region."
      }
    },
    {
      "@type": "Question",
      "name": "What is AWS Elastic Disaster Recovery (DRS) primarily used for?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AWS Elastic Disaster Recovery (DRS) is primarily used for simplifying and accelerating the recovery of applications running on physical servers, virtual machines, or other cloud environments (including other AWS regions) to an AWS target region with minimal downtime and data loss."
      }
    },
    {
      "@type": "Question",
      "name": "Why is testing your AWS DR plan crucial?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Testing confirms that your DR plan works as expected, identifies potential gaps or issues before a real disaster, and helps measure actual RTO/RPO, ensuring the plan meets business objectives and builds confidence in the recovery process."
      }
    }
  ]
}
    

Further Reading

• AWS Disaster Recovery Solutions (Official AWS Documentation)
• AWS Well-Architected Framework - Reliability Pillar
• AWS Elastic Disaster Recovery (AWS DRS) User Guide

Conclusion

Mastering AWS Disaster Recovery is a critical skill for any DevOps engineer. By understanding core concepts like RTO and RPO, selecting appropriate DR strategies, leveraging powerful AWS services, and diligently automating and testing your plans, you can build resilient, highly available applications. This guide has provided a solid foundation to confidently approach AWS disaster recovery interview questions and contribute significantly to your organization's operational excellence.

Stay tuned for more in-depth guides and advanced AWS topics. Subscribe to our newsletter to receive updates and exclusive content directly in your inbox!

1. What is AWS Disaster Recovery?

AWS Disaster Recovery is a strategy that ensures workloads can continue operating after failures using AWS services. It focuses on restoring systems, data, and infrastructure quickly through backups, multi-region architectures, and automated recovery workflows.

2. What are the main AWS Disaster Recovery strategies?

AWS offers four DR strategies: Backup & Restore, Pilot Light, Warm Standby, and Multi-Site Active-Active. Each provides varying RTO and RPO levels, enabling cost-effective or high-availability solutions based on business recovery requirements.

3. What is RTO in Disaster Recovery?

RTO (Recovery Time Objective) defines the maximum acceptable downtime after a failure. It helps determine how quickly systems must return to operation and guides DR strategy selection based on application criticality and business impact tolerance.

4. What is RPO in Disaster Recovery?

RPO (Recovery Point Objective) indicates how much data loss is acceptable, measured in time. It defines how frequently backups or replications should occur, ensuring data protection and continuity during disasters or infrastructure failures.

5. What AWS service is commonly used for backups?

AWS Backup centralizes and automates backup operations across services like EBS, RDS, DynamoDB, S3, and EFS. It enforces policies, schedules backups, safeguards data with cross-region copies, and ensures compliance for disaster recovery planning.

6. What is AWS Pilot Light architecture?

Pilot Light keeps minimal core infrastructure running in a secondary region while other components remain off. During disaster events, additional resources are quickly scaled up, enabling faster recovery at low cost with controlled resource usage.

7. What is Warm Standby in AWS DR?

Warm Standby keeps a scaled-down version of production running in another region. It enables faster failover compared to Pilot Light because key services remain online, offering improved RTO while still maintaining cost efficiency over active-active setups.

8. What is Multi-Site Active-Active Disaster Recovery?

Multi-Site Active-Active DR runs full workloads in two or more AWS regions simultaneously. Traffic is distributed across regions, enabling zero downtime failover, extremely low RTO and RPO, and highly resilient architectures for mission-critical systems.

9. What AWS service enables cross-region database replication?

Amazon RDS provides cross-region read replicas for MySQL, PostgreSQL, and MariaDB engines. It allows disaster recovery, offloading read workloads, and enabling fast failover. Aurora offers Global Database for sub-second replication between regions.

10. How does Amazon S3 support disaster recovery?

Amazon S3 supports DR using versioning, replication (CRR), lifecycle policies, and strong durability. Cross-region replication ensures automatic copying of objects, enabling rapid recovery and protecting against region-level outages or accidental deletions.

11. What is AWS Route 53 failover routing?

Route 53 failover routing enables automatic redirection of traffic to healthy endpoints when the primary site becomes unavailable. It uses health checks and DNS routing policies to support DR strategies like warm standby and active-active deployments.

12. How does AWS CloudFormation support disaster recovery?

CloudFormation enables infrastructure as code templates that can recreate entire environments in another region. During disasters, stacks can be redeployed quickly, ensuring consistent recovery of infrastructure, configurations, and dependencies.

13. What role does AWS IAM play in disaster recovery?

IAM ensures secure identity and access continuity during disasters by maintaining consistent permissions and roles across regions. Using IAM policies, roles, and federation, teams can manage DR infrastructure without security gaps or operational delays.

14. What is AWS Multi-AZ deployment?

Multi-AZ deployment automatically replicates data synchronously across Availability Zones, ensuring high availability and fault tolerance. It enables automatic failover during outages, reducing downtime for RDS, ElastiCache, and other AWS-managed services.

15. What is AWS Multi-Region DR?

Multi-Region DR replicates data, applications, and infrastructure across AWS regions. It protects workloads from regional failures, enabling quick failover, low RTO/RPO targets, and continuous operation even during large-scale outages or natural disasters.

16. How does Amazon EBS snapshot replication help DR?

EBS snapshots provide point-in-time backups of volumes, stored in S3. They can be copied across regions for DR, enabling rapid restoration of EC2 instances or applications in failure scenarios, ensuring resilience and minimized downtime during incidents.

17. What is AWS DataSync used for in DR?

AWS DataSync automates fast, secure, and consistent transfer of large datasets between on-premises and AWS or across regions. It accelerates backup, replication, and disaster recovery workflows by supporting continuous or scheduled data movement.

18. How does AWS S3 Cross-Region Replication work?

S3 Cross-Region Replication automatically copies objects from one S3 bucket to another in a different region. It supports DR by enabling geographically distributed data, ensuring durability, compliance, and rapid recovery from regional failures.

19. What is Amazon Aurora Global Database?

Aurora Global Database replicates data across multiple AWS regions with sub-second latency. It supports disaster recovery by enabling fast failover, minimal downtime, and continued read operations during disasters, ensuring high resilience for applications.

20. What is AWS Elastic Disaster Recovery?

AWS Elastic Disaster Recovery replicates physical, virtual, and cloud workloads continuously to AWS. It minimizes downtime and data loss by enabling fast recovery, automated scaling, and cross-region resilience for enterprise applications during failures.

21. How does Amazon DynamoDB Global Tables support DR?

DynamoDB Global Tables provide multi-region replication with automatic conflict resolution. They ensure global availability, low-latency reads, and immediate failover during disasters, enabling resilient architectures with near-zero RTO and RPO.

22. What is AWS Backup Vault Lock?

Backup Vault Lock enforces write-once-read-many (WORM) protection on backups, preventing accidental or malicious deletion. It supports DR and compliance by ensuring critical backups remain immutable and available during recovery events or security breaches.

23. How does AWS CloudEndure Disaster Recovery work?

CloudEndure DR continuously replicates machines to a low-cost staging area in AWS. During disasters, it launches fully provisioned instances within minutes. It offers fast recovery, minimal data loss, and automated failover across regions and accounts.

24. What is the purpose of AWS Global Accelerator in DR?

AWS Global Accelerator routes user traffic through the AWS edge network, improving performance and availability. In DR scenarios, it automatically redirects traffic to healthy regions or endpoints, ensuring low downtime and consistent user experience.

25. How does Amazon SNS help in DR automation?

SNS enables real-time notifications and automated workflows triggered by alarms and failures. It integrates with Lambda, CloudWatch, and other services to orchestrate DR actions such as failover, resource creation, and infrastructure scaling.

26. What is AWS RDS automated backup retention?

RDS automated backups provide daily snapshots and transaction logs, enabling point-in-time restoration. They support DR by ensuring databases can be recovered quickly after outages or corruption, with configurable retention periods for compliance.

27. What is the difference between Multi-AZ and Read Replicas?

Multi-AZ provides synchronous replication for high availability and failover. Read replicas use asynchronous replication for scaling read traffic. For DR, Multi-AZ provides automatic failover, while replicas support faster cross-region recovery strategies.

28. How does AWS Step Functions help with DR automation?

Step Functions orchestrate sequential DR workflows like failover, resource recreation, and data validation. They automate complex recovery processes using serverless state machines, reducing manual effort and improving recovery reliability and speed.

29. What is AWS Fault Injection Simulator?

AWS FIS introduces controlled failures to test system resilience. It helps validate DR strategies, uncover weaknesses, and improve recovery time by simulating outages, latency issues, or region failures in a safe, predictable testing environment.

30. How does Auto Scaling support DR?

Auto Scaling adapts capacity based on demand or failures. During DR events, it can recreate instances, scale workloads in backup regions, and ensure applications remain available. It improves resilience by restoring lost capacity quickly and efficiently.

31. What is S3 Versioning and why is it important for DR?

S3 Versioning preserves every version of an object, protecting against accidental deletion or overwriting. It supports DR by enabling recovery of previous versions, ensuring data integrity and restoring critical files during outages or human errors.

32. How does AWS Lambda help in disaster recovery workflows?

Lambda automates DR actions like backup validation, resource creation, DNS updates, or cross-region replication. Its serverless nature makes it ideal for lightweight, event-driven recovery tasks that reduce manual intervention and accelerate failover.

33. How does Amazon VPC support DR planning?

VPC provides isolated network environments that can be replicated across regions using templates. DR setups require subnets, routing, gateways, and security rules mirrored in secondary regions to maintain consistent network behavior during failover.

34. What is the role of Amazon CloudTrail in DR?

CloudTrail logs API calls and user activity, supporting DR by auditing events before and during outages. It helps identify causes, verify recovery steps, and ensure compliance. Logs can be replicated to another region for added fault tolerance.

35. What is AWS Config and how does it support DR?

AWS Config tracks configuration changes and enforces compliance rules. During DR, it ensures resources in backup regions match required configurations. It helps detect drift, maintain consistency, and validate infrastructure integrity across environments.

36. How does Amazon KMS support disaster recovery?

KMS stores encryption keys that must remain available during DR events. Keys can be replicated across regions using multi-Region keys, enabling encrypted data recovery without delays. It ensures secure access to protected workloads during failover.

37. Why is cross-region replication important in DR?

Cross-region replication protects workloads from regional outages by distributing data geographically. It ensures fast recovery, minimizes data loss, and supports compliance by keeping copies in distant regions for resilience against large-scale disasters.

38. What is AWS Local Zone and how does it relate to DR?

Local Zones extend AWS infrastructure closer to users, reducing latency. Although not a full DR solution, they complement DR planning by providing failover options for specific applications while maintaining low-latency access during outages.

39. How does Amazon FSx support DR?

Amazon FSx provides file systems with features like automatic backups, multi-AZ deployment, and cross-region replication. These capabilities help maintain data availability, support fast recovery, and ensure file-based workloads remain resilient to failures.

40. What is AWS Organizations' role in DR?

AWS Organizations manages multi-account environments used for isolation and DR planning. It centralizes governance, automates policy propagation, and supports cross-account backup, ensuring secure and structured DR architectures across environments.

41. How does AWS Control Tower support DR?

AWS Control Tower orchestrates multi-account setups with automated guardrails and predefined baselines. It helps DR by ensuring accounts are consistently configured, compliant, and ready for recovery operations using standardized infrastructure patterns.

42. What is the purpose of AWS Service Quotas in DR?

Service Quotas ensure resources can scale during DR failover. If quotas are too low, applications may fail to recover. Monitoring and adjusting quotas in advance ensures standby regions can provision required compute, storage, and network resources.

43. How does Amazon ECS/EKS support DR?

ECS and EKS support multi-region deployments, enabling container workloads to run across separate environments. They allow rapid recovery through cluster recreation, cross-region registries, and automated failover workflows using IaC and automation tools.

44. Why is testing essential in AWS Disaster Recovery?

Testing verifies that DR plans work as intended, uncovering gaps in automation, configuration, or scaling. Regular failover drills ensure teams can recover workloads successfully, maintain compliance, and improve recovery time during real disasters.

45. What is a Backup & Restore DR model?

Backup & Restore is the simplest DR model involving periodic backups stored in AWS. During a disaster, data and infrastructure are restored manually or using automation. It offers low cost but has the highest RTO and RPO compared to other DR models.

46. What is AWS S3 Glacier and how is it used in DR?

S3 Glacier provides low-cost archival storage for long-term backups. It supports DR by preserving critical data offline, with selectable retrieval times. It’s ideal for compliance, historical data retention, and cost-effective disaster recovery strategies.

47. How does Amazon MQ support DR?

Amazon MQ offers multi-AZ deployment and supports cross-region replication for message brokers. It ensures message durability and availability during outages, enabling DR for distributed applications relying on active messaging systems or event workflows.

48. What is AWS Outposts' role in DR?

AWS Outposts brings AWS infrastructure on-premises and supports hybrid DR setups. During failures, workloads can fail over between on-premises environments and AWS regions, enabling low-latency resiliency and consistent cloud-native application recovery.

49. How does CloudWatch support DR monitoring?

CloudWatch monitors infrastructure, sends alarms, and triggers automated DR actions. Metrics, logs, and events help detect failures quickly, enabling rapid recovery workflows. It integrates with SNS, Lambda, and Step Functions for automated failover.

50. What is a Disaster Recovery Runbook?

A DR Runbook documents all required recovery steps, tools, contacts, and automation workflows. It ensures teams can execute DR consistently during outages. In AWS, runbooks often integrate with automation tools like Lambda, CloudFormation, and Step Functions.