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 uses a hub-and-spoke topology in Google Cloud:
net-hub-project) connects to on-premises via Cloud Interconnect (global dynamic routing enabled), where corporate DNS hosts corp.example.com.app-host-project, connected to the Hub VPC via VPC Network Peering.payments service project team must independently manage private DNS records for payments.gcp.example.com for all VMs in the Spoke VPC, without creating a separate VPC or relying on host project admins.corp.example.com.Which Cloud DNS configuration should you implement?
corp.example.com in net-hub-project authorized for the Hub VPC, create a DNS peering zone for corp.example.com authorized for the Hub VPC targeting the Spoke VPC, and grant the payments team roles/dns.admin on app-host-project to manage payments.gcp.example.com in the host project.This configuration places a DNS peering zone on the Hub VPC targeting the Spoke VPC while centralizing all private DNS zone creation inside app-host-project by granting the payments service project team the DNS Administrator (roles/dns.admin) role on the Shared VPC host project.
corp.example.com in the Spoke VPC (which has no records or forwarding zone for it), leaving Spoke VPC VMs unable to resolve corp.example.com.roles/dns.admin on app-host-project gives the payments team permission to modify or delete DNS zones and policies belonging to other teams and core Shared VPC networking, forcing reliance on host-project governance rather than isolated service-project management.--target-network).dns.networks.targetWithPeeringZone permission (roles/dns.peer) on the producer network's project.roles/dns.admin on a Shared VPC host project.The DNS peering zone were reversed—authorized for the Spoke VPC and targeting the Hub VPC—and the payments zone were created in the payments service project using cross-project binding instead of granting roles/dns.admin on app-host-project.
corp.example.com in net-hub-project authorized for the Hub VPC targeting on-premises DNS servers, create a DNS peering zone for corp.example.com in app-host-project authorized for the Spoke VPC targeting the Hub VPC, and create a private zone for payments.gcp.example.com in the payments service project using cross-project binding to the Shared VPC.This architecture combines Cloud DNS outbound forwarding, Cloud DNS peering, and cross-project binding to deliver centralized hybrid DNS connectivity alongside decentralized, per-team private zone administration. Cross-project binding allows a Shared VPC service project to host and manage its own private Cloud DNS zone while attaching visibility directly to a Shared VPC network owned by a host project in the same Google Cloud organization.
corp.example.com: Authorizing a forwarding zone on the Hub VPC centralizes outbound DNS queries to on-premises resolvers through the Cloud Interconnect link. A DNS peering zone in app-host-project authorized for the Spoke VPC (the DNS consumer network) then forwards corp.example.com lookups to the Hub VPC (the DNS producer network), which executes forwarding according to its name resolution order.payments.gcp.example.com: Creating the private zone in the payments service project and specifying the Shared VPC network URL via cross-project binding lets the payments team manage records within their own project boundary while making them immediately resolvable by every VM in the Spoke VPC.dns.managedZones.create in their service project and dns.networks.bindPrivateDNSZone on app-host-project, avoiding broad host-project DNS admin permissions.35.199.192.0/19 via the Hub VPC.Because outbound DNS forwarding cannot traverse VPC Network Peering directly, pairing a centralized forwarding zone in the Hub VPC with a DNS peering zone on the Spoke VPC is the Google Cloud recommended pattern, while cross-project binding cleanly separates service-project DNS ownership from Shared VPC infrastructure.
payments.gcp.example.com in the payments service project restricted to the Shared VPC network.An outbound DNS server policy configures an alternative name server that intercepts all DNS queries from VMs in a VPC network. A Cloud DNS public zone publishes authoritative DNS records on Google's public name servers so they can be queried globally from the internet.
payments.gcp.example.com), peering zones, forwarding zones, or Compute Engine internal DNS (.internal) names.privateVisibilityConfig list of authorized VPC networks.You would use an outbound server policy only if every VM query had to be routed to on-premises resolvers for centralized filtering (with all internal zones hosted on-premises), and you would use a public zone only for internet-facing services—never for private Shared VPC workloads.
corp.example.com in app-host-project authorized for the Spoke VPC targeting on-premises DNS servers over VPC Network Peering, and create a private zone in app-host-project that delegates payments.gcp.example.com via NS records to a private zone in the payments service project.This option attempts to send outbound DNS forwarding traffic directly from the Spoke VPC across a VPC Network Peering link to on-premises resolvers, while relying on standard DNS NS record delegation inside a private zone to hand off subdomain authority to another project.
NS resource record sets. Attempting to delegate payments.gcp.example.com from a parent private zone in app-host-project using NS records is unsupported.35.199.192.0/19 and only accepts return traffic routed back to the VPC network where the forwarding zone originated.NS delegation records; subdomain matching relies instead on longest suffix matching across authorized private zones.This approach is invalid in Google Cloud regardless of minor tweaks; instead, you must place the forwarding zone on the Hub VPC, use a DNS peering zone from the Spoke VPC to the Hub VPC, and use cross-project binding for the payments private 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