What is an objective statement for designing hybrid multicloud platform architectures?

Question

Options

• ATo maximize dependency on a single cloud provider's proprietary technologies
• BTo enable flexibility, scalability, and compliance across diverse cloud environments
• CTo design exclusively for the lowest common denominator features across clouds
• DTo focus on manual processes for deployment and management to ensure control

• A
  3% (1)
• B
  81% (25)
• C
  6% (2)
• D
  10% (3)

Explanation

Option B is correct because hybrid multicloud architectures are fundamentally designed to give organizations the freedom to run workloads across multiple cloud providers and on-premises environments, adapting to different compliance requirements, cost structures, and technical needs without lock-in.

Why the distractors fail:

• A is the opposite of hybrid multicloud's purpose - maximizing dependency on a single provider is vendor lock-in, which multicloud strategies explicitly aim to avoid.
• C designing for the "lowest common denominator" would cripple capability - good multicloud architecture leverages each platform's strengths, not its weakest shared feature set.
• D manual processes undermine the entire value proposition; automation and orchestration (IaC, CI/CD, policy-as-code) are essential to managing complexity across clouds at scale.

Memory tip: Think of the three pillars - Flexibility (choose the best cloud per workload), Scalability (grow across environments), Compliance (meet regional/regulatory rules). "FSC" = the reason multicloud exists. Any answer that restricts these three things is wrong.

No community discussion yet for this question.