Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise requires on-premises workloads to privately access Google Cloud APIs and services without routing traffic over the public internet. The on-premises data center is connected to a Google Cloud Virtual Private Cloud (VPC) network via Cloud Interconnect. To comply with security policies, the API communication must be restricted to services supported by VPC Service Controls.
Which combination of DNS and routing configurations should the enterprise implement?
*.googleapis.com to private.googleapis.com (199.36.153.8/30), and enable custom route exports via VPC Network Peering to transitively forward the routes to on-premises routers.This option attempts to use the private.googleapis.com VIP range (199.36.153.8/30) and relies on VPC Network Peering custom route exports to transitively forward Google API routes from a peered VPC network to the on-premises routers.
private.googleapis.com (199.36.153.8/30) VIP allows access to most Google APIs, but it does not restrict access exclusively to VPC Service Controls-supported services. Only restricted.googleapis.com (199.36.153.4/30) guarantees this boundary protection.private.googleapis.com exposes APIs that are outside the VPC Service Controls boundary.The organization needed broad private access to all supported Google APIs (not restricted to VPC Service Controls) and was configuring BGP directly on the Cloud Router terminating the hybrid connection.
Private Google Access enabled on a VPC subnet allows Compute Engine VMs without external public IP addresses to reach Google APIs privately. Cloud NAT provides managed outbound Network Address Translation for VPC instances to reach the public internet without public IPs.
The scenario required private Compute Engine VM instances in a VPC subnet without external IP addresses to access both Google APIs and external third-party internet software repositories.
*.googleapis.com CNAME records to default.googleapis.com, and advertise a default route (0.0.0.0/0) from the VPC Cloud Router to on-premises routers.This option attempts to resolve Google APIs to standard public default VIPs and route all general on-premises internet traffic transitively through the VPC network by advertising a default 0.0.0.0/0 route over Cloud Router.
default.googleapis.com is not a valid endpoint for restricting API traffic to VPC Service Controls-supported services; standard Google API endpoints resolve to public anycast IP ranges that bypass restricted perimeter routing.0.0.0.0/0 forces all hybrid traffic through the VPC, creating unintended internet transit routing overhead instead of specifically directing API traffic to designated private access points.restricted.googleapis.com (199.36.153.4/30) or private.googleapis.com (199.36.153.8/30).The organization wanted to route all general outbound on-premises internet traffic through a centralized egress proxy or firewall hosted inside a Google Cloud VPC.
*.googleapis.com CNAME records to restricted.googleapis.com (199.36.153.4/30), and configure custom BGP route advertisements on the VPC's Cloud Router to announce 199.36.153.4/30 to on-premises routers.Private Google Access for on-premises hosts provides private connectivity from hybrid environments (such as on-premises data centers or colocation facilities connected via Cloud Interconnect or Cloud VPN) directly to Google APIs and services using internal Google network paths rather than the public internet.
*.googleapis.com domains to restricted.googleapis.com directs traffic to the dedicated IP range 199.36.153.4/30. This special virtual IP (VIP) block allows access exclusively to Google services that support VPC Service Controls, blocking unverified or unsupported services.199.36.153.4/30 ensures on-premises routers have an explicit route pointing to the Cloud Interconnect / Cloud VPN gateway for all Google API destinations.Using restricted.googleapis.com (199.36.153.4/30) combined with custom BGP route advertisements natively aligns hybrid routing topology with perimeter security controls, satisfying all security and zero-internet transit requirements.
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