Configure an Application Load Balancer with Autoscaling Reviews

sucks the instructions on create frontend the interface is different and when I try to validate show a error, this is the result for no update these instructions

Miguel S. · Reviewed 10 days ago

Juan Manuel P. · Reviewed 10 days ago

can't connect with SSH VM

Miguel S. · Reviewed 10 days ago

Nasurudeen Z. · Reviewed 10 days ago

en el paso final se realizo la prueba de estres de balanceo de cargas pero el verificador final aparece como si no lo hhubiese completado pero en la consola se realizaron las pruebas

Kevin Julian C. · Reviewed 10 days ago

stress test portion seems to not function. After SSHing into the load balancer and stress testing. Once completed, I still did not get credit for doing so.

Ivan M. · Reviewed 10 days ago

Piotr D. · Reviewed 10 days ago

Diego G. · Reviewed 10 days ago

Iqbaal R. · Reviewed 10 days ago

Ankush P. · Reviewed 10 days ago

Ivan M. · Reviewed 10 days ago

Luiz H. · Reviewed 10 days ago

Sayali J. · Reviewed 10 days ago

Sakshi L. · Reviewed 10 days ago

Prajakta K. · Reviewed 10 days ago

Hilbert N. · Reviewed 10 days ago

instance groups steps are not working as mentioned in lab

Bavireddy S. · Reviewed 10 days ago

Akshay Gowda .. · Reviewed 10 days ago

Sanika K. · Reviewed 10 days ago

Ankit G. · Reviewed 10 days ago

Yarrayya Naidu V. · Reviewed 10 days ago

Vlad-Ioan S. · Reviewed 10 days ago

Arianne Tresor M. · Reviewed 10 days ago

Victor M. · Reviewed 10 days ago

I encountered repeated SSH authentication failures when connecting to Compute Engine VMs in the lab environment, even after enabling the required APIs and having correct IAM permissions. Issue: * `Permission denied (publickey)` when using `gcloud compute ssh` * VM status and IAM checks passed successfully * The issue appeared to be related to OS Login / SSH metadata configuration conflicts Resolution: * Disabled OS Login on the VM metadata: `enable-oslogin=FALSE` * Re-ran SSH with: `--force-key-file-overwrite` * SSH access then worked correctly This issue consumed significant troubleshooting time because the automated diagnostics reported “No issues found” while SSH authentication was still failing.

Roman H. · Reviewed 10 days ago