Multi-region architecture patterns in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the primary region for a multi-region Cloud Storage bucket.

GCP

resource "google_storage_bucket" "multi_region_bucket" {
  name     = "my-multi-region-bucket"
  location = "[1]"
  storage_class = "MULTI_REGIONAL"
}

Drag options to blanks, or click blank then click option'

Aasia-east1

Bus-central1

Cus

Deurope-west1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a single region name instead of a multi-region name for the location.

The location for a multi-region bucket must be a multi-region name like us, not a single region like us-central1.

2fill in blank

medium

Complete the code to create a global load balancer forwarding rule for multi-region traffic.

GCP

resource "google_compute_global_forwarding_rule" "multi_region_lb" {
  name       = "multi-region-lb"
  target     = google_compute_target_http_proxy.http_proxy.[1]
  port_range = "80"
}

Drag options to blanks, or click blank then click option'

Aself_link

Bid

Cname

Durl

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'name' or 'id' instead of 'self_link' for the target field.

The target field requires the full self_link of the target HTTP proxy resource.

3fill in blank

hard

Fix the error in the backend service configuration for multi-region failover.

GCP

resource "google_compute_backend_service" "backend" {
  name                  = "multi-region-backend"
  protocol              = "HTTP"
  health_checks         = [google_compute_health_check.http_check.[1]]
  enable_cdn            = true
  failover_policy {
    disable_connection_draining = false
  }
}

Drag options to blanks, or click blank then click option'

Aname

Bself_link

Cid

Durl

Attempts:

3 left

💡 Hint

Common Mistakes

Referencing health checks by name instead of self_link.

The health_checks field expects a list of full resource URLs, so use self_link.

4fill in blank

hard

Fill both blanks to configure a Cloud DNS managed zone with geo-routing for multi-region traffic.

GCP

resource "google_dns_managed_zone" "geo_zone" {
  name        = "geo-zone"
  dns_name    = "example.com."
  description = "Managed zone with geo-routing"
  visibility  = "public"
  [1] = {
    [2] = "us-east1"
  }
}

Drag options to blanks, or click blank then click option'

Ageo_location

Bgeo_routing_policy

Cregion

Dlocation

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect block names like 'geo_location' or 'location' instead of 'geo_routing_policy' and 'region'.

The geo_routing_policy block configures routing by region, and inside it, the region specifies the target region.

5fill in blank

hard

Fill all three blanks to define a multi-region Cloud Spanner instance with regional configurations.

GCP

resource "google_spanner_instance" "multi_region_instance" {
  name        = "multi-region-instance"
  config      = "[1]"
  display_name = "Multi Region Instance"
  nodes       = [2]
  labels = {
    environment = "[3]"
  }
}

Drag options to blanks, or click blank then click option'

Anam-multi-region

Bregional-us-east1

Cnam-prod

Dregional-us-central1

E3

F5

Gprod

Hdev

Attempts:

3 left

💡 Hint

Common Mistakes

Using single-region configs for multi-region instances.

Setting nodes to too low a number like 3 for production.

Using 'dev' instead of 'prod' for production environment label.

The config for multi-region Cloud Spanner is typically a multi-region config like nam-multi-region. The nodes should be a number like 5 for capacity. The environment label is set to 'prod' for production.

Practice

1. What is the main benefit of using a multi-region architecture in cloud services?

easy

A. Improved availability and reduced latency for users

B. Lower cost by using only one data center

C. Simpler setup with fewer resources

D. Avoiding the use of load balancers

Solution

1. Step 1: Understand multi-region purpose

   Multi-region architecture places resources in different geographic locations to improve service reliability and speed.

2. Step 2: Identify benefits

   This setup reduces downtime and latency by serving users from the closest healthy region.

3. Final Answer:

   Improved availability and reduced latency for users -> Option A

4. Quick Check:

   Multi-region = availability + latency improvement [OK]

Hint: Multi-region means better uptime and faster access [OK]

