Develop your Google Cloud Network: Challenge Lab Reviews

John M. · Reviewed about 2 years ago

Tetsuya H. · Reviewed about 2 years ago

1DS21AI055 V. · Reviewed about 2 years ago

Soumajit K. · Reviewed about 2 years ago

1DS21AI055 V. · Reviewed about 2 years ago

Phil J. · Reviewed about 2 years ago

1DS21AI055 V. · Reviewed about 2 years ago

Rohan D. · Reviewed about 2 years ago

Pratham P. · Reviewed about 2 years ago

亮 柴. · Reviewed about 2 years ago

James W. · Reviewed about 2 years ago

DANISH N. · Reviewed about 2 years ago

HariKrishna S. · Reviewed about 2 years ago

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. · Reviewed about 2 years ago

Kamel S. · Reviewed about 2 years ago

Muhammad H. · Reviewed about 2 years ago

Suhas B. · Reviewed about 2 years ago

Vitali K. · Reviewed about 2 years ago

1DS21AI019 H. · Reviewed about 2 years ago

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

裕矢 米. · Reviewed about 2 years ago

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. · Reviewed about 2 years ago

Samruddhi G. · Reviewed about 2 years ago

HORACIO ADRIAN H. · Reviewed about 2 years ago

Lucimar S. · Reviewed about 2 years ago

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. · Reviewed about 2 years ago