Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
This strategy uses Cloud Composer (managed Apache Airflow) to run scheduled orchestration workflows that open SSH connections to developer machines and execute remote CLI commands to update configuration files and install IDE plugins.
You were orchestrating complex multi-system ETL/ELT data pipelines across BigQuery, Cloud Storage, and Dataproc rather than bootstrapping developer IDEs.
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.
This pattern provisions generic Compute Engine virtual machine instances and relies on OS-level startup scripts (Cloud Init or VM metadata startup scripts) to fetch packages, install the VS Code executable, and execute code --install-extension commands when developers connect or when the VM boots.
Your architecture required dedicated bare-metal or legacy virtualization infrastructure without containerization support, where developers strictly access VMs through traditional SSH or RDP rather than managed cloud IDE workstations.
This approach relies on committing workspace recommendation files (.vscode/extensions.json and .vscode/settings.json) directly into application source control repositories. When developers open the repository in an editor like Cloud Shell Editor or VS Code, the editor displays a notification prompting the user to install recommended extensions.
.vscode/ configurations. If a security linter rule changes, hundreds of repositories must be manually updated.You were managing an open-source project or loosely coupled microservices where project maintainers want to suggest helpful IDE extensions without enforcing corporate security policies or cloud infrastructure standards.
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