Configurar um balanceador de carga de rede interno avaliações

Jay Anne J. · Revisado há almost 3 years

Bugra B. · Revisado há almost 3 years

Bartłomiej M. · Revisado há almost 3 years

Mohammed B. · Revisado há almost 3 years

Luis T. · Revisado há almost 3 years

Vivek M. · Revisado há almost 3 years

Jesitha D. · Revisado há almost 3 years

Nishihata R. · Revisado há almost 3 years

Kashini M. · Revisado há almost 3 years

Samiksha S. · Revisado há almost 3 years

Natnara C. · Revisado há almost 3 years

Emanuel T. · Revisado há almost 3 years

Abdul Aziz Qohar c. · Revisado há almost 3 years

Taj A. · Revisado há almost 3 years

Jonathan K. · Revisado há almost 3 years

Alfin S. · Revisado há almost 3 years

NAN G. · Revisado há almost 3 years

NICOLAS V. · Revisado há almost 3 years

Ankita M. · Revisado há almost 3 years

Vasu G. · Revisado há almost 3 years

Ragupathy R. · Revisado há almost 3 years

ACHRAF H. · Revisado há almost 3 years

RASHMI R. · Revisado há almost 3 years

the lab is misleading, if you follow the lab it will be red flag to qwiklabs, running the startup script in Task3 after enabling the firewall rules will push the CPU utilization over 80% and qwiklabs will end the lab thinking you are provisioning new VMs, but the VMs are provisioned because in the instance group there is autoscalaer on CPU utilization, the only way I found is to add NAT first then run the startup scripts then enable firewall rules, i.e: Task 2 -> Task 3 -> Task 1 -> Task 4 -> Task 5

Maher A. · Revisado há almost 3 years

Ricardo Mar S. · Revisado há almost 3 years