A Cloud Engineer is managing a network setup where two Virtual Private Cloud networks, `vpc-analytics` and `vpc-core`, are connected using VPC Network Peering. Custom static routes created in `vpc-analytics` are currently not propagating to virtual machines in `vpc-core`. Which two actions must be taken using `gcloud compute networks peerings` to allow custom static routes to be properly exchanged between these two peered networks? (Select TWO.)
- Update the peering connection configuration in `vpc-analytics` to enable the `--export-custom-routes` flag.Cevap
- Update the peering connection configuration in `vpc-core` to enable the `--import-custom-routes` flag.Cevap
- CUpdate the peering connection in both VPC networks to set the `--auto-create-subnetworks` flag.
- DLower the priority numerical value on default ingress firewall rules to force route propagation across peering boundaries.
Cevap
To successfully exchange custom static routes between peered VPC networks, the sending network must update its peering configuration to export custom routes (`--export-custom-routes`), and the receiving network must update its peering configuration to import custom routes (`--import-custom-routes`).
In Google Cloud VPC Network Peering, custom static routes are not shared automatically. Exchanging custom routes requires a two-sided configuration: the peer network originating the routes (`vpc-analytics`) must set `--export-custom-routes`, and the receiving network (`vpc-core`) must set `--import-custom-routes`.
Adım Adım Çözüm
Anahtar Kavram
VPC Network Peering Custom Route Exchange