HTTP Load Balancer Reviews

Aakanksha P. · Reviewed over 3 years ago

Aprajita T. · Reviewed over 3 years ago

Very satisfied. The step at the end might require a egress firewall rule to allow traffic to the public load balancer IP.

Prateek S. · Reviewed over 3 years ago

alexander de jesus p. · Reviewed over 3 years ago

Alexander B. · Reviewed over 3 years ago

CLAUDIA MILENA R. · Reviewed over 3 years ago

Karen F. · Reviewed over 3 years ago

Yudy Patricia G. · Reviewed over 3 years ago

Andrés Felipe M. · Reviewed over 3 years ago

Isaac A. · Reviewed almost 4 years ago

Nishith S. · Reviewed almost 4 years ago

Srinivas S. · Reviewed almost 4 years ago

Boominathan S. · Reviewed almost 4 years ago

Peeya I. · Reviewed almost 4 years ago

hardest lab yet, took 5 tries and half my weekend It should not take that long and the scoring did now work and there is no way to have lab check if it was done right

Amil G. · Reviewed almost 4 years ago

NARENDRA N. · Reviewed almost 4 years ago

Amil G. · Reviewed almost 4 years ago

NARENDRA N. · Reviewed almost 4 years ago

It requires update of the console interface and fields.

Razvan S. · Reviewed almost 4 years ago

Ryk L. · Reviewed almost 4 years ago

RajagopalIyengar i. · Reviewed almost 4 years ago

Not enough time!!!!!

Chuck H. · Reviewed almost 4 years ago

i got to the end of the lab THREE TIMES but was not able to deploy the 250 user attack from the Seige SSH instance - THREE TIMES... Instructions need to be updated. The instructions for the "Seige" attack on the Load Balancer has terrible instructions. It asks to pull up the IP Address - but it references a different GCP console UI than the current GCP console UI.. The instructions for the "Load Balancer" did not match the GCP UI console and was very time-consuming to figure it out . Please have someone Quality Check this Lab. It NEEDS to be updated with CLEARER instructions. Thank you.

Gloria D. · Reviewed almost 4 years ago

HJ L. · Reviewed almost 4 years ago