You are configuring the final elements of a migration effort where resources have been moved from on-premises to Google Cloud. While reviewing the deployed architecture, you noticed that DNS resolutio

Question

Options

• AEnsure that the operating systems of the Compute Engine instances are configured to send DNS
• BValidate that there is network connectivity to the on-premises environment and that the Compute
• CValidate that the Compute Engine instances are using the Metadata Service IP address as their
• DReview the existing Cloud DNS zones, and validate that there is a route in the VPC directing

• A
  12% (3)
• B
  4% (1)
• C
  80% (20)
• D
  4% (1)

Explanation

In Google Cloud, Compute Engine instances must use the metadata server IP (169.254.169.254) as their DNS resolver for Cloud DNS to function, including any DNS forwarding zones that route queries to on-premises DNS servers. If instances are configured to use a different DNS resolver (e.g., an external one), their queries never reach Cloud DNS and therefore never get forwarded to on-premises. Validating that instances use 169.254.169.254 is the first managed-service diagnostic step. Option A is not a managed service approach. Option B addresses connectivity but not the DNS misconfiguration. Option D (reviewing VPC routes) would be relevant to routing, not DNS resolver configuration.

No community discussion yet for this question.