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 internal workloads across multiple subnets in a Google Cloud VPC without public IP addresses. The organization must meet the following egress security and partner integration requirements:
10.10.1.0/24) must route outbound traffic to external payment gateways using a dedicated, reserved static external IP address (IP_ADDRESS_1) for IP whitelisting.10.10.2.0/24) must route outbound traffic to an external reporting endpoint using a separate reserved static external IP address (IP_ADDRESS_2).Which Cloud NAT configuration should the cloud security engineer implement?
IP aliasing (alias IP ranges) allows assigning multiple internal IPv4 addresses from a subnet's primary or secondary range to a single VM network interface, commonly used in container environments like Google Kubernetes Engine (GKE) to assign Pod IPs.
The requirement was to host multiple internal container pods or virtual endpoints on a single VM interface and provide each pod with a distinct internal VPC IP address.
This approach attempts to use automatic IP allocation on Cloud NAT while relying on VPC firewall egress rules to dynamically modify packet headers and perform source address translation.
The workloads did not interact with third-party systems requiring static IP whitelisting and only needed elastic, self-scaling outbound internet connectivity.
inIpRange(source.ip, ...) to assign dedicated --source-nat-active-ips per subnet.Cloud NAT rules allow fine-grained control over how network address translation maps internal traffic to specific external IP addresses based on matching criteria, such as source or destination IP ranges. Using manual IP allocation, administrators pre-allocate regional static external IP addresses and bind them deterministically to the gateway and specific NAT rules.
10.10.1.0/24): A NAT rule configured with a Common Expression Language (CEL) match condition (inIpRange(source.ip, '10.10.1.0/24')) maps outbound packets from this subnet to --source-nat-active-ips=IP_ADDRESS_1.10.10.2.0/24): A second NAT rule with higher/lower priority matching inIpRange(source.ip, '10.10.2.0/24') maps outbound packets from the analytics subnet to --source-nat-active-ips=IP_ADDRESS_2.--nat-external-ip-pool.This configuration adheres to least privilege and defense-in-depth principles by maintaining private VM network interfaces while fulfilling partner firewall whitelisting constraints using a centralized, software-defined Cloud NAT gateway.
Custom static routes define egress paths for traffic within a VPC network by directing matching destination prefixes to next-hop resources such as VPN tunnels, Cloud Interconnect, VPC peering links, or internal VM network interfaces (appliances).
Traffic was being routed to a third-party virtual appliance (such as a self-managed Next-Generation Firewall VM) using its internal IP address as the next hop.
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