Hi Piyush, Please review the answers below 1) False. Transitive Peering not allowed between VPC A & VPC C 2) roles/editor or roles/compute.networkadmin 3) False 4) True 5) VPC Peering between VPC A & B and VPC B & VPAC A should be created
Knowledge Check: 1. false. No transitive peering in GCP (and I believe the question is, is VPC A and VPC C are connected?) 2. roles/editor, roles/compute.networkAdmin 3. false - cannot be created btw different organisations. 4. true - VPC peering can work b/w different projects, or different organisations 5. peering configuration to be setup between A to B and B to A
Just clarifying- in case of transitive peering explanation, the example you took technically doesn't work right as VPC network C has conflicting CIDR range as A. so active peering is not possible between B and C in the first place right?
I need to have a external IP to customer put it in their firewall that will allow my cloud function to access their backend, do you have some tutorial to do it?
Hi Mayank, Great Catch! Looks like I made a typo with the CIDR range, as I was focusing on transitive peering, I forgot the overlapping CIDRs. Thanks for letting me know also, it shows that you understood VPC peering very well :) Good job!
Hi Piyush - thanks for the explaining such important concept in simple terms - but one query - in case of shared VPC - two attached service project 's vm - wants to talk to each other - how that can be achieved ? example - in one subnet - I kept application Vm & in other subnet I kept Data base - thus now I need to connect to DB from Application VM - please describe what is the way - Thanks !!
Hello, Sorry for the delay in response, I somehow missed the comment notification. Thank you very much for your valuable feedback! I am glad that you liked it :) Regarding your query: You can establish the connectivity between those two service projects by peering them together.
Hi Piyush, thank you for a great video, one question if I may, I read about the Gcp NCC, network connectivity center which should be used like the AWS transit gateway but for some reason nobody is referring to it in hub and spoke topology. Is there some limitations that prevent it from being used?
Thank you so much Naor for the amazing feedback! About the question, I havent got a chance to work with NCC yet however, the way I see it, people prefer shared VPC over hub and spoke as it provides high availability. With Hub being a single point of failure it could be a bottleneck. I could be wrong but I will try to get some more details on this and get back to you. Thanks again!
That's how the command expects the input. As the compute engine is part of a vpc, it will be created using that command, more details here cloud.google.com/sdk/gcloud/reference/compute/networks/create
#1.False (VPC A and VPC C)not peered automatically #2.roles/editor or roles/compute.networkadmin #3.False (Shared VPC created within the projects/organisation) #4.True (VPC Peering created b/w different organisation) #5.Create VPC Peering Connection b/w VPC A to VPC B and VPC B to VPC A
🔥 Check out our GCP playlist Namaste Google Cloud - Google Cloud Tutorial for beginners
th-cam.com/play/PLl4APkPHzsUXvkDFARdrH2LMESVqeuH8W.html
Hi Piyush, Please review the answers below
1) False. Transitive Peering not allowed between VPC A & VPC C
2) roles/editor or roles/compute.networkadmin
3) False
4) True
5) VPC Peering between VPC A & B and VPC B & VPAC A should be created
These are absolutely correct answers. Well done Nagendran!
Knowledge Check:
1. false. No transitive peering in GCP (and I believe the question is, is VPC A and VPC C are connected?)
2. roles/editor, roles/compute.networkAdmin
3. false - cannot be created btw different organisations.
4. true - VPC peering can work b/w different projects, or different organisations
5. peering configuration to be setup between A to B and B to A
Yes, these are the absolutely correct answers. You have nailed it.
thanks alot Piyush that helps a lot for beginners like me
I am glad you found it helpful Sanjiv!
Very useful and helpful, Thankyou sir
Most welcome :)
Just clarifying- in case of transitive peering explanation, the example you took technically doesn't work right as VPC network C has conflicting CIDR range as A. so active peering is not possible between B and C in the first place right?
Good catch, yes that was a mistake from my side.
I need to have a external IP to customer put it in their firewall that will allow my cloud function to access their backend, do you have some tutorial to do it?
Hello Raphael, check out my video on GCP networking, it should have the step to setup firewall rules.
Hi Piyush,
In Transitive Peering, You have used sam CIDR for VPC A and VPC C so it will also not work.
Hi Mayank, Great Catch! Looks like I made a typo with the CIDR range, as I was focusing on transitive peering, I forgot the overlapping CIDRs. Thanks for letting me know also, it shows that you understood VPC peering very well :) Good job!
@@TechTutorialswithPiyush yeah, Piyush. Thanks
Hi Piyush - thanks for the explaining such important concept in simple terms - but one query - in case of shared VPC - two attached service project 's vm - wants to talk to each other - how that can be achieved ? example - in one subnet - I kept application Vm & in other subnet I kept Data base - thus now I need to connect to DB from Application VM - please describe what is the way - Thanks !!
Hello, Sorry for the delay in response, I somehow missed the comment notification.
Thank you very much for your valuable feedback! I am glad that you liked it :)
Regarding your query: You can establish the connectivity between those two service projects by peering them together.
Hi Piyush, thank you for a great video, one question if I may, I read about the Gcp NCC, network connectivity center which should be used like the AWS transit gateway but for some reason nobody is referring to it in hub and spoke topology. Is there some limitations that prevent it from being used?
Thank you so much Naor for the amazing feedback! About the question, I havent got a chance to work with NCC yet however, the way I see it, people prefer shared VPC over hub and spoke as it provides high availability. With Hub being a single point of failure it could be a bottleneck. I could be wrong but I will try to get some more details on this and get back to you. Thanks again!
@@TechTutorialswithPiyush Thank you for your reply Piyush 🙏🏻
To create vpc through console why we are using "gcloud compute" ? How it is linked with gcloud and compute which is used for compute engine.
That's how the command expects the input. As the compute engine is part of a vpc, it will be created using that command, more details here
cloud.google.com/sdk/gcloud/reference/compute/networks/create
Valeu pelo vídeo aí mano
De nada. Fico feliz que tenha sido útil :)
#1.False (VPC A and VPC C)not peered automatically
#2.roles/editor or roles/compute.networkadmin
#3.False (Shared VPC created within the projects/organisation)
#4.True (VPC Peering created b/w different organisation)
#5.Create VPC Peering Connection b/w VPC A to VPC B and VPC B to VPC A
Your understanding is 100 % correct, good job.
Q 1.. False
Q 2.. Editor , Owner role of VPC Network are delete and create vpc peering
Q 3.. False
Q 4.. True
You are awesome my friend! Absolutely correct answers 🔥