In terms of designing for auto-healing capabilities, which feature is crucial for maintaining continuous operation?

Question

Options

• AManual intervention for error detection and correction
• BAutomated monitoring and response systems
• CInfrequent backups to reduce the burden on system resources
• DThe use of monolithic architectures to simplify troubleshooting

• A
  3% (1)
• B
  83% (29)
• C
  9% (3)
• D
  6% (2)

Explanation

Automated monitoring and response systems (B) are the cornerstone of auto-healing because they detect failures, trigger corrective actions, and restore normal operation - all without human involvement, which is the very definition of auto-healing.

Why the distractors fail:

• A (Manual intervention) directly contradicts auto-healing - requiring humans to detect and fix errors introduces delays and defeats the purpose of an automated self-recovery system.
• C (Infrequent backups) actually increases risk; auto-healing relies on timely state recovery, which requires frequent, not infrequent, backups.
• D (Monolithic architectures) are harder to heal automatically because a failure in one component can cascade and bring down the entire system; microservices with isolated components are far better suited for targeted auto-recovery.

Memory tip: Think of auto-healing like a thermostat - it automatically monitors temperature and responds by turning heat on or off without you lifting a finger. Option B is the thermostat; all other options require you to get off the couch.

No community discussion yet for this question.