Which statement best describes the legacy product landscape in relation to cloud-native offerings?

Which statement best describes the legacy product landscape in relation to cloud-native offerings?

• A. Cloud-native multi-tenant features are delivered by legacy products with strong ROI.
• B. Legacy products are widely considered to have exceeded cloud capabilities.
• C. Legacy products, even when offered as hosted SaaS, are often weak on multi-tenancy and cloud-native features.
• D. Legacy products have no presence in IT operations.

Answer: (C)

The main idea is how legacy products compare to cloud-native offerings in a cloud environment. Even when legacy software is sold as hosted SaaS, it often keeps older architectural choices—monolithic design, limited isolation, and manual or semi-automated operations—that make true cloud-native benefits harder to realize. Cloud-native offerings are built for the cloud from the ground up: true multi-tenancy that securely serves many customers from the same runtime, containerized and scalable services, automated provisioning and scaling, resilient failure handling, and API-driven interactions. Because legacy approaches typically don’t fully adopt these patterns, they tend to be weaker on multi-tenancy and cloud-native features even when exposed as SaaS. The other statements don't fit the practical reality: legacy products aren’t generally deemed to have surpassed cloud capabilities, aren’t known for ROI-strong cloud-native features by default, and they absolutely have a presence in IT operations.

The main idea is how legacy products compare to cloud-native offerings in a cloud environment. Even when legacy software is sold as hosted SaaS, it often keeps older architectural choices—monolithic design, limited isolation, and manual or semi-automated operations—that make true cloud-native benefits harder to realize. Cloud-native offerings are built for the cloud from the ground up: true multi-tenancy that securely serves many customers from the same runtime, containerized and scalable services, automated provisioning and scaling, resilient failure handling, and API-driven interactions. Because legacy approaches typically don’t fully adopt these patterns, they tend to be weaker on multi-tenancy and cloud-native features even when exposed as SaaS. The other statements don't fit the practical reality: legacy products aren’t generally deemed to have surpassed cloud capabilities, aren’t known for ROI-strong cloud-native features by default, and they absolutely have a presence in IT operations.