Your organization uses a Shared VPC architecture with a host project and three service projects. You have Compute Engine instances that reside in the service projects. You have critical workloads in…

Question

Options

• ACreate a Cloud DNS private forwarding zone in the host project of the Shared VPC that forwards
• BCreate a Cloud DNS private forwarding zone in the host project of the Shared VPC that forwards
• CConfigure a Cloud DNS private zone in the host project of the Shared VPC.
• DConfigure a Cloud DNS private zone in the host project of the Shared VPC.

• A
  79% (19)
• B
  4% (1)
• C
  13% (3)
• D
  4% (1)

Explanation

In a Shared VPC architecture, DNS resources that need to be accessible from all service projects should be created in the host project and associated with the Shared VPC network. To resolve on-premises hostnames, you need a Cloud DNS private forwarding zone - this zone forwards queries for the on-premises domain to the on-premises DNS resolvers (reachable via the Dedicated Interconnect). Placing the forwarding zone in the host project and binding it to the Shared VPC network ensures all service project instances inheriting that VPC can use it. A private zone (options C/D) would only work for names you manage in Cloud DNS, not for resolving names on on-premises DNS servers.

No community discussion yet for this question.