What is a primary goal when designing solutions for portability in a hybrid multicloud environment?

Question

Options

• ATo lock in with a specific cloud provider's technology
• BTo utilize proprietary technologies as much as possible
• CTo ensure applications and data can move seamlessly between environments
• DTo increase the complexity of deployments

• A
  9% (4)
• B
  2% (1)
• C
  84% (38)
• D
  4% (2)

Explanation

Portability in a hybrid multicloud environment means designing applications and data so they can move freely across different cloud providers and on-premises infrastructure without being constrained by any single platform - making C the correct answer.

Why the distractors are wrong:

• A (lock-in with a specific provider) is the opposite of portability - vendor lock-in is the primary risk that portability strategies are designed to avoid.
• B (proprietary technologies) also undermines portability, since proprietary services tie you to one vendor's ecosystem and make migration costly or impossible.
• D (increasing complexity) is a side effect to minimize, not a goal - good portability design uses open standards and abstraction layers to reduce unnecessary complexity.

Memory tip: Think of portability as "packing light for the cloud" - you want your workloads in a standard suitcase (open standards, containers, Kubernetes) that fits any airline (cloud provider), not custom luggage that only one airline accepts.

No community discussion yet for this question.