Why is cloud-native design beneficial for resilience in MDC3?

• A. It centralizes all services into one monolith.
• B. It enables microservices, containers, and orchestration to isolate failures and scale components independently.
• C. It prevents any failure from occurring.
• D. It requires no monitoring.

Answer: (D)

Cloud-native design strengthens resilience by enabling isolation of failures and independent scaling through microservices, containers, and orchestration. Breaking an application into small, loosely connected services means a problem in one area doesn’t have to bring the entire system down. The orchestrator continuously checks service health, restarts failing components, and can route traffic away from problems while other parts keep operating. Containers provide consistent environments and fast restarts, making it practical to update, scale, or replace individual pieces without touching the whole app. This setup supports fault containment, quicker recovery, and the ability to adjust capacity for each part of the system as needed. In contrast, a single monolith creates a larger blast radius for failures and makes scaling or recovery slower. Also, resilience relies on visibility—monitoring and telemetry are essential to detect issues and drive automated responses, not something to skip.