Which practice improves portability of cloud-native applications across different clouds?

Which practice improves portability of cloud-native applications across different clouds?

• A. Vendor lock-in
• B. Portability across public, private, and hybrid clouds
• C. Monolithic architecture
• D. Heavy reliance on a single provider

Answer: (B)

Designing for portability across clouds means building cloud-native apps so they can run with little to no change on different cloud environments. This is achieved by using portable runtimes (like Kubernetes), containerized workloads, and cloud-agnostic tooling and configurations. Externalize state where possible, and avoid relying on provider-specific services or APIs. With these practices, the same application can be deployed across public, private, and hybrid clouds, enabling multi-cloud or hybrid strategies and reducing dependency on a single vendor. Choosing vendor lock-in increases dependence on one provider and hurts portability. A monolithic architecture makes moving between environments harder due to tight coupling. Heavy reliance on a single provider likewise limits where you can run the app.

Designing for portability across clouds means building cloud-native apps so they can run with little to no change on different cloud environments. This is achieved by using portable runtimes (like Kubernetes), containerized workloads, and cloud-agnostic tooling and configurations. Externalize state where possible, and avoid relying on provider-specific services or APIs. With these practices, the same application can be deployed across public, private, and hybrid clouds, enabling multi-cloud or hybrid strategies and reducing dependency on a single vendor.

Choosing vendor lock-in increases dependence on one provider and hurts portability. A monolithic architecture makes moving between environments harder due to tight coupling. Heavy reliance on a single provider likewise limits where you can run the app.