Configuring an HTTP Load Balancer with Google Cloud Armor Reviews

MUHAMMED T. · Reviewed about 4 years ago

武 松. · Reviewed about 4 years ago

Rob C. · Reviewed about 4 years ago

Raul M. · Reviewed about 4 years ago

robert f. · Reviewed about 4 years ago

Pretty frustrating, but I'm unable to click the grey'd out "Add Target" for the Cloud Armor policy where I would input our backend target group. So after 2 hrs of diligently doing this, lab, I didn't pass :(

Kevin H. · Reviewed about 4 years ago

David S. · Reviewed about 4 years ago

MUHAMMED T. · Reviewed about 4 years ago

Patrick H. · Reviewed about 4 years ago

Apurv C. · Reviewed about 4 years ago

Justin D. · Reviewed about 4 years ago

No es posible agregar un destino al Cloud Armor, estaba deshabilitada la opción

Daniel Jonathan R. · Reviewed about 4 years ago

Ching S. · Reviewed about 4 years ago

Harry C. · Reviewed about 4 years ago

Mirza A. · Reviewed about 4 years ago

Mike M. · Reviewed about 4 years ago

Prashant T. · Reviewed about 4 years ago

Yingzhao O. · Reviewed about 4 years ago

Arturo G. · Reviewed about 4 years ago

Maxwell M. · Reviewed about 4 years ago

Mehdi A. · Reviewed about 4 years ago

erreur dans le lab

Marie L. · Reviewed about 4 years ago

Ziad K. · Reviewed about 4 years ago

last part is not up to date : if not choosing classic lb you cannot configure cloud armor without a trick and the solution is not validated

Sebastien S. · Reviewed about 4 years ago

be careful, to do task 6 you need to create classic load balancer instead of "HTTP(S) Load Balancer with Advanced Traffic Management" in task 5. If you don't, you won't be able to add a backend with cloud Armor

Florian L. · Reviewed about 4 years ago