Configurar um balanceador de carga de aplicativo com o Google Cloud Armor avaliações

247208 avaliações

Sparsh J. · Revisado há 7 months

Obscenamente enorme, não deu tempo para concluir.

Welington A. · Revisado há 7 months

BHAVYA B. · Revisado há 7 months

Carlos Alberto L. · Revisado há 7 months

Maheshwari c. · Revisado há 7 months

please fix the ssh authentication

AMAN K. · Revisado há 7 months

CHETAN M. · Revisado há 7 months

done eveyrything and the last checkpoint doesn't give points

Mateusz M. · Revisado há 7 months

BHAVYA B. · Revisado há 7 months

238R1A1254 S. · Revisado há 7 months

PREETESH S. · Revisado há 7 months

Needed to redo that, due:I am submitting feedback regarding the final validation step ("Denylist the siege-vm") in the "Application Load Balancer with Cloud Armor" lab. I was unable to achieve a 100/100 score due to an apparent issue with the grading script failing to recognize a correct configuration. What I encountered and fixed: Resource Exhaustion: I initially hit a strict ZONE_RESOURCE_POOL_EXHAUSTED error when trying to provision the required e2-micro in us-east1-c. After troubleshooting and waiting, I was eventually able to successfully provision the exact required machine type in the correct zone. Cloud Armor Configuration: I successfully created the denylist-siege security policy. I manually verified via the CLI that the rule was correctly configured to deny(403) the exact External IP of my siege-vm, utilizing the correct /32 CIDR notation. Backend Attachment: I verified via CLI (gcloud compute backend-services describe) that the security policy was properly attached to the global HTTP backend service. What I couldn't figure out (The Issue): Despite the siege-vm being the correct e2-micro instance in us-east1-c, the IP address matching perfectly, the /32 CIDR block being applied, and the policy being attached to the backend, the "Check my progress" button continually failed. I even verified the block was actively working (returning 403 errors), but the grading script remained stuck and would not award the final 25 points. It appears the script may have timed out or failed to register the final correct state after the initial hardware provisioning delays in the zone.

Tomáš K. · Revisado há 7 months

SWARGAM S. · Revisado há 7 months

Julio S. · Revisado há 7 months

Trisha G. · Revisado há 7 months

BHAVYA B. · Revisado há 7 months

could not complete it as it failed to start any VMs in the template due to lack of resources! Instance 'europe-west1-mig-5020' creation failed: The zone 'projects/qwiklabs-gcp-03-42db68c105ee/zones/europe-west1-d' does not have enough resources available to fulfill the request. Try a different zone, or try again later.

Simon M. · Revisado há 7 months

LUCKY C. · Revisado há 7 months

Hemanth S. · Revisado há 7 months

MARLAPATI NIKHIL S. · Revisado há 7 months

Gomez Lopez C. · Revisado há 7 months

no even after completing all the things its still havent uploaded in progress several times

Emamsahebgari S. · Revisado há 7 months

lab does not work properly

Fatih D. · Revisado há 7 months

LAKSHAY N. · Revisado há 7 months

Piyush V. · Revisado há 7 months

Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.