Cloud Digital Leader Why Cloud Technology Can Transform Business 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.

• ✗

  Reduced overall security risk

  Why it's wrong here

  A multi-cloud architecture spreads workloads across AWS, GCP, and Azure, each with distinct IAM models, networking constructs, and compliance controls. This expands the attack surface and forces organizations to maintain multiple credential stores, identity federations, and logging pipelines, increasing the chance of misconfiguration. Rather than reducing risk, security teams must reconcile shared responsibility models and enforce consistent policies across heterogeneous environments, which may create more risk than a single well-governed cloud.

• ✗

  Simplified operational management

  Why it's wrong here

  Multi-cloud environments inherently increase operational complexity by requiring distinct management tools, APIs, and governance policies for each cloud provider (e.g., AWS, GCP, Azure). This fragmentation directly contradicts the promise of simplified management, as teams must master multiple consoles and automation frameworks. The temptation arises because a single-cloud strategy—where a unified platform like Microsoft Entra ID centralises identity and access—does reduce overhead. In a homogeneous environment, centralised tooling genuinely simplifies operations, but multi-cloud’s heterogeneity prevents this.

• ✗

  Improved latency for all users

  Why it's wrong here

  Latency is determined by the physical distance between users and the chosen compute/storage regions, not by the number of cloud providers involved. If an application runs in one region of each provider, most users still traverse the public internet to reach that location, and spanning providers can introduce inter-cloud egress charges and extra network hops. To approach 'improved latency for all users' you need a global anycast or edge CDN architecture, which is possible in a single cloud and not guaranteed by multi-cloud adoption. Therefore, this statement mischaracterizes the operational reality.

• ✓

  Ability to use best-of-breed services from different providers

  Why this is correct

  With a multi-cloud strategy, you can deploy each workload on the platform that offers the strongest capability for its requirements—for example, using BigQuery for large-scale analytics, SageMaker for machine learning, and Azure's identity services in the same solution. This prevents being forced into a 'jack of all trades, master of none' situation where a single provider lacks a feature you need at the required scale or cost. The tradeoff is that best-of-breed services often expose proprietary APIs, so you must design for portability or accept some dependency at the service layer.

• ✓

  Reduced vendor lock-in

  Why this is correct

  By running components on multiple public clouds, an organization avoids tying its infrastructure to one vendor's pricing, roadmap, and proprietary technologies, retaining the negotiating power to switch or shift workloads as business conditions change. However, this benefit only materializes when you deliberately use portable abstractions such as Kubernetes, Open Policy Agent, or Terraform across providers; otherwise, you may become locked into a single cloud's managed services even within a nominally multi-cloud setup. Thus, reduced lock-in is a potential advantage, but not automatic.

Go deeper

Related to this question