When designing environments for multicloud deployments, what is a key consideration?

Question

Options

• AAvoiding the use of automation and orchestration tools
• BCreating tightly coupled system architectures
• CEnsuring application and data portability across cloud environments
• DPrioritizing the use of cloud-specific services that prevent interoperability

• A
  2% (1)
• B
  6% (3)
• C
  80% (39)
• D
  12% (6)

Explanation

Application and data portability (C) is the defining requirement of any multicloud strategy - if your workloads and data can't move freely between AWS, Azure, GCP, or a private cloud, you're not truly multicloud, you're just using multiple clouds independently and losing the resilience and flexibility benefits that justify the complexity.

Why the distractors fail:

• A is the opposite of good practice; automation (Terraform, Ansible, Kubernetes) is essential for managing the complexity of multiple cloud environments consistently.
• B tight coupling defeats the purpose - if Service A on AWS can't function without a proprietary AWS dependency, you can't shift that workload to GCP during an outage or cost spike.
• D cloud-specific proprietary services (vendor lock-in) directly undermine portability and interoperability, the exact opposite of a multicloud design goal.

Memory tip: Think of multicloud like a universal power adapter - the whole point is that your "device" (app/data) plugs into any outlet (cloud), so portability and interoperability must be designed in from the start, not bolted on later.

No community discussion yet for this question.