Configuring VPC Network Peering Ulasan

Kit A. · Diulas 3 bulan lalu

Yareth O. · Diulas 3 bulan lalu

Srinivasarao K. · Diulas 3 bulan lalu

Rodrigo Joshua d. · Diulas 3 bulan lalu

Naimish P. · Diulas 3 bulan lalu

Abhinav K. · Diulas 3 bulan lalu

Oleksandr S. · Diulas 3 bulan lalu

Kai G. · Diulas 3 bulan lalu

Rohan C. · Diulas 3 bulan lalu

eduardo C. · Diulas 3 bulan lalu

Nargiz N. · Diulas 3 bulan lalu

Moushmi D. · Diulas 3 bulan lalu

Aydın M. · Diulas 3 bulan lalu

Vadim G. · Diulas 3 bulan lalu

good

Mahitha G. · Diulas 3 bulan lalu

Andrej O. · Diulas 3 bulan lalu

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. · Diulas 3 bulan lalu

Shweta A. · Diulas 3 bulan lalu

Yao W. · Diulas 3 bulan lalu

Igor B. · Diulas 3 bulan lalu

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. · Diulas 3 bulan lalu

i like

José Manuel R. · Diulas 3 bulan lalu

Abs K. · Diulas 3 bulan lalu

Rui V. · Diulas 3 bulan lalu

Shrija-Sunil D. · Diulas 3 bulan lalu