Common Mistakes:

• Thinking multi-region reduces cost by using fewer resources
• Assuming it simplifies setup instead of adding complexity
• Believing load balancers are not needed

2. Which GCP service is commonly used as a global load balancer to route traffic to the nearest region?

easy

A. Cloud Functions

B. Cloud CDN

C. Cloud Storage

D. Cloud Load Balancing

Solution

1. Step 1: Identify global load balancer service

   Cloud Load Balancing in GCP can distribute traffic globally and route users to the closest healthy backend.

2. Step 2: Exclude other services

   Cloud Storage is for files, Cloud CDN caches content, Cloud Functions run code, none route traffic globally.

3. Final Answer:

   Cloud Load Balancing -> Option D

4. Quick Check:

   Global traffic routing = Cloud Load Balancing [OK]

Hint: Global traffic routing uses Cloud Load Balancing [OK]

Common Mistakes:

• Confusing Cloud CDN with load balancing
• Thinking Cloud Storage handles traffic routing
• Assuming Cloud Functions manage global traffic

3. Consider this setup: A multi-region app uses Cloud Load Balancing with backends in us-central1 and europe-west1. If us-central1 backend fails health checks, where will traffic go?

medium

A. Traffic stops until us-central1 recovers

B. Traffic routes to europe-west1 backend

C. Traffic routes randomly to any backend

D. Traffic routes to a single zone in us-central1

Solution

1. Step 1: Understand health checks in load balancing

   Cloud Load Balancing monitors backend health and stops sending traffic to unhealthy backends.

2. Step 2: Determine traffic routing on failure

   If us-central1 fails, traffic automatically shifts to healthy backends like europe-west1.

3. Final Answer:

   Traffic routes to europe-west1 backend -> Option B

4. Quick Check:

   Unhealthy backend traffic rerouted to healthy backend [OK]

Hint: Traffic goes only to healthy backends [OK]

Common Mistakes:

• Assuming traffic stops on failure
• Thinking traffic routes randomly
• Believing traffic stays in the same region despite failure

4. You deployed a multi-region app but users in Asia experience high latency. Which mistake likely caused this?

medium

A. Deploying backends in multiple continents

B. Enabling global load balancing

C. Using a single region in the US only

D. Configuring health checks properly

Solution

1. Step 1: Analyze latency cause

   High latency in Asia means traffic is routed far away, likely because no nearby region exists.

2. Step 2: Identify deployment mistake

   Using only a US region means no local backend for Asia users, causing delays.

3. Final Answer:

   Using a single region in the US only -> Option C

4. Quick Check:

   Single distant region causes high latency [OK]

Hint: No local region means high latency for distant users [OK]

Common Mistakes:

• Thinking global load balancing causes latency
• Assuming multiple continents always cause latency
• Ignoring health check configuration impact

5. You want to design a multi-region architecture for a global app that must stay online even if an entire region fails. Which setup best meets this requirement?

hard

A. Deploy app in multiple regions with global load balancing and health checks

B. Deploy app in one region with multiple zones and use regional load balancing

C. Deploy app in one zone only and use Cloud CDN

D. Deploy app in multiple zones within the same region without load balancing

Solution

1. Step 1: Understand high availability needs

   To stay online if a whole region fails, app must run in multiple regions, not just zones.

2. Step 2: Choose architecture with global load balancing

   Global load balancing routes traffic to healthy regions automatically, ensuring uptime.

3. Step 3: Exclude less resilient options

   Single region or zone setups fail if that region/zone goes down; Cloud CDN alone doesn't provide failover.

4. Final Answer:

   Deploy app in multiple regions with global load balancing and health checks -> Option A

5. Quick Check:

   Multi-region + global load balancing = high availability [OK]

Hint: Multi-region plus global load balancing ensures uptime [OK]

Common Mistakes:

• Relying on zones instead of regions for failover
• Using only regional load balancing for global failover
• Thinking Cloud CDN replaces multi-region deployment