Configurando o peering de rede VPC avaliações

Kit A. · Revisado há 3 months

Yareth O. · Revisado há 3 months

Srinivasarao K. · Revisado há 3 months

Rodrigo Joshua d. · Revisado há 3 months

Naimish P. · Revisado há 3 months

Abhinav K. · Revisado há 3 months

Oleksandr S. · Revisado há 3 months

Kai G. · Revisado há 3 months

Rohan C. · Revisado há 3 months

eduardo C. · Revisado há 3 months

Nargiz N. · Revisado há 3 months

Moushmi D. · Revisado há 3 months

Aydın M. · Revisado há 3 months

Vadim G. · Revisado há 3 months

good

Mahitha G. · Revisado há 3 months

Andrej O. · Revisado há 3 months

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. · Revisado há 3 months

Shweta A. · Revisado há 3 months

Yao W. · Revisado há 3 months

Igor B. · Revisado há 3 months

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. · Revisado há 3 months

i like

José Manuel R. · Revisado há 3 months

Abs K. · Revisado há 3 months

Rui V. · Revisado há 3 months

Shrija-Sunil D. · Revisado há 3 months