Google Cloud Armor ile Uygulama Yük Dengeleyicisi Yapılandırma Reviews

A O. · Reviewed 3 ay ago

PRISHA S. · Reviewed 3 ay ago

Nagasai G. · Reviewed 3 ay ago

25EU08R0327 - M. · Reviewed 3 ay ago

Isha G. · Reviewed 3 ay ago

Michelle w. · Reviewed 3 ay ago

Christian K. · Reviewed 3 ay ago

25EU05R0464 - B. · Reviewed 3 ay ago

25EU05R0006 - B. · Reviewed 3 ay ago

SWARNABHA G. · Reviewed 3 ay ago

Abhishek P. · Reviewed 3 ay ago

Nujhat Z. · Reviewed 3 ay ago

24J41A6712 - B. · Reviewed 3 ay ago

晨毓 ̇ ˇ ̇ 高. · Reviewed 3 ay ago

Varshitha A. · Reviewed 3 ay ago

Devon Patrick A. · Reviewed 3 ay ago

SAHIL K. · Reviewed 3 ay ago

24J41A1221 - D. · Reviewed 3 ay ago

一騎 山. · Reviewed 3 ay ago

FAVOUR A. · Reviewed 3 ay ago

Emmanuel O. · Reviewed 3 ay ago

Shaista M. · Reviewed 3 ay ago

Zoya K. · Reviewed 3 ay ago

Eugene K. · Reviewed 3 ay ago

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. · Reviewed 3 ay ago