Why load balancing matters in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use load balancing in cloud infrastructure?

Imagine you have a website that many people visit at the same time. What is the main reason to use load balancing?

A To store user data securely in a single server for faster access.

B To distribute user traffic evenly across multiple servers to prevent any single server from being overwhelmed.

C To increase the size of a single server's hard drive automatically.

D To reduce the number of servers needed by combining their power into one.

💡 Hint

Think about what happens when too many people try to use one server at once.

Load balancing helps by spreading the work across many servers. This keeps the website fast and reliable even when many users visit at the same time.

❓ service_behavior

intermediate

What happens if a server behind a load balancer fails?

In a cloud setup with a load balancer, if one server stops working, what does the load balancer do?

A It automatically stops sending traffic to the failed server and routes requests to healthy servers.

B It keeps sending traffic to the failed server until it is manually removed.

C It shuts down all servers to prevent errors.

D It duplicates the failed server to create a new one instantly.

💡 Hint

Think about how to keep the website working smoothly even if one server has a problem.

The load balancer checks server health and stops sending traffic to any server that is not responding. This keeps the service available by using only healthy servers.

❓ Architecture

advanced

Designing a scalable web application with load balancing

You want to design a web app that can handle sudden spikes in user traffic without slowing down. Which architecture best supports this?

A Use a single powerful server with a large CPU and memory to handle all traffic.

B Use multiple databases without load balancing to store user data.

C Use a load balancer to distribute traffic across multiple auto-scaled instances of the app servers.

D Use a load balancer but keep only one app server running at all times.

💡 Hint

Think about how to add or remove servers automatically based on traffic.

Using a load balancer with auto-scaling app servers allows the system to add more servers when traffic increases and remove them when traffic decreases, keeping performance steady and costs efficient.

❓ security

advanced

How does load balancing improve security in cloud services?

Which security benefit does a load balancer provide in a cloud environment?

A It replaces firewalls by blocking all incoming traffic by default.

B It encrypts all data stored on the servers automatically.

C It stores user passwords securely in the load balancer itself.

D It can help protect against denial-of-service (DoS) attacks by spreading traffic and filtering bad requests.

💡 Hint

Think about how spreading traffic can help handle attacks that flood servers.

Load balancers can detect unusual traffic patterns and distribute or block harmful traffic, helping to reduce the impact of DoS attacks and improve overall security.

✅ Best Practice

expert

Choosing the right load balancing method for global users

Your app has users worldwide. Which load balancing method best reduces latency by sending users to the closest server?

A Use geo-based load balancing that routes users to the nearest regional server.

B Use round-robin load balancing that sends requests in order to each server regardless of location.

C Use a single global server with a load balancer to handle all traffic.

D Use random load balancing that sends requests to any server randomly.

💡 Hint

Think about how to make the website faster for users far away from the main server.

Geo-based load balancing directs users to the closest server geographically, reducing delay and improving user experience worldwide.

Practice

1. Why is load balancing important in cloud infrastructure?

easy

A. It stores data permanently for backup purposes.

B. It encrypts data to secure communication.

C. It distributes incoming traffic evenly across multiple servers to prevent overload.

D. It monitors user activity for analytics.

Solution

1. Step 1: Understand the role of load balancing

   Load balancing helps distribute user requests evenly to multiple servers to avoid any single server from becoming overwhelmed.

2. Step 2: Compare with other options

   Options A, C, and D describe different cloud functions like storage, encryption, and monitoring, which are not related to load balancing.

3. Final Answer:

   It distributes incoming traffic evenly across multiple servers to prevent overload. -> Option C

4. Quick Check:

   Load balancing = traffic distribution [OK]

Hint: Load balancing spreads traffic to avoid server overload [OK]

Common Mistakes:

• Confusing load balancing with data storage
• Thinking load balancing encrypts data
• Assuming load balancing is for analytics

2. Which of the following is the correct way to configure a basic HTTP load balancer in GCP?

easy

A. Create a backend service, add instance groups, and set up a URL map.

B. Create a Cloud Storage bucket and upload files.

