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 Shared VPC (shared-vpc) in host-project with workloads in service-project-a and Cloud Interconnect VLAN attachments terminating in shared-vpc. You manage private zones authorized for shared-vpc and a managed public zone in service-project-a.
You must satisfy these requirements:
shared-vpc private DNS lookups and external queries to the managed public zone, viewing logs in the owning project.Which configuration should you implement?
host-project, create a single DNS server policy attached to shared-vpc with both inbound query forwarding and DNS logging enabled, and keep alternative name servers unconfigured. In service-project-a, enable query logging directly on the managed public zone, and view shared-vpc DNS logs in host-project.A Cloud DNS server policy is a VPC-level configuration resource that controls inbound DNS forwarding, outbound alternative name servers, and private DNS query logging for an attached VPC network. Because a VPC network can reference at most one DNS server policy, combining inbound query forwarding and DNS logging into a single policy on shared-vpc enables hybrid resolution and comprehensive private DNS auditing without disrupting internal name resolution.
DNS_RESOLVER addresses) from subnet primary ranges in shared-vpc. On-premises resolvers reachable over Cloud Interconnect can query these internal entry points to resolve authorized private zones, forwarding zones, peering zones, and Compute Engine internal DNS, while private zones remain completely invisible to the public internet.service-project-a to resolve private zones and Compute Engine internal DNS names (169.254.169.254).host-project because it owns the network. Enabling --log-dns-queries directly on the managed public zone in service-project-a captures external internet queries against that public zone.53 traffic without requiring VPC firewall rules.host-project for security and troubleshooting.This architecture respects Cloud DNS resource boundaries by placing network-scoped server policies in the Shared VPC host project and zone-scoped logging on the public zone, avoiding service disruptions caused by outbound alternative name servers or unsupported peering topologies.
host-project, create one DNS server policy on shared-vpc with inbound query forwarding enabled, and create a second DNS server policy on shared-vpc with DNS logging enabled for both private and public zones. Add an ingress VPC firewall rule on shared-vpc allowing TCP and UDP port 53 from on-premises CIDR blocks to the inbound forwarder entry point IP addresses.This approach attempts to separate inbound forwarding and query logging into two independent DNS server policies on shared-vpc, relies on a server policy to log a managed public zone, and attempts to enforce access control on inbound forwarders using VPC firewall rules.
shared-vpc fails, making it impossible to split inbound forwarding and logging into separate policies.gcloud dns managed-zones update ZONE_NAME --log-dns-queries).DNS_RESOLVER). Cloud DNS automatically accepts TCP and UDP port 53 traffic on these entry points.No scenario supports attaching two DNS server policies to the same VPC network or applying VPC firewall rules to Cloud DNS inbound forwarder entry points; both capabilities would have to be configured within a single server policy, with zone-level logging enabled separately on the public zone.
shared-vpc via VPC Network Peering, attach a DNS server policy with inbound query forwarding to the spoke VPC, and configure a Cloud DNS response policy on shared-vpc to log private and public DNS queries while restricting public zone access to shared-vpc subnets.This option places the inbound DNS server policy in a peered spoke VPC instead of shared-vpc and attempts to use a Cloud DNS response policy for query logging and public zone access control.
shared-vpc) that contains the Cloud Interconnect VLAN attachments receiving the on-premises queries.privateVisibilityConfig (authorized VPC networks), whereas public zones are always globally authoritative.The Cloud Interconnect VLAN attachments terminated directly in the spoke VPC (with a DNS peering zone pointing to shared-vpc), query logging was enabled via a DNS server policy and zone settings rather than a response policy, and all internal records were isolated in private zones.
host-project, create a DNS server policy attached to shared-vpc with inbound query forwarding, DNS logging, and an on-premises alternative name server configured. View all VM DNS query logs in service-project-a where the VMs reside, and leave the managed public zone settings unchanged because the server policy covers it.This configuration combines inbound forwarding and DNS logging with an outbound server policy (configuring an alternative name server), expects Shared VPC DNS logs to appear in service-project-a, and assumes a VPC server policy automatically logs queries to a managed public zone.
shared-vpc from resolving Cloud DNS private zones, forwarding zones, peering zones, and Compute Engine internal DNS.host-project) because the host project owns the VPC network—not the service project (service-project-a) where the VMs run.shared-vpc only logs private VPC resolution and inbound-forwarded traffic; external internet queries targeting the managed public zone in service-project-a will not be logged unless logging is enabled directly on that public zone.169.254.169.254).service-project-a), whereas Shared VPC network DNS logs are stored in host-project.The organization intentionally wanted all VPC DNS traffic filtered through an on-premises resolver without needing VPC-scoped private zones or Compute Engine internal DNS, checked network DNS logs in host-project, and separately enabled logging on the public 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