Question 18
Cloud Native ArchitectureWhich of these is NOT a typical benefit of using a container orchestrator for managing applications?
Correct answer: D
Explanation
Container orchestrators manage deployment, scaling, scheduling, and service discovery for containerized apps. They do not redesign application architecture, so they cannot "automatically convert" a monolithic application into microservices; that requires code and design changes by developers.
Why each option is right or wrong
A. Improved resource utilization through bin packing.
B. Simplified application code logic for handling infrastructure failures.
C. Abstracted underlying infrastructure differences.
D. Automatic conversion of monolithic applications to microservices.
Container orchestrators such as Kubernetes are designed to handle operational concerns like scheduling, scaling, self-healing, and service discovery for already-containerized workloads; they do not alter an application’s internal architecture. There is no standard orchestration feature, API, or control-plane function that can transform a monolith into microservices automatically, because that requires refactoring code, defining service boundaries, and changing data and deployment design by developers.
E. Enhanced scalability and availability of applications.