
Before you begin
- Labs create a Google Cloud project and resources for a fixed time
- Labs have a time limit and no pause feature. If you end the lab, you'll have to restart from the beginning.
- On the top left of your screen, click Start lab to begin
Create multiple web server instances
/ 20
Configure the load balancing service
/ 35
Create an HTTP load balancer
/ 45
In a challenge lab you’re given a scenario and a set of tasks. Instead of following step-by-step instructions, you will use the skills learned from the labs in the course to figure out how to complete the tasks on your own! An automated scoring system (shown on this page) will provide feedback on whether you have completed your tasks correctly.
When you take a challenge lab, you will not be taught new Google Cloud concepts. You are expected to extend your learned skills, like changing default values and reading and researching error messages to fix your own mistakes.
To score 100% you must successfully complete all tasks within the time period!
Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources are made available to you.
This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials you use to sign in and access Google Cloud for the duration of the lab.
To complete this lab, you need:
You are a junior cloud engineer working as part of a team of cloud engineers that are assigned to provide network functionality to Compute Engine virtual machine (VM) instances on a Google Cloud Virtual Private Cloud (VPC) network.
Because you cannot create VM instances, containers, or App Engine applications without a VPC network, each Google Cloud project has a default network configured to get you started.
To support load balancing for the network traffic, you need to know the difference between a network load balancer and an HTTP load balancer and how to configure both for your applications running on Compute Engine VMs.
You are expected to have the skills and knowledge to complete the tasks that follow.
In this lab, you are asked to create an auto-mode VPC network with firewall rules and three VM instances. Then, you need to configure load balancing to explore the connectivity for the VM instances.
You need to:
Some standards you should follow:
Each task is described in detail below, good luck!
For this task, you need to create three Compute Engine VM instances using the configuration that follows, install Apache on them, and then add a firewall rule that allows HTTP traffic to reach the instances.
Set the following values, leaving all others at their defaults:
Property | Value (type value or select option as specified) |
---|---|
VM Instance -1 | web1 |
VM Instance -2 | web2 |
VM Instance -3 | web3 |
Region | |
Zone | |
Series | E2 |
Machine type | e2-small |
Tags | network-lb-tag |
image-family | debian-11 |
image-project | debian-cloud |
Use the following script for installing Apache on each server (updating web
to match the VM name):
curl
, replacing [IP_ADDRESS] with the IP address for each of your VMs:
Click Check my progress to verify the objective.
For this task, you need to create the resources that support the load balancing service.
Set the following values, leaving all others at their defaults:
Property | Value (type value or select option as specified) |
---|---|
Static external IP | network-lb-ip-1 |
Target-pool | www-pool |
Ports | 80 |
Once the load balancing service is configured, start sending traffic to the forwarding rule and watch the traffic be dispersed to different instances.
Click Check my progress to verify the objective.
For this task, you need to create resources for the HTTP load balancer.
Set the values as follows, leaving all others at their defaults:
Property | Value (type value or select option as specified) |
---|---|
Backend Template | lb-backend-template |
tags | allow-health-check |
Managed instance group | lb-backend-group |
machine-type | e2-medium |
image-family and image-project | same as previously created VMs |
fw-allow-health-check | fw-allow-health-check |
Allow source-ranges | 130.211.0.0/22, 35.191.0.0/16 |
Traffic | ingress |
Port | 80 |
external IP address | lb-ipv4-1 |
health check | http-basic-check |
URL map | web-map-http |
Target http proxy | http-lb-proxy |
Click Check my progress to verify the objective.
In the console, from the Navigation menu, go to Network services > Load balancing.
Click on the load balancer that you just created (web-map-http
).
To verify that the VMs are available, test the load balancer using a web browser. Navigate to http://IP_ADDRESS/
and replacing IP_ADDRESS
with the load balancer's IP address (for example, 35.241.29.40
).
Page served from: lb-backend-group-xxxx
).You have successfully set up a VPC consisting of three VMs, configured a load balancer, and practiced testing the network traffic.
...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.
Manual Last Updated June 8, 2023
Lab Last Tested June 8, 2023
Copyright 2025 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.
This content is not currently available
We will notify you via email when it becomes available
Great!
We will contact you via email if it becomes available
One lab at a time
Confirm to end all existing labs and start this one