Bird
0
0

You set up a pilot light disaster recovery strategy but notice recovery time is longer than expected. What is the most likely cause?

medium📝 Debug Q14 of 15
AWS - Architecture Best Practices
You set up a pilot light disaster recovery strategy but notice recovery time is longer than expected. What is the most likely cause?
ABackups are stored in Amazon S3
BThe pilot light environment is not fully configured and requires manual scaling
CWarm standby environment is running at full capacity
DThe primary environment is still active
Step-by-Step Solution
Solution:

  1. Step 1: Analyze pilot light recovery process

    Pilot light requires scaling up minimal systems to full production, so incomplete setup delays recovery.

  2. Step 2: Exclude unrelated options

    Backups in S3 are normal; warm standby running full is unrelated; primary active is normal operation.

  3. Final Answer:

    The pilot light environment is not fully configured and requires manual scaling -> Option B

  4. Quick Check:

    Pilot light slow recovery = incomplete setup [OK]
Quick Trick: Incomplete pilot light setup causes slow recovery [OK]
Common Mistakes:
  • Blaming backups for slow recovery
  • Confusing warm standby with pilot light
  • Assuming primary environment affects recovery time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
Advanced Security - KMS for key management - Quiz 8hard Architecture Best Practices - Multi-tier architecture patterns - Quiz 5medium CloudFormation - Updating and deleting stacks - Quiz 6medium EKS - kubectl configuration for EKS - Quiz 6medium Route 53 - Why DNS management matters - Quiz 2easy Route 53 - Domain registration - Quiz 4medium Route 53 - Route 53 with ELB integration - Quiz 9hard Serverless Architecture - Lambda with S3 event triggers - Quiz 3easy Serverless Architecture - Serverless vs container decision - Quiz 3easy Serverless Architecture - Lambda with DynamoDB Streams - Quiz 8hard