Free PROFESSIONAL-CLOUD-NETWORK-ENGINEER Web TestEngine Demo

Q39 Single choice

You correctly configured Cloud DNS forwarding zones to point towards your on-premises DNS. You noticed that you cannot query your on-premises Active Directory main Domain Controller by using "dig ad.company.int" over your interconnect attachment. However, the query is successful if you directly target your on-premises DNS server by using "dig @10.10.10.53 ad.company.int". You need to correctly configure Cloud DNS so VMs and other resources can correctly resolve DNS records in your on-premises
DNS system.

What should you do?

A
Make sure that the Cloud DNS source range is advertised over your BGP sessions towards the on-premises environment, and that the on-premises ingress firewalls allow traffic from this range on port
53.
B
Change the local DNS server in your Google Cloud VMs from 169.254.169.254 to your on-premises service, 10.10.10.53.
C
Use a nslookup query instead of a dig query.
D
Add an egress firewall rule in your VPC to allow DNS traffic on port 53 that is destined to your on-premises DNS server.

PROFESSIONAL-CLOUD-NETWORK-ENGINEER Web TestEngine demo