HTTP Load Balancer avaliações

Aakanksha P. · Revisado há over 3 years

Aprajita T. · Revisado há over 3 years

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

Prateek S. · Revisado há over 3 years

alexander de jesus p. · Revisado há over 3 years

Alexander B. · Revisado há over 3 years

CLAUDIA MILENA R. · Revisado há over 3 years

Karen F. · Revisado há over 3 years

Yudy Patricia G. · Revisado há over 3 years

Andrés Felipe M. · Revisado há over 3 years

Isaac A. · Revisado há almost 4 years

Nishith S. · Revisado há almost 4 years

Srinivas S. · Revisado há almost 4 years

Boominathan S. · Revisado há almost 4 years

Peeya I. · Revisado há almost 4 years

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. · Revisado há almost 4 years

NARENDRA N. · Revisado há almost 4 years

Amil G. · Revisado há almost 4 years

NARENDRA N. · Revisado há almost 4 years

It requires update of the console interface and fields.

Razvan S. · Revisado há almost 4 years

Ryk L. · Revisado há almost 4 years

RajagopalIyengar i. · Revisado há almost 4 years

Not enough time!!!!!

Chuck H. · Revisado há almost 4 years

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. · Revisado há almost 4 years

HJ L. · Revisado há almost 4 years