CV0-004 Cloud Architecture and Design Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use each provider's native management tools

  Why it's wrong here

  Native tools per provider give two separate management planes, so operators still learn and maintain both AWS and Azure toolchains — the opposite of the single toolset required. It is tempting because native tooling exposes every provider-specific feature, and would be right if workloads were deliberately kept provider-idiomatic rather than unified.

• ✗

  Single cloud migration to one provider

  Why it's wrong here

  Consolidating onto one provider removes multi-cloud redundancy, which the stem explicitly requires for resilience. It is tempting because a single provider does yield one native toolset, and would be correct if the company prioritised simplified operations over running identical workloads across two clouds.

• ✓

  Multi-cloud using a cloud-agnostic orchestration tool

  Why this is correct

  A cloud-agnostic orchestration tool such as Terraform or Kubernetes abstracts provider-specific APIs, letting one toolset manage AWS and Azure workloads. This directly satisfies the requirement to simplify management across both clouds while preserving the redundancy architecture.

• ✗

  Hybrid cloud using VPN between AWS and Azure

  Why it's wrong here

  A VPN links AWS and Azure networks for connectivity, not management; it does nothing to unify the tooling used to operate workloads. It is tempting because hybrid connectivity is genuinely needed when workloads must exchange traffic across providers, and would be correct if the requirement were private cross-cloud data transfer rather than a single management toolset.