Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
Your enterprise wants to standardize cloud-hosted developer workspaces across multiple engineering teams using Google Cloud Workstations. The security and DevOps teams have defined the following governance requirements:
Which approach should you implement to meet these requirements?
Create and publish a custom container image extending the Cloud Workstations base Code OSS image that pre-installs the required .vsix extensions and injects default workspace settings, then manage Workstation Configurations referencing this image via Terraform.
Configure a repository-level .vscode/extensions.json and settings.json file in each Git source repository, requiring developers to manually accept recommended extensions when opening Cloud Shell.
Deploy standard Compute Engine virtual machines with Cloud Init startup scripts that download the VS Code desktop binary and execute runtime extension install commands upon user login.
Define a Cloud Composer DAG that executes remote SSH commands against active developer workstations on a daily schedule to synchronize IDE settings and install missing extensions.
Create and publish a custom container image extending the Cloud Workstations base Code OSS image that pre-installs the required .vsix extensions and injects default workspace settings, then manage Workstation Configurations referencing this image via Terraform.
Google Cloud Workstations provides managed development environments running inside container instances. By building a custom container image derived from Google's base Code OSS (VS Code open-source) image, organizations can package specific runtimes, dependencies, configuration files, and IDE extensions into an immutable artifact.
.vsix binaries during the Dockerfile build step and installed directly into the global extension directory (/opt/code-oss/extensions).settings.json directory in the container image, ensuring immediate compliance when workspaces launch.google_workstations_workstation_config) creates a fully automated, auditable, and repeatable delivery pipeline. Updating the container image tag in Terraform triggers managed workstation updates, preventing configuration drift.Baking configurations and extensions directly into the workstation container image and deploying them via Terraform ensures absolute reproducibility, high startup performance, and centralized policy enforcement across the entire developer fleet.
Configure a repository-level .vscode/extensions.json and settings.json file in each Git source repository, requiring developers to manually accept recommended extensions when opening Cloud Shell.
Deploy standard Compute Engine virtual machines with Cloud Init startup scripts that download the VS Code desktop binary and execute runtime extension install commands upon user login.
Define a Cloud Composer DAG that executes remote SSH commands against active developer workstations on a daily schedule to synchronize IDE settings and install missing extensions.