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 is deploying Google Cloud Workstations for a software development team requiring custom development tooling and internal security packages. You must establish a secure lifecycle and deployment workflow for these workstations that satisfies the following requirements:
Which combination of steps should you implement to satisfy these requirements?
This approach uses Compute Engine virtual machine disk snapshots and exports them as raw compressed disk files (disk.raw.tar.gz) to a Cloud Storage bucket, which is a legacy image-management workflow for standard VM boot disks.
You were designing custom VM boot images for traditional Compute Engine Managed Instance Groups (MIGs) rather than containerized Cloud Workstations.
This architecture establishes a fully automated, secure CI/CD lifecycle pipeline for Cloud Workstations custom container images utilizing native Google Cloud services: Cloud Build, Artifact Registry, Artifact Analysis (Container Scanning), and Cloud Scheduler.
0 1 * * *), ensuring that upstream base editor security updates are automatically pulled in daily.containerscanning.googleapis.com) enabled automatically triggers vulnerability scanning on each uploaded digest, identifying CVEs and severity levels.roles/artifactregistry.reader), granting the host VM permission to pull the private image without exposing broader permissions.This solution relies entirely on serverless, managed Google Cloud services without introducing operational overhead, third-party registry dependencies, or insecure long-lived service account keys.
This option builds container images using external GitHub Actions and publishes them to a publicly accessible repository on Docker Hub, relying on default Compute Engine service account permissions.
The workload only involved non-sensitive, open-source sample development environments that intentionally needed to be publicly distributed.
This approach relies on individual developers or administrators manually executing local docker build and docker push commands on their local machines, while granting overly broad administrative permissions (roles/owner) to the workstation service account.
roles/owner) to a workstation runtime service account is a severe security anti-pattern that violates least-privilege principles. Workstations only require the read-only Artifact Registry Reader role (roles/artifactregistry.reader).You were performing one-time local testing or prototyping in an isolated non-production sandbox without automation or security compliance requirements.
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