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 runs Compute Engine workloads in us-central1 behind a Public Cloud NAT gateway (nat-gw-prod). Because an external financial partner enforces strict IP allowlisting, nat-gw-prod uses manual NAT IP address assignment with two Premium Tier regional static external IPv4 addresses (nat-ip-1 and nat-ip-2).
During peak batch processing, Cloud Monitoring triggers nat_allocation_failed alerts due to port exhaustion. You must meet the following requirements:
nat-ip-1 while keeping nat-ip-2 active.Which sequence of actions should you take?
us-central1 and provide them to the partner for allowlisting. Update nat-gw-prod to add both new addresses alongside nat-ip-1 and nat-ip-2, enable draining on nat-ip-1, and remove nat-ip-1 only after its active connections close.Manual NAT IP address assignment lets you reserve specific regional static external IPv4 addresses in your project and bind them to a Public Cloud NAT gateway. NAT IP draining is a lifecycle control for manually assigned addresses that stops the gateway from assigning an IP address to new connections while keeping existing sessions alive until they terminate normally.
us-central1 and adding them to the gateway immediately increases the pool of available NAT source IP and port tuples, resolving nat_allocation_failed port exhaustion.nat-gw-prod prevents outbound requests from being blocked by the partner's firewall.nat-ip-1 without dropping connections: Enabling draining on nat-ip-1 prevents new connections from using it while allowing established flows to finish gracefully. Keeping nat-ip-2 active ensures continuous availability, and removing nat-ip-1 only after its active connections close guarantees zero dropped traffic.nat-ip-1 and nat-ip-2, satisfying the requirement that all active IP addresses within a NAT rule (including the default rule) share the same network tier.Unlike deleting nat-ip-1 directly (which severs active connections), switching to automatic allocation (which breaks all connections and prevents pre-allowlisting), or mixing network tiers (which is rejected), adding same-tier static IPs after allowlisting and draining nat-ip-1 is completely non-disruptive and compliant with Cloud NAT rules.
nat-gw-prod to automatic NAT IP address allocation so Cloud NAT scales out additional Premium Tier IP addresses, identify the new addresses from Cloud NAT logs for partner allowlisting, and then switch back to manual assignment without nat-ip-1.Changing a Public Cloud NAT gateway between manual NAT IP address assignment and automatic NAT IP address allocation switches control of external IP provisioning between customer-managed static IP resources and Google Cloud's automated IP pool manager.
nat-ip-2.Automatic NAT IP address allocation would be appropriate if the external partner did not require IP allowlisting, no specific IP addresses needed to be retained, and a maintenance window allowed dropping all existing connections during the initial migration.
us-central1 and provide them to the partner for allowlisting. Update nat-gw-prod to set its manual external IP pool to nat-ip-2 and the two new addresses, omitting nat-ip-1 to shift traffic off it.Updating a Public Cloud NAT gateway's manual NAT IP pool by omitting an existing IP address instructs Google Cloud to immediately detach that external IPv4 address from the gateway's active translation pool and purge its corresponding entries from the connection tracking table.
nat-ip-1. Return packets from the external partner matching nat-ip-1 will no longer find active mappings and will be dropped.nat-ip-1 directly bypasses graceful lifecycle management.This configuration would be acceptable only if nat-ip-1 currently had zero active NAT mappings (for example, during a scheduled maintenance window with no running workloads) or if the application could tolerate immediate connection resets and automatic retries.
Always check active connections or enable IP address draining before deleting an address from a manual Cloud NAT pool. Draining separates the removal of an IP from new connection assignment from the termination of existing flows.
us-central1 and add them to nat-gw-prod in a drained state alongside nat-ip-1 and nat-ip-2. Once the partner updates their allowlist, disable draining on the new addresses and remove nat-ip-1.This approach attempts to combine Standard Tier static external IPv4 addresses with existing Premium Tier addresses in the gateway's default rule, while pre-staging the new addresses in a drained state until external firewall allowlists are updated.
nat-ip-1 and nat-ip-2) in the same rule is rejected by Google Cloud.Standard Tier addresses could be used only if you first drained all existing Premium Tier addresses (which conflicts with keeping nat-ip-2 active in the same rule) or configured separate Cloud NAT rules for different source ranges, and updated the partner allowlist prior to attaching the new IPs.
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