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.
A financial enterprise is securing its Google Cloud environment to minimize perimeter attack surfaces and prevent unintended internet exposure. The security architect establishes the following requirements:
Which combination of architectural controls and services should the security architect deploy?
This option suggests using the compute.skipDefaultNetworkCreation constraint to avoid automatic VPC generation, relying on Cloud NAT for bidirectional traffic inspection, opening administrative ports widely across VPC firewall rules, and using Cloud DNS to route external user requests.
0.0.0.0/0 for ports 22 and 3389 creates severe security risks by exposing administrative interfaces to brute-force and port-scanning attacks across the public internet. Furthermore, because private VMs have no external IPs, open internet firewall rules without a tunneling mechanism like IAP are ineffective.compute.skipDefaultNetworkCreation stops the initial default network from being created, it does not prevent users or automation from provisioning external IP addresses on VMs inside custom VPC networks.compute.skipDefaultNetworkCreation only impacts network provisioning during project creation.The organization only required disabling default auto-mode VPC networks in new projects and relied solely on direct public DNS routing for external access without perimeter load balancing or IAP.
This architecture combines preventive organizational governance, edge translation, zero-trust administrative access, and managed reverse-proxy ingress to isolate virtual machines entirely within private IP address spaces while retaining full outbound capability, secure management, and public service delivery.
constraints/compute.vmExternalIpAccess) organization policy constraint with a policy value of Deny All replaces default behaviors and blocks any Compute Engine instance in the organization from acquiring public external IP addresses.35.235.240.0/20 allows authenticated, authorized administrators to access VMs without assigning public IPs or running dedicated bastion hosts.This pattern aligns with defense-in-depth and zero-trust principles by ensuring that compute resources never maintain direct public IP bindings while cleanly separating inbound reverse-proxy edge routing, outbound egress translation, and IAM-gated administrative access.
This option relies on restricting protocol forwarding rules, configuring Internet Network Endpoint Groups (NEGs) with internal IP targets, and allowing Google Cloud Load Balancer health check probe ranges for SSH and RDP administrative traffic.
constraints/compute.restrictProtocolForwardingCreationForTypes) prevents external forwarding rules used with protocol forwarding. It does not prevent standard Compute Engine VM instances from acquiring external public IP addresses on their virtual network interfaces (nic0).35.191.0.0/16 and 130.211.0.0/22 are reserved for Google Cloud Load Balancer health checking mechanisms. Allowing them does not provide SSH/RDP connectivity for engineers, which specifically requires IAP TCP forwarding from 35.235.240.0/20.The primary goal was strictly to prohibit standalone external protocol forwarding rules while routing load-balanced traffic to third-party public cloud endpoints outside of Google Cloud.
This option attempts to disable external IPv6 subnet allocations, deploy an internal Application Load Balancer targeting internet endpoints, and peer VPC networks with public IP route exchange enabled to handle outbound and administrative flows.
constraints/compute.disableVpcExternalIpv6 only prevents subnets from being configured with external IPv6 allocations; it leaves IPv4 external IP assignments on VMs completely unrestricted.compute.disableVpcExternalIpv6 does not govern IPv4 addresses.The requirement was specifically focused on prohibiting dual-stack IPv6 public subnets and establishing internal routing across peered VPCs utilizing non-RFC 1918 privately owned public IP space.
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