Multi-region architecture patterns in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Active-Active Multi-Region Setup

In a multi-region architecture, what is the main advantage of an active-active setup compared to active-passive?

A It allows traffic to be served from multiple regions simultaneously, improving availability and reducing latency.

B It keeps one region completely offline until a failure occurs in the primary region.

C It requires manual failover to switch traffic between regions.

D It stores data only in one region to avoid replication delays.

💡 Hint

Think about how traffic is handled in both setups.

Active-active means multiple regions serve traffic at the same time, improving availability and latency. Active-passive keeps one region idle until failover.

❓ Architecture

intermediate

Choosing Data Replication Strategy

You want to design a multi-region system on GCP that keeps data consistent across regions with minimal delay. Which replication strategy fits best?

A Synchronous replication, where writes are confirmed only after all regions have the data.

B Asynchronous replication, where data is copied after the write is acknowledged.

C No replication, data is stored only in the primary region.

D Manual data export and import between regions daily.

💡 Hint

Consider consistency and delay trade-offs.

Synchronous replication ensures data is consistent across regions by confirming writes only after all regions have the data, minimizing inconsistency but may add latency.

❓ service_behavior

advanced

Impact of DNS Failover in Multi-Region Setup

In a multi-region architecture using DNS failover, what is a common limitation affecting failover speed?

A DNS failover only works if regions share the same IP address.

B DNS automatically detects region health instantly and switches traffic immediately.

C DNS failover requires manual intervention to update IP addresses.

D DNS caching by clients and resolvers can delay traffic switching to the healthy region.

💡 Hint

Think about how DNS caching works on the internet.

DNS caching by clients and resolvers can cause delays in failover because cached IP addresses may still point to the failed region until the cache expires.

❓ security

advanced

Securing Data in Multi-Region Replication

Which practice best secures data replicated across multiple GCP regions?

A Store data unencrypted to speed up replication.

B Encrypt data at rest and in transit using managed encryption keys.

C Use the same encryption key without rotation for all regions indefinitely.

D Disable network security to allow faster data transfer between regions.

💡 Hint

Consider encryption best practices for cloud data.

Encrypting data at rest and in transit with managed keys protects data confidentiality and integrity during replication across regions.

✅ Best Practice

expert

Designing for Disaster Recovery in Multi-Region Architecture

Which design choice best supports fast disaster recovery with minimal data loss in a multi-region GCP architecture?

A Use asynchronous replication with manual failover and no health monitoring.

B Rely on client-side retries to handle region failures without failover.

C Use synchronous replication with automated failover and health checks between regions.

D Keep backups only in the primary region and restore manually after failure.

💡 Hint

Think about automation and replication consistency for recovery speed.

Synchronous replication combined with automated failover and health checks enables quick recovery with minimal data loss by switching traffic automatically to a healthy region.

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