关于“开发 Google Cloud 网络：实验室挑战赛”的评价

Phil J. · 已于 about 2 years前审核

1DS21AI055 V. · 已于 about 2 years前审核

Rohan D. · 已于 about 2 years前审核

Pratham P. · 已于 about 2 years前审核

亮 柴. · 已于 about 2 years前审核

James W. · 已于 about 2 years前审核

DANISH N. · 已于 about 2 years前审核

HariKrishna S. · 已于 about 2 years前审核

The Lab didn't mention which Cloud SQL Instance Type i should use. I have use what was default then the lab closed warning me i am not following the Lab Instruction.

Ariful I. · 已于 about 2 years前审核

Kamel S. · 已于 about 2 years前审核

Muhammad H. · 已于 about 2 years前审核

Suhas B. · 已于 about 2 years前审核

Vitali K. · 已于 about 2 years前审核

1DS21AI019 H. · 已于 about 2 years前审核

us-centralを指定しないといけないのに、本文中がus-eastになっている。IAMのアクセス権を付与が押せない時があった

裕矢 米. · 已于 about 2 years前审核

Great lab. Although I finished with 4 minutes left on the timer due to it taking too long to create the Cloud SQL instance and Kubernetes cluster

Nermin S. · 已于 about 2 years前审核

Samruddhi G. · 已于 about 2 years前审核

HORACIO ADRIAN H. · 已于 about 2 years前审核

Lucimar S. · 已于 about 2 years前审核

What is most difficult about timed labs, is the fact that if you make an error on resources that take a long time to create and need a fixed name, is very difficult to ammend the error since deleting the resource is slow (in order to free the taken name), and then the need to reacrate the resource. Usually happens with eks containers.

Tomás C. · 已于 about 2 years前审核

rudy s. · 已于 about 2 years前审核

David d. · 已于 about 2 years前审核

Jorge Ulises S. · 已于 about 2 years前审核

Nayely P. · 已于 about 2 years前审核

not enough time. Unsure how to create uptime check monitor for wordpress service. Took several minutes for the Uptime check to be recognized as completed with the progress tracker. My first attempt I ran out of time, on my second attempt I have enough time for the checker to finally recognize it.

Jason R. · 已于 about 2 years前审核