C. Enable Cloud Functions and write a trigger.

D. Set up a BigQuery dataset and run SQL queries.

Solution

1. Step 1: Identify load balancer components

   In GCP, an HTTP load balancer requires a backend service, instance groups as backends, and a URL map to route traffic.

2. Step 2: Eliminate unrelated options

   Options A, B, and C relate to data analytics, storage, and serverless functions, not load balancing setup.

3. Final Answer:

   Create a backend service, add instance groups, and set up a URL map. -> Option A

4. Quick Check:

   Load balancer setup = backend + instance groups + URL map [OK]

Hint: Load balancer needs backend service and URL map [OK]

Common Mistakes:

• Confusing load balancer setup with storage or functions
• Skipping URL map configuration
• Not adding instance groups as backends

3. Consider this simplified code snippet configuring a load balancer backend in GCP:

backend_service = create_backend_service()
add_instance_group(backend_service, 'group-1')
add_instance_group(backend_service, 'group-2')

requests = 100
handle_requests(backend_service, requests)

What is the expected behavior when 100 requests arrive?

medium

A. Requests are sent to a single instance in 'group-2' only.

B. All 100 requests go to 'group-1' only.

C. Requests are dropped because no URL map is set.

D. Requests are evenly distributed between 'group-1' and 'group-2'.

Solution

1. Step 1: Understand backend groups in load balancing

   When multiple instance groups are added to a backend service, the load balancer distributes incoming requests evenly among them.

2. Step 2: Analyze request handling

   With 100 requests and two groups, requests will be balanced roughly 50 each, not all to one group or dropped.

3. Final Answer:

   Requests are evenly distributed between 'group-1' and 'group-2'. -> Option D

4. Quick Check:

   Multiple backends = balanced requests [OK]

Hint: Multiple backends share traffic evenly [OK]

Common Mistakes:

• Assuming all traffic goes to one group
• Thinking requests drop without URL map
• Believing only one instance gets all requests

4. You set up a load balancer but notice all traffic is going to a single server, causing overload. What is the most likely cause?

medium

A. The health checks are passing for all instances.

B. The backend service has only one instance group attached.

C. The load balancer is configured with multiple backend groups.

D. The URL map is routing traffic evenly.

Solution

1. Step 1: Identify cause of uneven traffic

   If all traffic goes to one server, likely only one instance group is attached, so no distribution occurs.

2. Step 2: Check other options

   Multiple backend groups or even URL map routing would distribute traffic. Healthy instances mean traffic can be balanced.

3. Final Answer:

   The backend service has only one instance group attached. -> Option B

4. Quick Check:

   Single backend = no traffic distribution [OK]

Hint: One backend group means no load balancing [OK]

Common Mistakes:

• Assuming multiple backends cause overload
• Ignoring health check status
• Believing URL map causes single-server traffic

5. A company wants to ensure their web app stays available even if one server fails. They have three servers behind a load balancer. Which setup best achieves this goal?

hard

A. Use a load balancer with health checks and three backend servers in different zones.

B. Use a single server with a backup database.

C. Use three servers without a load balancer and rely on DNS round robin.

D. Use a load balancer but disable health checks to avoid false failures.

Solution

1. Step 1: Understand high availability requirements

   To stay available if one server fails, traffic must shift automatically to healthy servers in different zones.

2. Step 2: Evaluate options for failover

   Use a load balancer with health checks and three backend servers in different zones. uses load balancer with health checks and multi-zone servers, ensuring automatic failover and availability.

3. Step 3: Reject other options

   Use a single server with a backup database. lacks redundancy; Use three servers without a load balancer and rely on DNS round robin. lacks health checks and proper failover; Use a load balancer but disable health checks to avoid false failures. risks undetected failures by disabling health checks.

4. Final Answer:

   Use a load balancer with health checks and three backend servers in different zones. -> Option A

5. Quick Check:

   Health checks + multi-zone = high availability [OK]

Hint: Health checks + multi-zone servers ensure uptime [OK]

Common Mistakes:

• Disabling health checks thinking it helps
• Relying on DNS round robin alone
• Using single server for high availability