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.
An enterprise network engineering team is standardizing IP address management (IPAM) lifecycle operations across a Shared VPC architecture that hosts VPC-native GKE clusters, Managed Service for Microsoft Active Directory (Managed Microsoft AD) domains, and ephemeral CI/CD test workloads. The team must meet the following requirements:
Which IPAM automation and lifecycle strategy should the team implement?
/24 ranges—on every test run, and update the Managed Microsoft AD CIDR in place when subnets require resizing.Cloud Deployment Manager is an infrastructure deployment service that uses templates to create, update, and delete Google Cloud resources declaratively. While it supports automating project creation and network provisioning, how stateful versus stateless resources are separated within CI/CD pipelines is critical to operational stability.
/24 range in place fails and forces a full domain redeployment.Deployment Manager were used outside the CI/CD pipeline to provision persistent, stateful Shared VPC networks and immutable /24 Managed Microsoft AD ranges once, while CI/CD pipelines deployed and deleted only stateless test workloads inside pre-existing QA projects.
terraform.tfstate file for each static IP reservation or managed service addition, provision /28 subnets for Direct VPC workloads to conserve IPv4 space, and run imperative gcloud compute networks subnets list checks manually before each deployment.Using separate Terraform workspaces and state files (terraform.tfstate) isolates resource tracking per execution, while gcloud compute networks subnets list is an imperative CLI command for inspecting existing subnets within a project. Sizing subnets to /28 attempts to minimize IPv4 consumption for serverless workloads.
terraform.tfstate file used for the initial deployment. Creating a new state file for every addition fragments infrastructure ownership, prevents unified drift detection, and risks IP collisions./26 or larger. Although Cloud Run reserves IPs in blocks of 16 (/28 mask) for fast scale-up and retains scaled-down IPs for up to 20 minutes, provisioning a /28 subnet fails the minimum /26 subnet requirement.gcloud checks lacks automated CI/CD validation, version-controlled change history, and proactive GKE IP utilization alerts.terraform.tfstate files cannot automatically coordinate non-overlapping allocations across a shared deployment./26 requirement: Direct VPC subnets must be /26 or larger, with recommended 2X–4X overprovisioning to absorb revision rollouts and retention windows.The team maintained a unified terraform.tfstate per environment with automated CI/CD validation, sized Direct VPC subnets to /26 or larger, and replaced manual CLI checks with automated Network Analyzer and Cloud Asset Inventory auditing.
gcloud compute networks subnets expand-ip-range in a Cloud Build pipeline to expand exhausted secondary Pod CIDR ranges in place.expand-ip-range Actually DoGKE auto IPAM is an automated IP allocation feature designed to simplify standalone cluster networking by automatically creating subnets and allocating non-overlapping IP ranges for nodes and Pods. Meanwhile, gcloud compute networks subnets expand-ip-range is a Compute Engine command used to enlarge a subnet's primary IPv4 host address range live without workload disruption.
gcloud compute networks subnets expand-ip-range command only expands a subnet's primary range. It cannot expand secondary Pod or Service CIDR ranges in place. Resolving Pod IP exhaustion requires adding discontiguous secondary Pod ranges (multi-Pod CIDR) or executing a blue-green node pool migration./24 allocations or tracks stateless CI/CD resource lifecycles.The organization deployed standalone (non-Shared VPC) VPC-native GKE clusters using IPv4-only subnets and only needed live expansion of the primary node subnet range via expand-ip-range.
/24 Managed Microsoft AD CIDRs, and static IP reservations using modular Terraform configurations in Git with CI/CD validate and plan checks against the shared terraform.tfstate, separate stateful network deployments from stateless test teardowns, and audit IP usage using Cloud Asset Inventory and Network Analyzer ipAddressInsight.Declarative Infrastructure as Code (IaC) IPAM lifecycle management uses modular Terraform configurations stored in Git to define Shared VPC subnets, secondary Pod/Service ranges, static IP reservations, and managed service allocations in a single source of truth. By pairing declarative state management (terraform.tfstate) with Cloud Asset Inventory and Network Analyzer insights, network teams govern provisioning, auditing, and capacity monitoring end to end.
terraform validate and terraform plan into CI/CD pipelines automatically verifies CIDR allocations and catches conflicts before applying changes to the shared terraform.tfstate. Because Managed Microsoft AD requires at least a /24 RFC 1918 range that cannot be modified after creation, declarative validation prevents costly deployment mistakes.google.networkanalyzer.container.ipAddressInsight) flags GKE IP utilization exceeding 80% before IP_SPACE_EXHAUSTED events block autoscaling.terraform.tfstate allows adding new static internal IP reservations without recreating existing infrastructure.Unlike GKE auto IPAM (which does not support Shared VPC) or destructive pipeline-driven project deletion, combining modular Terraform state management with Cloud Asset Inventory and Network Analyzer provides full IPAM lifecycle governance without violating platform 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