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 operates a hub-and-spoke VPC architecture in Google Cloud where Dedicated Interconnect VLAN attachments terminate in a central hub VPC in us-east1, and application workloads run in peered spoke VPCs. On-premises data science applications must privately query Vertex AI (us-east1-aiplatform.googleapis.com) over the Interconnect.
Your security and networking teams enforce the following requirements:
How should you design the hybrid DNS architecture?
googleapis.com authorized for the hub VPC with a CNAME record for *.googleapis.com. pointing to restricted.googleapis.com. and an A record resolving to 199.36.153.4, 199.36.153.5, 199.36.153.6, and 199.36.153.7. Enable an outbound DNS server policy on the hub VPC, advertise 35.199.192.0/19 and 199.36.153.4/30 via Cloud Router, and configure on-premises DNS conditional forwarders for googleapis.com to target an IP address in the 35.199.192.0/19 range.35.199.192.0/19 doA Cloud DNS outbound server policy specifies alternative name servers for VMs inside a VPC network to use for their own DNS lookups, while 35.199.192.0/19 is the source IP address range that Cloud DNS uses when sending outbound-forwarded queries to on-premises DNS servers.
35.199.192.0/19 is strictly an egress source range for Cloud DNS outbound forwarding and forwarding zones; it is not an addressable inbound listener for DNS queries originating on-premises. Conditional forwarders targeting 35.199.192.0/19 will time out.53 requests from on-premises.35.199.192.0/19 is reserved for Cloud DNS outbound query egress.AXFR/IXFR) to synchronize private zone records to on-premises servers, making inbound server policies mandatory for on-premises lookups of Cloud DNS private zones.You needed Google Cloud VMs in the hub VPC to send DNS queries to on-premises authoritative servers using outbound forwarding, in which case on-premises firewalls and Cloud Router would permit and advertise 35.199.192.0/19 for return traffic.
googleapis.com authorized for the spoke VPC with a CNAME record for *.googleapis.com. pointing to restricted.googleapis.com. and an A record resolving to 199.36.153.4, 199.36.153.5, 199.36.153.6, and 199.36.153.7. Enable an inbound DNS server policy on the spoke VPC, advertise the spoke subnet and 199.36.153.4/30 prefixes via the hub Cloud Router, and configure on-premises DNS conditional forwarders for googleapis.com to target the spoke VPC's inbound forwarder IP address.A Cloud DNS inbound server policy allocates internal IPv4 entry point addresses from the primary IPv4 address ranges of subnets inside the VPC network to which the policy is attached. These entry points allow external clients over Cloud VPN or Cloud Interconnect to query private DNS zones authorized for that VPC.
The Dedicated Interconnect VLAN attachments terminated directly in that spoke VPC rather than in a separate hub VPC connected via VPC Network Peering.
googleapis.com authorized for the hub VPC with a CNAME record for *.googleapis.com. pointing to restricted.googleapis.com. and an A record resolving to 199.36.153.4, 199.36.153.5, 199.36.153.6, and 199.36.153.7. Enable an inbound DNS server policy on the hub VPC, advertise the hub subnet and 199.36.153.4/30 prefixes via Cloud Router, and configure on-premises DNS conditional forwarders for googleapis.com to target the hub VPC's us-east1 inbound forwarder IP address.This architecture combines a Cloud DNS private managed zone for googleapis.com with a Cloud DNS inbound server policy on the hub VPC and on-premises conditional forwarding. Together, they allow on-premises workloads to resolve us-east1-aiplatform.googleapis.com to the restricted.googleapis.com virtual IP addresses (199.36.153.4/30) and route API traffic privately over Dedicated Interconnect.
*.googleapis.com. via a CNAME to restricted.googleapis.com. (199.36.153.4 through 199.36.153.7) restricts traffic exclusively to Google Cloud APIs and services supported by VPC Service Controls, mitigating data exfiltration risks.googleapis.com records in a Cloud DNS private zone avoids managing duplicate BIND or Active Directory zone files across on-premises DNS servers.us-east1 region as the Dedicated Interconnect VLAN attachment. Because Cloud DNS automatically accepts TCP and UDP port 53 on inbound forwarder IPs without needing VPC firewall rules, conditional forwarders on-premises can immediately query the us-east1 entry point.199.36.153.4/30 via Cloud Router ensures bidirectional private routing for both DNS queries and Vertex AI HTTPS traffic.us-east1 inbound forwarder entry point matches the region of the VLAN attachment, ensuring optimal latency and symmetric hybrid return paths.Unlike private.googleapis.com, restricted.googleapis.com guarantees VPC Service Controls enforcement, and unlike spoke-placed or outbound-targeted configurations, placing the inbound server policy in the hub VPC in us-east1 adheres to Cloud DNS peering and regional routing rules.
googleapis.com authorized for the hub VPC with a CNAME record for *.googleapis.com. pointing to private.googleapis.com. and an A record resolving to 199.36.153.8, 199.36.153.9, 199.36.153.10, and 199.36.153.11. Enable an inbound DNS server policy on the hub VPC, advertise the hub subnet and 199.36.153.8/30 prefixes via Cloud Router, and configure on-premises DNS conditional forwarders for googleapis.com to target the hub VPC's us-east1 inbound forwarder IP address.private.googleapis.com and Private Google Access VIPs doThe private.googleapis.com domain (199.36.153.8/30) provides Private Google Access virtual IP addresses (VIPs) that allow on-premises hosts and VPC workloads to reach Google APIs and services over private connectivity without traversing the public internet. Combined with a Cloud DNS inbound server policy and on-premises conditional forwarding, it centralizes DNS overrides inside Cloud DNS.
private.googleapis.com permits access to almost all Google APIs and services regardless of whether they are supported by VPC Service Controls. This leaves a potential data exfiltration path open to non-VPC-SC Google APIs.us-east1-aiplatform.googleapis.com resolves and functions over 199.36.153.8/30, the architecture does not enforce the strict API-level perimeter protection requested by the security team.private.googleapis.com (199.36.153.8/30): Supports most Google APIs (including Google Maps, Google Ads, and Google Cloud services outside VPC Service Controls).*.googleapis.com. wildcard CNAME pointing to private.googleapis.com. redirects all subdomains to the broader VIP range.private.googleapis.com and restricted.googleapis.com in the same zone, as doing so causes intermittent API failures.The organization either did not use VPC Service Controls or explicitly needed on-premises hosts to access Google APIs that are not supported by VPC Service Controls alongside Vertex AI.
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