An organization maintains a Cloud DNS private managed zone named `corp-internal-zone` that provides internal domain name resolution for workloads. The private zone is currently associated with a single Virtual Private Cloud (VPC) network named `vpc-analytics`. An operations engineer must extend DNS resolution for `corp-internal-zone` so that virtual machines in a second VPC network named `vpc-services` can also resolve these internal DNS records without removing access from `vpc-analytics`. Which `gcloud` command should the engineer run to accomplish this goal?
- gcloud dns managed-zones update corp-internal-zone --networks=vpc-analytics,vpc-servicesCevap
- Bgcloud dns managed-zones update corp-internal-zone --networks=vpc-services
- Cgcloud compute networks subnets update vpc-services --add-dns-zone=corp-internal-zone
- Dgcloud dns record-sets update corp-internal-zone --add-network=vpc-services
Cevap
The command `gcloud dns managed-zones update corp-internal-zone --networks=vpc-analytics,vpc-services` is correct because updating a private Cloud DNS zone's authorized VPC networks replaces the existing list with the values supplied to the `--networks` flag.
Updating a Cloud DNS private zone to authorize multiple VPC networks requires passing a complete, comma-separated list of all VPC networks to the `--networks` flag of `gcloud dns managed-zones update`. Including both `vpc-analytics` and `vpc-services` ensures both networks maintain private DNS resolution.
Adım Adım Çözüm
Anahtar Kavram
Cloud DNS Private Zone VPC Network Binding Management