Answer-first summary for fast verification
Answer: Set up a Cloud DNS zone, designate its visibility as private, link it to your VPC, and register each instance's record within this zone.
The correct approach involves creating a Cloud DNS zone with private visibility and associating it with your VPC to register internal DNS records for each instance. This method aligns with Google's recommendations by leveraging Cloud DNS for internal service discovery without the need for external DNS servers or unnecessary VPC configurations. Custom hostnames do not fulfill the requirement for a custom DNS zone. Deploying a BIND DNS server, while possible, is not recommended as Cloud DNS provides the necessary functionality. Creating a new VPC and configuring two DNS zones is overly complex and does not facilitate communication between VPCs without peering.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
To ensure service discovery within your VPC by associating each Compute Engine instance with an internal DNS record in a custom zone, adhering to Google's recommended practices, what is the best approach?
A
Deploy a BIND DNS server within the VPC, establish a Cloud DNS forwarding zone to direct DNS queries to BIND, and register each instance's record in the BIND DNS server.
B
Establish a new VPC, restrict all external access via a firewall rule, and configure two Cloud DNS zones—one in the new VPC and another in the primary VPC that forwards requests to the first. Register each instance's record in the initial zone.
C
Configure your Compute Engine instances with custom hostnames.
D
Set up a Cloud DNS zone, designate its visibility as private, link it to your VPC, and register each instance's record within this zone.