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

A O. · Revisado há 3 months

PRISHA S. · Revisado há 3 months

Nagasai G. · Revisado há 3 months

25EU08R0327 - M. · Revisado há 3 months

Isha G. · Revisado há 3 months

Michelle w. · Revisado há 3 months

Christian K. · Revisado há 3 months

25EU05R0464 - B. · Revisado há 3 months

25EU05R0006 - B. · Revisado há 3 months

SWARNABHA G. · Revisado há 3 months

Abhishek P. · Revisado há 3 months

Nujhat Z. · Revisado há 3 months

24J41A6712 - B. · Revisado há 3 months

晨毓 ̇ ˇ ̇ 高. · Revisado há 3 months

Varshitha A. · Revisado há 3 months

Devon Patrick A. · Revisado há 3 months

SAHIL K. · Revisado há 3 months

24J41A1221 - D. · Revisado há 3 months

一騎 山. · Revisado há 3 months

FAVOUR A. · Revisado há 3 months

Emmanuel O. · Revisado há 3 months

Shaista M. · Revisado há 3 months

Zoya K. · Revisado há 3 months

Eugene K. · Revisado há 3 months

Hello, I would like to report what appears to be an autograder issue with this lab. This is the second time I have restarted and completed the entire lab from the beginning, and I am getting the exact same result. The only task that does not validate is: "Please create a security policy with the required deny rule for the VM IP." I carefully verified every required step: Created the VM siege-vm in the correct zone. Installed siege successfully. Created the Cloud Armor security policy denylist-siege. Configured the default rule to Allow. Added the required deny (403) rule for the VM external IP using /32. Attached the policy to the http-backend backend service. Verified that the backend service is using the security policy. Verified that the deny rule matches the current external IP of siege-vm. Tested the policy from siege-vm: curl -I http://<LB_IP> returns HTTP/1.1 403 Forbidden. siege requests are blocked with Connection reset by peer. These tests confirm that Cloud Armor is working correctly and that the deny rule is being enforced. Despite this, the autograder continues to report: "Please create a security policy with the required deny rule for the VM IP." I have already restarted the lab twice, spent more than two hours troubleshooting, and used additional lab credits because of this issue. Could you please review the autograder or manually validate this task? If this is a platform issue, I would also appreciate a credit reimbursement since I had to restart the lab multiple times due to the same problem. Thank you for your assistance.

JOSE R. · Revisado há 3 months