Portfolio ↗

Landing Zones

A governed foundation of accounts, network, identity and guardrails.

4Questions
6Flashcards
3Terms
1Deliverables
Drill this topic All of Cloud Architecture
Questions

4 to work through

  1. intermediate

    An enterprise SaaS company grows from one cloud account to hundreds across many teams. What structure prevents this from becoming ungovernable, and what is the wrong way to impose it?

    2 min answer
  2. advanced

    A large enterprise is starting a cloud programme across dozens of business units with different regulatory obligations. What must the landing zone establish before the first workload, and what is the cost of getting it wrong?

    2 min answer
  3. advanced

    An organisation has 200 cloud accounts created ad hoc, with overlapping IP ranges and no consistent controls. Where do you start?

    2 min answer
  4. advanced

    An organisation is starting cloud adoption. Three teams want to deploy next month. What must exist first, and what can wait?

    2 min answer
Terminology

3 terms in this topic

practice

Account Vending

Automated creation of new cloud accounts pre-configured with the organisation's networking, identity, logging, guardrails and cost allocation.

 pattern

Landing Zone

The pre-built, policy-governed cloud foundation into which workloads are deployed — account structure, networking, identity, logging and guardrails.

 tool

Service Control Policy

An organisation-level guardrail that limits what any identity in an account may do, regardless of the permissions granted within that account.
Deliverables

1 artifact you would hand over

Deployment & Infrastructure View

Cloud Landing Zone Diagram

The account, network, identity and policy scaffolding every future workload will be dropped into, drawn before the first workload exists.
Cloud Architecture

Neighbouring topics

Cloud Architecture

General material on designing for cloud platforms.

8 quiz 16 cards 19 terms

Compute Models

Instances, containers and functions, and what each is priced and shaped for.

5 quiz 12 cards 5 terms

Cloud Storage

Object, block and file storage, and the access patterns each suits.

3 quiz 8 cards 4 terms

Cloud Databases

Managed relational, key-value, document and analytical services.

3 quiz 8 cards 3 terms

Containers

Images, registries, immutability and the deployment model they enable.

3 quiz 11 cards 5 terms

Kubernetes

The reconciliation loop, and whether the workload needs what it provides.

5 quiz 7 cards 4 terms

Serverless

Scale to zero, per-request billing, cold starts and connection limits.

4 quiz 11 cards 3 terms

Autoscaling

Signals, delays and bounds — and the maximum that caps a runaway bill.

5 quiz 7 cards 5 terms

Load Balancing

Distributing traffic, health checking, and removing failures from rotation.

3 quiz 8 cards 2 terms

Multi-Region Architecture

Surviving a region, and the data consistency price of doing so.

5 quiz 11 cards 6 terms

Availability Zones

The unit of correlated physical failure, and what zones do not protect against.

3 quiz 8 cards 3 terms

Disaster Recovery

Backup-restore, pilot light, warm standby and active-active postures.

2 quiz 10 cards 4 terms

Backup Strategies

Scope, immutability, separation, and the restore drill that makes it real.

4 quiz 8 cards 6 terms

Infrastructure as Code

Declarative infrastructure, drift, state files and rebuild-from-empty.

4 quiz 10 cards 3 terms

Managed Services

Which operational responsibilities actually transfer, and which do not.

3 quiz 10 cards 3 terms

Cloud Migration

Per-application disposition, sequencing and the capability change underneath.

3 quiz 8 cards 3 terms

Multi-Cloud

Best-of-breed, portfolio and portable — three very different costs.

3 quiz 5 cards 1 terms

Edge Computing

Moving compute towards the user, and what cannot follow it.

3 quiz 7 cards 2 terms

Cloud Governance

Preventive policy, tagging, quotas and cost and security guardrails.

4 quiz 11 cards 5 terms