Configuring an HTTP Load Balancer with Google Cloud Armor Reviews

Tristan G. · Reviewed over 6 years ago

Ian M. · Reviewed over 6 years ago

Aleksei K. · Reviewed over 6 years ago

Reihaneh T. · Reviewed over 6 years ago

Timothy Raymund M. · Reviewed over 6 years ago

GCP has been update several parameter name, example : CPU usage has been changed CPU Utilization. Qwiklabs must update this.

Hendra F. · Reviewed over 6 years ago

Mohibul M. · Reviewed over 6 years ago

Some menus are out of date but overall it was good

Dave D. · Reviewed over 6 years ago

Kanat N. · Reviewed over 6 years ago

Kanat N. · Reviewed over 6 years ago

Created firewall rule but it didn't work and didn't give me the credits

Neil L. · Reviewed over 6 years ago

Shondy A. · Reviewed over 6 years ago

gianpiero p. · Reviewed over 6 years ago

健太郎 井. · Reviewed over 6 years ago

Very good lab!

Thiago T. · Reviewed over 6 years ago

The Siege-VM public ip address kept on getting proxy NAT'd from it's public physical IP address to other ranges in the 35.0.0.0/8 and 130.0.0.0/8 ranges.... so the black list policy would not trigger a deny.... by trial and error added the ranges mentioned above for the source in the armor policy and was able to create the intended effect which was to block the siege-vm.

oscar q. · Reviewed over 6 years ago

Ed A. · Reviewed over 6 years ago

Nice Lab

Gaurav G. · Reviewed over 6 years ago

Nilesh M. · Reviewed over 6 years ago

Changhun H. · Reviewed over 6 years ago

cool

Wahyu E. · Reviewed over 6 years ago

Wahyu E. · Reviewed over 6 years ago

Zachary P. · Reviewed over 6 years ago

Harles P. · Reviewed over 6 years ago

Jeremiah C. · Reviewed over 6 years ago