Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your platform team is deploying Cloud Workstations to support remote developers connecting from local VS Code editors over Cloud VPN. You must enforce these security and networking policies:
Which configuration should you implement?
Google Kubernetes Engine (GKE) orchestrates containerized workloads on Kubernetes nodes, VPC Network Peering connects two separate VPC networks for internal IP routing, and roles/workstations.networkAdmin grants permissions to configure network resources for connecting a workstation cluster to a Shared VPC. Cloud Shell provides an ephemeral browser-based administrative terminal.
roles/workstations.networkAdmin violates the principle of least privilege. Only the Cloud Workstations Service Agent needs roles/compute.networkUser on the Shared VPC subnet.roles/workstations.user or roles/workstations.workstationCreator to create and connect to workstations.A platform team were provisioning Kubernetes workloads on private GKE nodes for network administrators to manage Shared VPC connectivity rather than deploying managed Cloud Workstations for developers.
Confusing workstation clusters with GKE clusters is a common misconception because both use the term "cluster" and run containers. In Cloud Workstations, each workstation runs its container on a dedicated, isolated Compute Engine VM.
This configuration combines Shared VPC integration, a private workstation cluster, VPC Service Controls alignment, and hardened workstation configuration policies to deliver isolated, containerized development environments accessible from local VS Code editors over Cloud VPN.
roles/compute.networkUser on the Shared VPC subnet to the Cloud Workstations Service Agent (service-$PROJECT_NUMBER@gcp-sa-workstations.iam.gserviceaccount.com) allows the service to provision workstation VMs in the centralized host network.*.<clusterHostname> to the PSC IP enables on-premises developers to reach the cluster gateway over Cloud VPN.--disable-ssh-to-vm blocks direct OS-level SSH to the Compute Engine VMs so all connections pass through the Cloud Workstations gateway.gcloud workstations start-tcp-tunnel opens a local TCP tunnel to port 22 through the authenticated gateway, allowing the VS Code Remote - SSH extension to connect seamlessly./home disks.Unlike public clusters or direct VM SSH approaches, this design satisfies strict enterprise data exfiltration controls, preserves centralized Shared VPC governance, and uses native Google Cloud tunneling for remote IDE workflows.
When a private workstation cluster is created, Cloud Workstations automatically provisions a Private Service Connect (PSC) endpoint for communication between the Google-managed control plane and the workstation VMs. Private Google Access allows VMs without external IP addresses to reach Google APIs and services over internal routing.
*.<clusterHostname>, developers connecting over Cloud VPN cannot resolve or route traffic to the private cluster gateway.roles/compute.networkUser to the Cloud Workstations Service Agent on the Shared VPC subnet, the service cannot provision resources in the host network.gcloud workstations start-tcp-tunnel workflows.*.pkg.dev is configured) but does not handle inbound developer connections.No private cluster gateway access was needed from on-premises networks and direct SSH to internal Compute Engine VMs over Cloud VPN was explicitly desired instead of gateway-managed Cloud Workstations access.
In a private cluster deployment, Cloud VPN or Cloud Interconnect traffic must terminate in the VPC network containing the manually created client PSC endpoint, with on-premises DNS forwarding or private zones resolving *.<clusterHostname> to that endpoint's reserved IP.
A public workstation cluster exposes a Google-managed public cluster gateway endpoint so clients can reach workstations over the internet, while Identity-Aware Proxy (IAP) for TCP forwarding allows administrators to tunnel SSH traffic from 35.235.240.0/20 directly to Compute Engine VM instances on port 22. Cloud NAT provides outbound internet access for VMs without external IP addresses.
Developers needed to connect from untrusted public networks without a VPC Service Controls perimeter or Cloud VPN, and direct IAP SSH access to standard Compute Engine VMs was permitted by security policy.
Even when public IP addresses are disabled on workstation VMs, a public workstation cluster still maintains an internet-facing control plane gateway. Securing Cloud Workstations inside a perimeter requires a private cluster paired with Private Service Connect and gateway-routed connections.
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