关于“Configuring an HTTP Load Balancer with Google Cloud Armor”的评价

Tristan G. · 评论over 6 years之前

Ian M. · 评论over 6 years之前

Aleksei K. · 评论over 6 years之前

Reihaneh T. · 评论over 6 years之前

Timothy Raymund M. · 评论over 6 years之前

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

Hendra F. · 评论over 6 years之前

Mohibul M. · 评论over 6 years之前

Some menus are out of date but overall it was good

Dave D. · 评论over 6 years之前

Kanat N. · 评论over 6 years之前

Kanat N. · 评论over 6 years之前

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

Neil L. · 评论over 6 years之前

Shondy A. · 评论over 6 years之前

gianpiero p. · 评论over 6 years之前

健太郎 井. · 评论over 6 years之前

Very good lab!

Thiago T. · 评论over 6 years之前

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. · 评论over 6 years之前

Ed A. · 评论over 6 years之前

Nice Lab

Gaurav G. · 评论over 6 years之前

Nilesh M. · 评论over 6 years之前

Changhun H. · 评论over 6 years之前

cool

Wahyu E. · 评论over 6 years之前

Wahyu E. · 评论over 6 years之前

Zachary P. · 评论over 6 years之前

Harles P. · 评论over 6 years之前

Jeremiah C. · 评论over 6 years之前