Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization implements split-horizon DNS for services.example.com. using a Cloud DNS public managed zone and a private managed zone authorized for prod-vpc. An inbound DNS server policy on prod-vpc allows on-premises clients over Cloud Interconnect to resolve private records.
| Record | Public Zone | Private Zone |
|---|---|---|
api.services.example.com. | 203.0.113.10 | 10.10.1.10 |
portal.services.example.com. | 203.0.113.20 | (missing) |
status.services.example.com. | 203.0.113.30 | (missing) |
External internet clients resolve all three hostnames to their public IP addresses. However, Compute Engine VMs in prod-vpc and on-premises hosts receive NXDOMAIN for portal.services.example.com. and status.services.example.com. while resolving api.services.example.com. to 10.10.1.10.
How should you ensure internal VPC and on-premises clients resolve api.services.example.com. internally and the remaining hostnames to their public endpoints while maintaining identical zone namespaces?
A records for portal.services.example.com. (203.0.113.20) and status.services.example.com. (203.0.113.30) directly to the services.example.com. private managed zone.In a split-horizon DNS architecture using identical domain namespaces (services.example.com.), a Cloud DNS private managed zone completely overrides the corresponding public managed zone for every authorized VPC network. When a query originates from a VM in prod-vpc (via the metadata server 169.254.169.254) or from an on-premises host targeting the prod-vpc inbound DNS forwarder IP, Cloud DNS evaluates the VPC's name resolution order using longest suffix matching.
NXDOMAIN responses: Because services.example.com. is the longest matching suffix among authorized private zones, Cloud DNS treats that private zone as authoritative for the entire domain. If portal.services.example.com. or status.services.example.com. is missing from the private zone, Cloud DNS immediately returns NXDOMAIN without falling through to public DNS.A records (203.0.113.20 and 203.0.113.30) into the private zone ensures both internal VPC workloads and hybrid on-premises clients resolve those hostnames to their public endpoints while api.services.example.com. continues resolving to 10.10.1.10.203.0.113.10 for api.services.example.com. alongside the portal and status endpoints.services.example.com. queries to the prod-vpc inbound server policy automatically follow the exact same VPC name resolution order as prod-vpc VMs.Replicating the non-overridden public records into the private managed zone directly satisfies Cloud DNS's authoritative lookup behavior with zero additional infrastructure, preserves the single services.example.com. namespace across both horizons, and guarantees seamless resolution across cloud-native and hybrid clients.
NS records for portal.services.example.com. and status.services.example.com. in the services.example.com. private managed zone pointing to the public zone's authoritative name servers.In traditional DNS and Cloud DNS public zones, NS (Name Server) delegation allows a parent zone owner to delegate authority for a subdomain (such as portal.services.example.com.) to a separate set of authoritative name servers. Recursive resolvers follow those NS records to query the target servers for records under that subdomain.
NS resource record sets or delegating subdomains to external or public authoritative name servers.NS delegation records inside the services.example.com. private zone is rejected by the Cloud DNS API, leaving portal.services.example.com. and status.services.example.com. unresolved (NXDOMAIN) for both prod-vpc VMs and on-premises clients.169.254.169.254) and inbound DNS forwarders.NS records, Cloud DNS private zones do not support DNSSEC.portal.services.example.com.) to a different resolver from within a VPC, you must create a separate Cloud DNS forwarding zone or peering zone for that specific subdomain rather than using NS records inside a private zone.portal.services.example.com.) to a different public DNS provider or a separate Cloud DNS public managed zone.services.example.com. authorized for prod-vpc with standard routing targeting a public recursive resolver (8.8.8.8).A Cloud DNS forwarding zone is a specialized type of private zone that forwards DNS queries matching a specific domain suffix to target DNS name servers (such as on-premises resolvers or external public resolvers using standard routing) instead of storing resource record sets locally.
services.example.com. private managed zone and a services.example.com. forwarding zone to prod-vpc.8.8.8.8, internal VPC and on-premises clients would lose the private 10.10.1.10 mapping for api.services.example.com. and resolve it to the public IP 203.0.113.10.prod-vpc to delegate resolution of a distinct subdomain (such as portal.services.example.com.)—not the identical services.example.com. origin—to an external resolver while keeping services.example.com. as the parent private zone.prod-vpc specifying a public recursive resolver (8.8.8.8) as an alternative name server.A Cloud DNS outbound server policy overrides the standard VPC name resolution order by redirecting all DNS queries from VMs in the attached VPC network to specified alternative name servers (such as on-premises BIND or Active Directory resolvers, or external DNS appliances).
8.8.8.8 bypasses the services.example.com. private zone completely, causing internal VMs to resolve api.services.example.com. to 203.0.113.10 instead of 10.10.1.10.NXDOMAIN; they replace Cloud DNS private zone evaluation entirely.prod-vpc also lose the ability to resolve Compute Engine internal DNS names (.internal) and any forwarding or peering zones attached to the VPC.NXDOMAIN response.services.example.com. zone.Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated