Advanced Vocabulary #multi-cloud #cloud-strategy #finops #cloud-architecture

Multi-Cloud Strategy Vocabulary

5 exercises — vocabulary every cloud architect and platform engineer needs in English: vendor lock-in, workload placement, egress cost, data residency, active-active deployments, and multi-cloud governance.

Core multi-cloud vocabulary clusters

Strategy & risk: multi-cloud, vendor lock-in, cloud portability, abstraction layer, cloud-agnostic
Architecture: workload placement, active-active multi-cloud, failover cloud, latency-optimised routing
Compliance & governance: data residency, governance policy, cloud broker, cloud management platform (CMP)
Cost: egress cost, FinOps (multi-cloud), showback, chargeback, cost allocation
Tools: Terraform, Kubernetes, CloudHealth, Apptio, Morpheus, HashiCorp Terraform Cloud

0 / 5 completed

1 / 5

A cloud architect presents a new infrastructure proposal:
"We currently run everything on AWS, but we've become heavily dependent on their proprietary managed services — Aurora, SQS, Kinesis. Migrating away would cost millions and take over a year. The board wants us to adopt a multi-cloud strategy to reduce this risk."
What problem is the architect primarily describing?

2 / 5

An engineering manager explains a workload distribution decision:
"We run our ML training jobs on GCP because TPUs are the best option there. Our customer-facing API is on AWS because that's where our UK user base has the lowest latency. Our disaster-recovery environment sits on Azure. Each workload is placed on the cloud that suits it best."
Which multi-cloud concept does this describe?

3 / 5

A platform team presents its annual cloud cost review:
"Our AWS bill has an unexpected line item: $42,000 last month in egress charges. That's data we sent from AWS S3 to our GCP data warehouse. Every gigabyte leaving AWS costs $0.09. When we designed this multi-cloud architecture, we didn't account for the cost of moving data between providers."
What is egress cost in a multi-cloud context?

4 / 5

A compliance officer addresses the engineering team:
"For our NHS contract, patient data cannot leave UK soil. All processing must happen in UK regions. We also have EU customers whose data must stay within the EEA under GDPR. We need to ensure our multi-cloud architecture enforces these boundaries automatically — not just as a policy document."
What term describes the requirement that data must remain within a specific geographic territory?

5 / 5

A site reliability engineer explains a resilience architecture:
"We run our payment processing API simultaneously on both AWS eu-west-2 and GCP europe-west2. Both handle live traffic at all times — 60% AWS, 40% GCP. If AWS experiences an outage, our global load balancer shifts 100% of traffic to GCP within 30 seconds, with no manual intervention required."
What term describes this architecture?

Vocabulary Reference

Key terms from this exercise set — use this section to review before retrying or to consolidate your learning.

multi-cloud: A strategy of using two or more cloud providers (e.g., AWS, GCP, Azure) for different workloads, to avoid vendor lock-in, leverage best-of-breed services, and improve resilience.
vendor lock-in: Excessive dependence on a single cloud provider's proprietary APIs and managed services, making migration to another provider prohibitively expensive or complex.
cloud portability: The ability to move workloads between cloud providers with minimal rework. Achieved through containers, Kubernetes, and cloud-agnostic tooling such as Terraform.
abstraction layer: A software layer (e.g., Kubernetes, Terraform, a provider-neutral SDK) that hides cloud-provider-specific APIs, enabling the same code or configuration to run on multiple providers.
cloud-agnostic: Designed to work on any cloud provider without relying on proprietary features. A cloud-agnostic application or tool avoids hard dependencies on AWS-specific, GCP-specific, or Azure-specific services.
workload placement: The strategic decision of which cloud provider or region should host a given workload, based on available capabilities, cost, latency, and data residency requirements.
egress cost: The fee charged by a cloud provider when data is transferred out of its network. A significant hidden cost in multi-cloud architectures where data moves frequently between providers.
data residency: The legal or regulatory requirement that data is stored and processed only within a specified geographic territory (e.g., UK, EEA). Common in healthcare, finance, and government contracts.
active-active multi-cloud: An architecture where the same production workload runs concurrently across two or more cloud providers, each handling live traffic. Offers maximum resilience but requires data synchronisation and adds operational complexity.
cloud management platform (CMP): Software that provides a single pane of glass for managing infrastructure, costs, and governance policies across multiple cloud providers (e.g., HashiCorp Terraform Cloud, Morpheus, VMware Aria).

← Back to Vocabulary Exercises