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 is deploying Compute Engine virtual machines without external IP addresses in a custom subnet (10.10.1.0/24). The workloads need to securely communicate with Cloud Storage and Artifact Registry while preventing data exfiltration to non-supported external services by leveraging an active VPC Service Controls security perimeter.
The VPC network enforces a strict baseline egress policy with an explicit low-priority deny rule for 0.0.0.0/0.
Which set of actions should the security engineer take to establish connectivity while maintaining network isolation and security perimeter enforcement?
0.0.0.0/0 on TCP port 443.Cloud NAT (Network Address Translation) allows Google Cloud VM instances without external IP addresses to initiate outbound connections to the internet using a shared pool of public IP addresses.
0.0.0.0/0 allows outbound connectivity to any arbitrary internet endpoint over port 443, breaching strict isolation policies.199.36.153.4/30), failing to restrict access exclusively to VPC-SC protected services.0.0.0.0/0), increasing risk of data exfiltration.The VMs required direct outbound internet access to non-Google third-party web services and public repositories without assigning public IPs to individual VMs.
Private services access is a private connection between a VPC network and a service producer network (such as Cloud SQL, Memorystore, or Vertex AI) established via VPC Network Peering using an allocated internal IP range.
restricted.googleapis.com VIP required for VPC-SC.restricted.googleapis.com.The VMs needed private IP connectivity to a Google-managed database instance like Cloud SQL or a Memorystore Redis instance.
*.googleapis.com and *.pkg.dev to restricted.googleapis.com (199.36.153.4/30), ensure a default route exists to the default internet gateway for 199.36.153.4/30, and create an egress allow firewall rule for 199.36.153.4/30 on TCP port 443.Private Google Access (PGA) allows Compute Engine instances with only internal IP addresses to reach Google APIs and services through internal Google network pathways. When paired with VPC Service Controls (VPC-SC), traffic must be directed to the restricted VIP domain (restricted.googleapis.com), which maps to 199.36.153.4/30.
*.googleapis.com and *.pkg.dev to restricted.googleapis.com resolves endpoints to 199.36.153.4/30, which strictly allows only APIs supported by VPC Service Controls and blocks non-supported services, mitigating risk of data exfiltration.199.36.153.4/30 (or 0.0.0.0/0) with the default internet gateway next hop is required by Google Cloud's routing layer to direct internal API traffic to Google infrastructure.199.36.153.4/30 on TCP port 443 maintains tight boundary isolation while permitting necessary API traffic./30 prefix, keeping network attack surfaces minimal.This solution meets all functional, routing, firewall, and VPC-SC perimeter security requirements without introducing unneeded infrastructure or exposing internal workloads to broader network ranges.
*.googleapis.com and *.pkg.dev to private.googleapis.com (199.36.153.8/30), ensure a route exists for 199.36.153.8/30 to the default internet gateway, and create an egress allow firewall rule for 199.36.153.8/30 on TCP port 443.private.googleapis.com Isprivate.googleapis.com is a Google-managed private VIP (199.36.153.8/30) used by Private Google Access to route traffic to most Google APIs and services using internal Google network paths.
private.googleapis.com endpoint provides access to both VPC Service Controls-supported services and services that do not support VPC Service Controls. It does not automatically block requests to unsupported APIs.restricted.googleapis.com (199.36.153.4/30) to enforce service perimeter boundaries and prevent data exfiltration.199.36.153.8/30 rather than the 199.36.153.4/30 restricted subnet range.The organization did not require VPC Service Controls perimeter enforcement and needed to access Google APIs and services that are not supported by VPC-SC.
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