Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company is deploying an internal backend service hosted on Compute Engine virtual machines in a Virtual Private Cloud (VPC) network named vpc-production.
The service requires internal domain name resolution using the custom namespace corp.internal., and the DNS records must meet the following criteria:
vpc-production networkWhich Cloud DNS configuration should you implement to satisfy these requirements?
corp.internal., set visibility to private, and authorize the vpc-production network.A Cloud DNS managed private zone is a domain name service hosted within Google Cloud that provides authoritative name resolution exclusively to authorized Virtual Private Cloud (VPC) networks. Unlike public zones, private zones do not publish records to the global internet, keeping internal domain structures and IP assignments completely confidential.
private, the DNS records are only exposed within the Google Cloud internal network infrastructure.vpc-production network under the zone's private visibility configuration authorizes VMs within that specific VPC to query and resolve records in the corp.internal. namespace.A, AAAA, CNAME, and PTR records without operating dedicated DNS servers.Configuring a managed private zone bound to vpc-production directly addresses the core requirement of internal-only name resolution. It avoids exposing private network topology to the public internet while eliminating the operational overhead of deploying and maintaining custom DNS server infrastructure.
corp.internal., enable DNSSEC, and add standard A records pointing to the private IP addresses.A Cloud DNS managed public zone publishes DNS records to the global, publicly reachable internet. Anyone on the internet can query public zones through authoritative nameservers assigned by Cloud DNS.
vpc-production.The organization needed to host a publicly accessible website or external API endpoint that external users across the internet must resolve to public IP addresses.
corp.internal. and set the target to the default internet gateway.A Cloud DNS peering zone is a specialized private DNS zone type that forwards DNS lookups for a specific namespace from one VPC network to another VPC network that hosts the actual authoritative records.
A or CNAME records) directly; they merely send DNS requests to another VPC network that contains a managed private zone.The corp.internal. private zone were already hosted in a shared hub VPC, and VMs in vpc-production needed to resolve records hosted in that central hub VPC.
corp.internal. configured to forward queries to Google's public DNS resolvers.A Cloud DNS forwarding zone is a private zone configuration that instructs Cloud DNS to relay DNS queries for a specific domain name to external or on-premises target nameservers (such as Active Directory DNS or on-premises BIND servers).
8.8.8.8) have no knowledge of the private internal namespace corp.internal. and will return NXDOMAIN (domain does not exist) errors.A or AAAA records directly within Cloud DNS.The corp.internal. domain were authoritative on an existing on-premises DNS server, and VMs in Google Cloud needed to forward lookups over Cloud VPN to resolve those on-premises hostnames.
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