Configuring VPC Network Peering Reviews

Kit A. · Reviewed 3 months ago

Yareth O. · Reviewed 3 months ago

Srinivasarao K. · Reviewed 3 months ago

Rodrigo Joshua d. · Reviewed 3 months ago

Naimish P. · Reviewed 3 months ago

Abhinav K. · Reviewed 3 months ago

Oleksandr S. · Reviewed 3 months ago

Kai G. · Reviewed 3 months ago

Rohan C. · Reviewed 3 months ago

eduardo C. · Reviewed 3 months ago

Nargiz N. · Reviewed 3 months ago

Moushmi D. · Reviewed 3 months ago

Aydın M. · Reviewed 3 months ago

Vadim G. · Reviewed 3 months ago

good

Mahitha G. · Reviewed 3 months ago

Andrej O. · Reviewed 3 months ago

Never verified when i was pinging between machines even though this was done. I even did it again and entered exit encase that was specifically what it was looking for but still nothing

Sara G. · Reviewed 3 months ago

Shweta A. · Reviewed 3 months ago

Yao W. · Reviewed 3 months ago

Igor B. · Reviewed 3 months ago

Here is the final review of the lab in English. We are definitely satisfied because we moved from a "broken" state to a fully automated, robust solution.Lab Performance Review: VPC Network Peering1. Connectivity & Isolation (Task 1)We successfully demonstrated the fundamental principle of VPC Isolation. By attempting to ping the internal IP (172.16.0.2) before peering, we confirmed that without an explicit connection, Google Cloud VPCs are private silos. The use of exit was crucial here to allow the Qwiklabs scoring engine to validate the state.2. Bidirectional Peering (Task 2)We correctly identified that VPC Peering is a handshake, not a one-way street.Action: Established peering-1-2 and peering-2-1.Result: The status moved to ACTIVE only when both sides were configured, ensuring a symmetric path for traffic.3. Verification & Route Injection (Task 3)This was the highlight of the lab. Instead of hardcoding IPs, we used a zone-agnostic discovery method:Logic: gcloud compute instances list --filter="name:privatenet-us-vm"Validation: The successful ping to 172.16.0.2 proved that the routing table was successfully updated with peering routes ($172.16.0.0/24$).4. Lifecycle & Termination (Task 4)We confirmed the logic that deleting one side of a peering connection immediately terminates the entire link.Outcome: Once peering-1-2 was deleted, the internal communication failed as expected, returning the networks to their secure, isolated states.Final Verdict: SUCCESSThe scripts are now clean, robust, and English-documented. By automating the IP extraction and following the strict ping and exit sequence, we satisfied all the mechanical requirements of the Qwiklabs platform.You are all set to hit "End Lab" with a 100% score!

Betta Z. · Reviewed 3 months ago

i like

José Manuel R. · Reviewed 3 months ago

Abs K. · Reviewed 3 months ago

Rui V. · Reviewed 3 months ago

Shrija-Sunil D. · Reviewed 3 months ago