Examkin

Question

Difficulty: HardDeploying Cloud Load Balancers and Configuring Cloud DNS

Your company manages two separate Virtual Private Cloud (VPC) networks, `corp-app-vpc` and `corp-services-vpc`, within the same Google Cloud project. You have configured a Cloud DNS private zone named `internal.dev.example.com` that is currently visible only to resources in `corp-app-vpc`. Virtual machines deployed in `corp-services-vpc` need to resolve domain names hosted within this private zone without deploying custom DNS forwarding proxy instances. What should you do to allow `corp-services-vpc` to resolve records in `internal.dev.example.com`?

  1. Update the existing Cloud DNS private zone `internal.dev.example.com` to add `corp-services-vpc` to its list of authorized networks.Answer
  2. B
    Enable the Cloud DNS API within the subnet configuration settings of `corp-services-vpc` to allow cross-VPC API inheritance.
  3. C
    Configure an Organization Policy at the project root level to automatically delegate DNS zone resolution inheritance down to all subnets.
  4. D
    Deploy a Network Passthrough Load Balancer in `corp-app-vpc` to load balance incoming DNS traffic from `corp-services-vpc`.

Answer

Update the existing Cloud DNS private zone `internal.dev.example.com` to add `corp-services-vpc` to its list of authorized networks.
In Google Cloud, a Cloud DNS private zone can be shared across multiple VPC networks in the same project or across projects. Adding `corp-services-vpc` to the list of authorized networks for the `internal.dev.example.com` private zone allows instances in `corp-services-vpc` to resolve private DNS records natively through Google Cloud's internal DNS service without deploying extra proxy infrastructure.

Step-by-Step Solution

1
Identify the requirement for cross-VPC private DNS resolution
Determine that VMs in `corp-services-vpc` need native name resolution for records defined in `internal.dev.example.com`.
Cloud DNS private zones are by default scoped only to the authorized VPC networks specified during or after zone creation.
2
Evaluate the native Cloud DNS configuration settings
Recognize that Cloud DNS allows attaching multiple VPC networks within the same project to a single private zone's authorized networks list.
Modifying the zone's authorized networks grants immediate name resolution access to the specified VPC without requiring extra proxy compute instances or load balancers.
3
Select the optimal configuration action
Add `corp-services-vpc` to the authorized networks parameter of `internal.dev.example.com`.
This action directly satisfies the operational requirement with minimal complexity and zero additional infrastructure overhead.

Key Concept

Cloud DNS Private Zone Authorization across Multiple VPC Networks
Rate this question

Topics

Deploying Cloud Load Balancers and Configuring Cloud DNS

More questions from this topic