Configuring Network Connectivity Center as a Transit Hub Reviews

Mohinder R. · Reviewed 5 months ago

Way too long.... Why not just configure all this using cloud shell? This is kind of ridiculous.

Christopher H. · Reviewed 5 months ago

Bad indications

Domiciano A. · Reviewed 5 months ago

Prashant S. · Reviewed 5 months ago

Ahmed H. · Reviewed 5 months ago

Levin Madhu Sudhan M. · Reviewed 5 months ago

Shahbaz Ikram B. · Reviewed 5 months ago

Andrey R. · Reviewed 5 months ago

The info was wrong for vpc-b-vm-1 in the spreadsheet. It caused some confusion when it didn't work the first time.

Dirk P. · Reviewed 5 months ago

Dirk P. · Reviewed 5 months ago

Justin R. · Reviewed 5 months ago

Ramkumar D. · Reviewed 5 months ago

Prabhu V. · Reviewed 5 months ago

Juan Ramon V. · Reviewed 5 months ago

Daman K. · Reviewed 5 months ago

Need to use better naming convention. Also tunnels should be numbers 1,2,3,4 ....also ther aer some typos making it even more confusing.

Vimal P. · Reviewed 5 months ago

Anindya S. · Reviewed 5 months ago

Sergei L. · Reviewed 5 months ago

Hymavathi l. · Reviewed 5 months ago

Vimal P. · Reviewed 5 months ago

This Lab can not be completed. The VPC and region mapping is messed. vm1 expected in us east region , to be created in vpc a, where as in vpc a there is only one subnet in us east region.

Pravin B. · Reviewed 5 months ago

Xavier R. · Reviewed 5 months ago

Task with vpc-b-vm-1 is not clear. It tells user to create vm in the same zone as vpc-a-vm-1. In this case it is impossible to connect vpc-b-vm-1 to vpc-b. Instruction has to be updated to use the same region as vpc-b is using.

Bruno S. · Reviewed 5 months ago

Piotr K. · Reviewed 5 months ago

Kartik G. · Reviewed 5 months ago