What best describes cloud-native design and its relevance to MDC3?

• A. Cloud-native design rejects containers.
• B. It means moving all systems to a single VM.
• C. It ignores orchestration.
• D. Cloud-native design uses microservices, containers, and dynamic orchestration to leverage cloud elasticity; relevant to MDC3 for resilience.

Answer: (D)

Cloud-native design centers on building and running applications in the cloud using small, independently deployable services packaged in containers, with dynamic orchestration to manage them across a cluster. This approach leverages microservices to break functionality into focused components, containers to package code and dependencies consistently, and orchestration (like Kubernetes) to handle deployment, scaling, health checks, and automated recovery. The result is flexible resource use and resilience: services can scale up or down automatically, failures are contained to individual components, and updates can be rolled out safely without downtime.

In the MDC3 context, cloud-native design is especially relevant because it supports robust, fault-tolerant architectures. The ability to isolate failures, recover quickly, and adapt to changing load aligns with MDC3 goals around resilience and reliable operations in distributed environments. It also enables safer, faster deployments and efficient use of cloud resources, which are important for maintaining performance and security at scale.

The other options miss the essence: cloud-native design embraces containers, not rejects them; it relies on distributed microservices rather than a single VM; and orchestration is a core part of managing dynamic, scalable deployments rather than something to ignore.