Which combination of approaches is most effective for designing environments for multicloud deployments? (Select two)

Question

Options

• AUsing cloud-agnostic infrastructure as code tools for deployment
• BDesigning applications to use cloud-specific services and APIs
• CImplementing consistent security policies across all cloud environments
• DDeveloping custom deployment scripts for each cloud provider

• A
  81% (22)
• B
  11% (3)
• D
  7% (2)

Explanation

Using cloud-agnostic IaC tools (like Terraform or Pulumi) lets you define infrastructure once and deploy it across AWS, Azure, GCP, and others without rewriting everything - this is the core value proposition of multicloud. Consistent security policies ensure that your access controls, compliance requirements, and threat models don't develop dangerous gaps just because workloads live in different clouds.

Option B is wrong because deliberately using cloud-specific APIs and services creates vendor lock-in, which directly undermines the purpose of multicloud. Option D is wrong because custom scripts per provider multiply maintenance burden and introduce inconsistency - exactly what you're trying to avoid.

Memory tip: Think "SAME across clouds" - Same tooling (cloud-agnostic IaC), Same security. Anything that says "specific to one cloud" or "custom per cloud" is the wrong direction for a multicloud strategy.

No community discussion yet for this question.