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 is deploying a regional Secure Web Proxy instance in us-central1 with a Certificate Manager certificate, TLS inspection, and a Gateway Security Policy to govern outbound web traffic. To complete the production integration, you must meet three requirements:
Which configuration should you implement?
networkservices.googleapis.com, networksecurity.googleapis.com, certificatemanager.googleapis.com, and privateca.googleapis.com in the VPC Service Controls perimeter; and configure a log-based alert on Admin Activity audit logs for networkservices.googleapis.com/Gateway.This option correctly identifies the four APIs required inside the VPC Service Controls perimeter for a certificate-enabled, TLS-inspecting proxy, but it misconfigures both Cloud NAT egress routing and Cloud Logging alerting. It attempts to control proxy egress through a separate workload-subnet Cloud NAT gateway with static port allocation and relies on Admin Activity audit logs to monitor denied traffic.
swg-autogen-nat gateway in the proxy's region and VPC network. A separate Cloud NAT gateway targeting workload subnets does not translate outbound traffic leaving the proxy, and static port allocation risks port exhaustion under peak load.DENIED), leaving the SOC blind to blocked egress attempts.swg-autogen-nat gateway in that same region and VPC.gateway_requests) track data-plane traffic flows.The organization were bypassing Secure Web Proxy entirely and routing VM traffic directly through a custom Cloud NAT gateway (with DPA enabled), and the alerting requirement was to detect unauthorized policy configuration edits rather than denied web requests.
A common misconception is treating Secure Web Proxy like standard VM egress; because the proxy terminates client connections and initiates new outbound connections, NAT and logging must target the proxy's managed NAT gateway and transaction log stream.
swg-autogen-nat on Automatic NAT IP address allocation for maximum port scalability; include networkservices.googleapis.com, networksecurity.googleapis.com, and compute.googleapis.com in the VPC Service Controls perimeter; and enable Data Access audit logs on networkservices.googleapis.com to alert on denied egress connections.This option relies on Automatic NAT IP address allocation on swg-autogen-nat, adds Compute Engine API (compute.googleapis.com) alongside the core proxy APIs in VPC Service Controls, and enables Data Access audit logs to monitor denied egress connections.
swg-autogen-nat on Automatic allocation allows Google Cloud to dynamically assign and scale external IP addresses on demand. Partner APIs protected by strict IP-based access control lists (ACLs) will reject traffic whenever Google Cloud rotates or scales the ephemeral NAT IPs.compute.googleapis.com is only needed if the proxy interacts with Compute Engine resources across the perimeter, while omitting certificatemanager.googleapis.com and privateca.googleapis.com leaves the proxy's Certificate Manager certificate and TLS inspection CA unprotected.networkservices.googleapis.com%2Fgateway_requests).Partner APIs did not require IP allowlisting, TLS inspection and Certificate Manager certificates were disabled, and the security team only needed to audit administrative reads of proxy resource metadata.
Many engineers conflate Automatic NAT IP allocation with Dynamic Port Allocation; automatic IP allocation scales public IPs unpredictably, whereas manual static IPs paired with DPA keep external IPs fixed while scaling port allocation per VM.
swg-autogen-nat gateway in us-central1 to use manually reserved static IPv4 addresses with Dynamic Port Allocation (DPA) enabled; include only networkservices.googleapis.com and networksecurity.googleapis.com in the VPC Service Controls perimeter; and create a log-based alert on networkservices.googleapis.com%2Fgateway_requests (resource.type="networkservices.googleapis.com/Gateway") filtering on jsonPayload.authzPolicyInfo.result="DENIED".This option correctly updates the managed swg-autogen-nat gateway with manual static IPv4 addresses and Dynamic Port Allocation (DPA), and it targets the correct gateway_requests transaction log stream. However, it omits mandatory VPC Service Controls APIs for TLS inspection and uses the wrong JSON payload field for a Gateway Security Policy.
networkservices.googleapis.com and networksecurity.googleapis.com are the baseline required APIs for Secure Web Proxy, provisioning the proxy with a Certificate Manager certificate requires adding certificatemanager.googleapis.com, and enabling TLS inspection requires adding privateca.googleapis.com (Certificate Authority Service API). Omitting them leaves certificate management and CA operations outside the perimeter boundary.jsonPayload.authzPolicyInfo.result="DENIED" is populated when Secure Web Proxy is deployed as an Agent Gateway enforcing an authorization policy. Standard web traffic governed by a Gateway Security Policy writes rule denials to jsonPayload.enforcedGatewaySecurityPolicy.matchedRules.action="DENIED", so the alert query will never match.The proxy were deployed as an Agent Gateway using an authorization policy without Certificate Manager certificates or TLS inspection enabled.
Administrators frequently overlook conditional API requirements in VPC Service Controls tables and confuse Agent Gateway authzPolicyInfo fields with standard enforcedGatewaySecurityPolicy log fields during SIEM rule creation.
swg-autogen-nat gateway in us-central1 to use manually reserved static IPv4 addresses with Dynamic Port Allocation (DPA) enabled; include networkservices.googleapis.com, networksecurity.googleapis.com, certificatemanager.googleapis.com, and privateca.googleapis.com in the VPC Service Controls perimeter; and create a log-based alert on networkservices.googleapis.com%2Fgateway_requests (resource.type="networkservices.googleapis.com/Gateway") filtering on jsonPayload.enforcedGatewaySecurityPolicy.matchedRules.action="DENIED".This configuration combines Secure Web Proxy with managed Cloud NAT, VPC Service Controls, and Cloud Logging to establish a deterministic, perimeter-protected, and observable egress architecture. When a Secure Web Proxy gateway is deployed in a region and VPC network, Google Cloud automatically provisions a Cloud Router (swg-autogen-router-*) and a Cloud NAT gateway (swg-autogen-nat) to handle outbound translation.
swg-autogen-nat from Automatic to Manual IP allocation binds outbound traffic to reserved regional static IPv4 addresses for partner allowlists. Enabling Dynamic Port Allocation (DPA) (typically configured with 2,048 minimum and 4,096 maximum ports per VM) dynamically assigns source ports from the limited static IP pool so high-concurrency workloads do not suffer port exhaustion.networkservices.googleapis.com and networksecurity.googleapis.com APIs. Because the proxy uses a provisioned certificate and TLS inspection, certificatemanager.googleapis.com and privateca.googleapis.com are also mandatory inside the perimeter.networkservices.googleapis.com%2Fgateway_requests log stream under resource.type="networkservices.googleapis.com/Gateway". Filtering on jsonPayload.enforcedGatewaySecurityPolicy.matchedRules.action="DENIED" accurately detects requests blocked by a Gateway Security Policy.Unlike creating secondary NAT gateways, querying Admin Activity logs, or omitting certificate APIs, this approach aligns directly with Secure Web Proxy's regional egress pipeline, full TLS inspection dependency tree, and transaction logging schema.
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