关于“在 Google Cloud 上实施云安全基础措施：实验室挑战赛”的评价

Rahul R. · 已于 5 days前审核

Shriharsh G. · 已于 5 days前审核

Yosuke K. · 已于 5 days前审核

Good

Janie H. · 已于 5 days前审核

Shankar S. · 已于 5 days前审核

Pravinkumar K. · 已于 5 days前审核

Rashmi C. · 已于 6 days前审核

The lab instructions were missing several prerequisites that cost significant time to work out. IAM permissions: the task never mentions that the jumphost service account needs roles/container.developer. Following the instructions as written produces a 403 on get-credentials, then a separate RBAC error on kubectl create. Neither is anticipated in the text. Quota: cluster creation fails with an IP address quota error using default settings. Nothing explains what consumes that quota or that a zonal single-node cluster is needed to stay under it. Console navigation: the four required flags are named only as gcloud flags, but the console labels them differently and has recently been redesigned. enable-private-nodes and enable-private-endpoint now sit in separate sections of the networking page, and enable-ip-alias is no longer exposed as a checkbox at all since VPC-native is the default. Mapping each flag to its current UI control took longer than the task itself. Either give the console labels alongside the flags, or state plainly that the task is intended to be done via gcloud. Each of these would be easy to pre-empt with a line in the setup section. As written, the lab tests navigation and troubleshooting more than the stated learning objective.

Sonny T. · 已于 6 days前审核

Satyam A. · 已于 6 days前审核

Sunghun K. · 已于 6 days前审核

Gideon A. · 已于 6 days前审核

Christopher E. · 已于 6 days前审核

GRATE

Rishabh s. · 已于 6 days前审核

Good Lab

Suki R. · 已于 6 days前审核

harshinisree G. · 已于 6 days前审核

Samhith V. · 已于 6 days前审核

Ambati Lakshmi P. · 已于 6 days前审核

Bhushan P. · 已于 6 days前审核

Rakshit G. · 已于 6 days前审核

Silvia S. · 已于 6 days前审核

Khushi S. · 已于 6 days前审核

Aryan D. · 已于 6 days前审核

Selvakumar K. · 已于 6 days前审核

Ekshith C. · 已于 6 days前审核

Foram B. · 已于 6 days前审核