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 deploys multiple GKE Standard (version 1.29) VPC-native clusters across several service projects in a Shared VPC. You must optimize RFC 1918 IP address utilization while preserving strict isolation boundaries:
ClusterIP Services without using VPC-scope Cloud DNS for GKE.Which configuration should you implement?
This approach correctly identifies the Shared VPC pre-creation model, the dedicated Private Service Connect (PSC) control plane subnet, and the separation of Pod ranges alongside a shared Service range. However, it introduces two incompatible configuration constraints regarding cluster creation tooling and DNS scope.
gcloud CLI or the GKE API.ClusterIP ranges.ClusterIP allocations.kube-dns (or cluster-scope DNS) and be provisioned via CLI or API.You deployed the clusters using the gcloud CLI or REST API instead of the Google Cloud console, and did not enable VPC-scope Cloud DNS for GKE.
--private-endpoint-subnetwork when creating each cluster. In the host project, create one shared user-managed secondary Service IP range and separate secondary Pod IP ranges per cluster, then create the clusters using the gcloud CLI.This architecture combines Private Service Connect (PSC) control plane subnet isolation with user-managed Shared VPC IP range allocation. Pre-creating subnets and secondary ranges in the Shared VPC host project gives network administrators centralized control over IP planning and firewall boundaries across all service projects.
--private-endpoint-subnetwork during cluster creation overrides the default behavior (which places the control plane internal IP in the node subnet's primary range). GKE provisions each PSC control plane endpoint inside the dedicated subnet, which can be shared across clusters and Shared VPC service projects while enforcing separate firewall rules from worker nodes.ClusterIP addresses are programmed locally on nodes via eBPF or iptables and are never routed across the VPC, multiple clusters can safely share a single user-managed secondary Service IP range (provided its name does not match ^gke-.*-services-[abcdef0-9]{8}). Using the gcloud CLI is mandatory because shared secondary ranges cannot be selected in the Google Cloud console UI.ClusterIP Services across dozens of clusters.Unlike peering-based --master-ipv4-cidr ranges that cannot overlap, a PSC endpoint subnet is shareable across projects, and sharing a user-managed Service range via the CLI works cleanly when VPC-scope Cloud DNS for GKE is not required.
/28 CIDR block to --master-ipv4-cidr on every cluster to share the control plane IP range across projects, and allow GKE to automatically create and share GKE-managed secondary ranges for Pods and Services in the Shared VPC host project.--master-ipv4-cidr and GKE-managed secondary ranges doThe --master-ipv4-cidr flag provisions a /28 CIDR block for a peering-based GKE control plane inside a Google-managed tenant VPC peered to your VPC network. GKE-managed secondary ranges allow GKE to automatically allocate subnet secondary CIDR blocks in standalone VPCs without manual pre-creation.
--master-ipv4-cidr route into your VPC peering group. This /28 block must be unique and cannot overlap with any other CIDR in the VPC network or peering group, so passing the same /28 across multiple clusters causes routing conflicts and cluster creation failures.^gke-.*-services-[abcdef0-9]{8}) cannot be shared across clusters.--master-ipv4-cidr consume a separate /28 CIDR and a VPC peering route per cluster.Each cluster resided in an independent standalone VPC with a unique, non-overlapping /28 --master-ipv4-cidr range and did not need to share secondary IP ranges across clusters.
VPC_PEERING range named google-managed-services-<vpc> in the Shared VPC host project for control plane endpoints. Share a single user-managed secondary Pod IP range across all clusters via the gcloud CLI, and assign a unique secondary Service IP range to each cluster.google-managed-services-<vpc> and shared Pod ranges doThe google-managed-services-<vpc> allocation created with --purpose=VPC_PEERING is a Private Services Access construct used to connect a VPC to Google-managed producer services such as Cloud SQL, Memorystore, or Apigee. Meanwhile, sharing a secondary Pod IP range lets multiple VPC-native clusters draw per-node alias IP CIDR blocks from the same subnet secondary range.
VPC_PEERING allocations do not host GKE control plane endpoints. GKE clusters running version 1.29 or later use Private Service Connect (PSC) for control plane connectivity and require a standard VPC subnet specified via --private-endpoint-subnetwork to isolate and share control plane internal endpoints./24 for up to 110 Pods) from the secondary Pod range.ClusterIP Service addresses are non-routable outside each cluster, making Service ranges safe to share.You were provisioning managed database services like Cloud SQL over Private Services Access rather than GKE control planes, and did not require Pod capacity isolation across clusters.
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