关于“实现专用 Google 访问通道和 Cloud NAT”的评价

Mx L. · 已于 3 months前审核

Sebastian G. · 已于 3 months前审核

Joelson A. · 已于 3 months前审核

Fernando W. · 已于 3 months前审核

Luis Enrique J. · 已于 3 months前审核

Ryan F. · 已于 3 months前审核

Steven F. · 已于 3 months前审核

Mateusz N. · 已于 3 months前审核

Eleazar R. · 已于 3 months前审核

Felipe C. · 已于 3 months前审核

YAHIYA K. · 已于 3 months前审核

Gomanth Sai G. · 已于 3 months前审核

Umesh Chandra K. · 已于 3 months前审核

Vijay Ashok H. · 已于 3 months前审核

Vemula S. · 已于 3 months前审核

Piyush G. · 已于 3 months前审核

Bharath Rajiv R 2. · 已于 3 months前审核

Subject: Inaccuracies and technical hurdles in the lab instructions This lab contains several inaccuracies and "hidden" issues that result in significant time loss: 1. In Task 1, the instructions suggest connecting to the VM via SSH using the command: `gcloud compute ssh vm-internal --zone ZONE --tunnel-through-iap`. This command fails with an error because it requires a non-obvious step that isn't mentioned in the lab: disabling OS Login. The command only works after manually adding metadata to the instance: `gcloud compute instances add-metadata vm-internal --zone=ZONE --metadata=enable-oslogin=FALSE` 2. In the Cloud Console, after uploading an image to the bucket, the file does not appear in the object list until the "Refresh" button is manually clicked. The interface lacks auto-refresh, which is confusing. 3. The lab instructs the user to "Pin" the Network Services page by clicking a specific button. I spent a significant amount of time searching for this button, but it seems to have been replaced by the "Star" (Favorites) icon in the new UI. Either the interface has changed significantly or the instructions are outdated, despite the lab being marked as "recently updated."

Rostislav R. · 已于 3 months前审核

Jaswanth R. · 已于 3 months前审核

Manoj G. · 已于 3 months前审核

Sameera B. · 已于 3 months前审核

Habiba A. · 已于 3 months前审核

Arun S. · 已于 3 months前审核

Kalyani Satya Harshitha N. · 已于 3 months前审核

Russell M. · 已于 3 months前审核