Your organization maintains a private Cloud DNS zone hosted in `vpc-shared-services` that resolves internal service domain names. A team deploying a separate workload in `vpc-analytics` needs their Compute Engine instances to resolve these internal DNS names without duplicating DNS records. Which configuration should you implement to enable internal DNS resolution from `vpc-analytics`?
- Create a Cloud DNS Peering zone associated with `vpc-analytics` that specifies `vpc-shared-services` as the target peer network.Cevap
- BDeploy a Global External HTTP(S) Load Balancer in `vpc-analytics` configured with a backend service targeting DNS port 53 in `vpc-shared-services`.
- CEnable the Cloud DNS API directly inside `vpc-analytics` and create a public DNS zone with the same private domain name.
- DModify the subnet CIDR ranges in `vpc-analytics` so they overlap with `vpc-shared-services` subnets to allow automatic DNS broadcast.
Cevap
Create a Cloud DNS Peering zone associated with `vpc-analytics` that specifies `vpc-shared-services` as the target peer network.
Cloud DNS Peering allows queries for private DNS zones to be forwarded from one VPC network (the querying network) to another VPC network (the peer network) where the private zone is authorized. Creating a DNS peering zone in `vpc-analytics` targeting `vpc-shared-services` allows `vpc-analytics` to resolve private records without needing direct authorization on the managed zone or duplicating record sets.
Adım Adım Çözüm
Anahtar Kavram
Cloud DNS Peering for Cross-VPC Private Zone Resolution
Tahmini Süre:1m 30s