What is a key consideration when designing solutions for portability across cloud platforms?

Question

Options

• AUsing proprietary features specific to a single cloud provider
• BLeveraging containerization technologies like Docker and Kubernetes
• CDesigning applications that are tightly coupled to physical hardware
• DAvoiding automated deployment and management tools

• A
  8% (2)
• B
  83% (20)
• C
  4% (1)
• D
  4% (1)

Explanation

Containerization technologies like Docker and Kubernetes are the cornerstone of cloud portability because they package applications with all their dependencies into standardized units that run consistently across AWS, Azure, GCP, or any cloud environment. Option A is wrong because proprietary features lock you into a single vendor, the opposite of portability. Option C fails because tight coupling to physical hardware eliminates the abstraction layer that makes cloud migration possible in the first place. Option D is counterproductive - automated tools like Helm and CI/CD pipelines are precisely what enable repeatable, portable deployments across environments.

Memory tip: Think "containers = carry-on luggage" - your app fits in a standard-sized container that any airline (cloud provider) can load without special handling.

No community discussion yet for this question.