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 a fleet of private Compute Engine instances without external IP addresses into a dedicated Virtual Private Cloud (VPC) subnet. The security team has defined the following security, routing, and observability requirements:
Which combination of architectural configurations and observability controls should the security engineer implement?
This configuration attempts to use Private Services Access (PSA) for Google APIs, writes firewall rules targeting post-translation external IP addresses, sets Cloud NAT logging to record only dropped packets, and alerts on port consumption count.
*.googleapis.com) without external IPs.The workload only needed connectivity to a managed Cloud SQL instance over an internal VPC peering range and did not require auditing of successful outbound internet connections.
This architecture combines Private Google Access (PGA), Cloud NAT, Cloud Next Generation Firewall (Cloud NGFW) policies, Cloud NAT logging, and Cloud Monitoring alerting to deliver secure outbound internet connectivity, optimize Google API routing, enforce pre-translation firewall filtering, and provide robust telemetry.
ALL) captures both established outbound connections and dropped packets caused by port exhaustion in Cloud Logging. Creating an alerting policy on the nat_allocation_failed metric in Cloud Monitoring ensures real-time notification when workloads run out of available NAT ports.This approach leverages fully managed, cloud-native services that scale horizontally while maintaining strict least-privilege boundary controls and full observability across all outbound network flows.
This configuration attempts to use VPC Service Controls (VPC-SC) perimeter bridges for internet routing, sets Cloud NAT logging to omit errors, writes hierarchical firewall rules with FQDNs, and processes logs via a custom Cloud Run functions pipeline.
nat_allocation_failed are directly exported to Cloud Monitoring, making a custom Log Sink-to-Cloud Run function pipeline unnecessarily complex and delayed.The requirement was to allow cross-perimeter API data sharing between two distinct VPC Service Controls perimeters while executing custom event-driven automation in Cloud Run.
This option removes the default internet route from the VPC, uses VPC Flow Logs with extended sampling intervals, configures ingress firewall rules for return packets, and monitors infrastructure configuration changes using Cloud Asset Inventory.
default-internet-gateway (destination 0.0.0.0/0) to route internet traffic. Deleting this route prevents Cloud NAT from functioning.The goal was to detect unauthorized modifications to firewall resource definitions rather than monitoring active NAT traffic and port allocation failures.
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