Implementing a Hub and Spoke using NCC Reviews
3222 reviews
Dharani A. · Reviewed about 1 year ago
There is an issue with the last check. the pings are working but it's marked as failed
Said G. · Reviewed about 1 year ago
Said G. · Reviewed about 1 year ago
Great .. thanks 4 everything
Bayu Rahmat K. · Reviewed about 1 year ago
why the final task can't completed even i already have make a ping success ?
Bayu Rahmat K. · Reviewed about 1 year ago
Kazuhiro O. · Reviewed about 1 year ago
bad instructions on how to add spokes. will not give me credit for the connection between spoke1 and spoke2. i can ping both. but when I attempt the check mark to verify, it fails.
T.J. Y. · Reviewed about 1 year ago
The lab is wrong, the name of the VMs needs to be hub-vm , hub-vm1 and hub-vm2
Giovanni A. · Reviewed about 1 year ago
ZHIJUN C. · Reviewed about 1 year ago
Jairo M. · Reviewed about 1 year ago
Silvio C. · Reviewed about 1 year ago
Add more time to labs
Xiadani M. · Reviewed about 1 year ago
Silvio C. · Reviewed about 1 year ago
Kris B. · Reviewed about 1 year ago
done
Abhinay K. · Reviewed about 1 year ago
Luca A. · Reviewed about 1 year ago
Last check is broken
Juho T. · Reviewed about 1 year ago
Instructions needs updating as they do not match the GCP portal. Also, when checking my progress, my connectivity tests were not passing on the lab, even though i was getting successful pings. It may be because i named my spokes differently to the instructions
James K. · Reviewed about 1 year ago
Roberto P. · Reviewed about 1 year ago
Last lab checkpoint assessment failed to update to complete this lab
Tom H. · Reviewed about 1 year ago
The lab cannot be completed at present. In Step 5, it is asking for us to create the internal connection between the two spoke VMs, but does not give the information on how to complete that. I verified that the two VMs could ping each other, but the step will not mark itself complete. Also, in the firewall rules created when the lab is provisioned, one of the rules indicates it should be on spoke2, but is actually assigned to the spoke1-vpc.
Michael M. · Reviewed about 1 year ago
Aman C. · Reviewed about 1 year ago
Was unable to complete the lab despite being able to ping from each spoke VM to the other because I kept receiving the same error when I went to verify the last objective: "Please create the internal connection between 'spoke1-vm' and 'spoke2-vm'." Pings were successful in both directions.
Melissa S. · Reviewed about 1 year ago
Adrian D. · Reviewed about 1 year ago
Vimaldeep W. · Reviewed about 1 year ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.