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 an AI agent runtime on Google Cloud that must securely query third-party external tool APIs across the internet. The agent workloads are hosted in a private VPC subnet without external IP addresses.
To control and monitor outbound connections, all agent traffic to external APIs is routed through an Internal Application Load Balancer with internet Network Endpoint Groups (internet NEGs). The external API providers require all incoming API requests to originate from a known, dedicated set of allowlisted public IP addresses.
Which network architecture configuration should the security engineer implement to satisfy these requirements?
Hierarchical and Network Firewall Policies allow administrators to define stateful Layer 3/4 and Layer 7 firewall rules applied across projects and VPCs using IAM-governed resource tags to microsegment workloads.
ENDPOINT_TYPE_MANAGED_PROXY_LB specifically attached to the regional Cloud Router and proxy-only subnet.The objective was implementing microsegmentation and FQDN-based access restrictions between the agent runtime subnet and the load balancer proxy-only subnet without managing NAT IP allocations.
This option creates a standard Cloud NAT gateway targeting Compute Engine VM instances residing in the primary workload subnet and uses Google-managed automatic IP address allocation.
ENDPOINT_TYPE_VM) does not process traffic coming from proxy-only subnets.NICs).The agent VMs connected directly to external APIs over the internet without going through an intermediate proxy load balancer, and the external API services did not require static IP allowlisting.
Google Cloud Armor delivers Layer 7 DDoS mitigation and Web Application Firewall (WAF) filtering primarily for inbound traffic directed toward HTTP(S) load balancers, protecting internal backends from external threats.
The primary goal was filtering and inspecting incoming API client traffic targeting agent endpoints using web application security rules and rate limiting.
Cloud NAT for managed proxy load balancers allows regional internal proxy-based load balancers (such as regional Internal Application Load Balancers) that route traffic to external backends via internet NEGs to translate proxy egress traffic through specific public NAT IP addresses.
--endpoint-types=ENDPOINT_TYPE_MANAGED_PROXY_LB ensures the NAT gateway specifically handles egress traffic originating from the Envoy proxies residing in the load balancer's proxy-only subnet.--nat-custom-subnet-ip-ranges=PROXY_ONLY_SUBNET_NAME provides NAT service strictly for the subnet that hosts the load balancer proxy interfaces rather than general VM subnets.When using an Internal Application Load Balancer with internet NEGs, the backend TCP/HTTP connections to external endpoints originate from Envoy proxies inside the proxy-only subnet, not directly from the agent VMs. Standard VM-based Cloud NAT cannot translate proxy-only subnet traffic. Configuring Cloud NAT with ENDPOINT_TYPE_MANAGED_PROXY_LB and manual static IP allocation directly meets the architectural and allowlisting constraints.
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