Which option correctly lists the key pillars of Cloud Native Architecture?

Which option correctly lists the key pillars of Cloud Native Architecture?

• A. Monoliths, Virtual Machines, SSH, FTP
• B. Microservices, Containers, DevOps, Continuous Delivery
• C. Serverless, Event-driven, Big Data, AI
• D. Batch processing, Relational databases, Manual processes

Answer: (B)

Cloud Native Architecture rests on building software as a set of independently deployable, scalable pieces that work well in dynamic environments. The set that lists microservices, containers, DevOps, and Continuous Delivery captures these foundational ideas: microservices break applications into small services that can be developed, deployed, and scaled independently; containers package each service with its runtime and dependencies so they run consistently across environments; DevOps emphasizes collaboration between development and operations with automation, monitoring, and infrastructure as code; and Continuous Delivery ensures automated, reliable build-test-deploy pipelines for frequent, safe releases. This combination enables agility, resilience, and scalable operation in the cloud. The other options reflect traditional or unrelated approaches. Monoliths, virtual machines, SSH, and FTP signal a non–cloud-native pattern with less emphasis on rapid, automated deployment and containerized, service-based architecture. Serverless and event-driven concepts are modern techniques that often exist within cloud-native ecosystems but aren’t the four pillars themselves. Batch processing, relational databases, and manual processes describe older, heavier, and more hands-on workflows not aligned with cloud-native principles.

Cloud Native Architecture rests on building software as a set of independently deployable, scalable pieces that work well in dynamic environments. The set that lists microservices, containers, DevOps, and Continuous Delivery captures these foundational ideas: microservices break applications into small services that can be developed, deployed, and scaled independently; containers package each service with its runtime and dependencies so they run consistently across environments; DevOps emphasizes collaboration between development and operations with automation, monitoring, and infrastructure as code; and Continuous Delivery ensures automated, reliable build-test-deploy pipelines for frequent, safe releases. This combination enables agility, resilience, and scalable operation in the cloud.

The other options reflect traditional or unrelated approaches. Monoliths, virtual machines, SSH, and FTP signal a non–cloud-native pattern with less emphasis on rapid, automated deployment and containerized, service-based architecture. Serverless and event-driven concepts are modern techniques that often exist within cloud-native ecosystems but aren’t the four pillars themselves. Batch processing, relational databases, and manual processes describe older, heavier, and more hands-on workflows not aligned with cloud-native principles.