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 organization requires all development teams across multiple Google Cloud projects to provision Compute Engine virtual machines exclusively from standardized, security-hardened base images. These images must embed organizational security policies, required logging agents, and baseline development tooling from inception.
You need to establish an automated, centralized image architecture and governance strategy that meets the following requirements:
What should you do?
tar.gz archives, give developers Storage Object Viewer permissions, and have each team import the raw image file into their respective project.This option bakes images, exports the raw disk bytes to a Cloud Storage bucket using the disk.raw tar.gz format, and requires individual application teams to import and register the image inside their local project before launching VMs.
DEPRECATED, OBSOLETE) to seamlessly update downstream deployments.You needed to move virtual machine disk backups to an external air-gapped system, another cloud provider, or a project in an isolated Google Cloud organization that cannot establish cross-project IAM trust.
This option uses Google-provided public OS images (such as Debian or Ubuntu) as the boot disk and relies on runtime startup scripts to install monitoring agents, security software, and organizational configuration files every time an instance boots.
The environment required highly dynamic, fast-changing application code deployments where baking static VM images for every minor release creates too much pipeline latency.
roles/compute.imageUser) on the central project.This solution implements a centralized golden image factory architecture using Compute Engine custom images, image families, Identity and Access Management (IAM) least-privilege roles, and Organization Policy Service constraints.
family/. Compute Engine automatically provisions instances using the most recent, non-deprecated image in that family.constraints/compute.trustedImageProjects) at the organization or folder level blocks developers from launching boot disks from unauthorized public OS repositories or unvetted projects.roles/compute.imageUser gives development teams the exact permission (compute.images.useReadOnly) needed to instantiate disks without granting administrative rights over the images.gcloud compute images deprecate, allowing rollbacks while automatically pointing new VM creations to the newest release.This approach combines native Google Cloud resource governance mechanisms (Organization Policies and IAM) with Compute Engine Image Families, completely eliminating configuration drift and manual script updates while enforcing strict baseline security.
allAuthenticatedUsers with the Compute Image User role (roles/compute.imageUser), while distributing image release IDs to development teams for their provisioning scripts.This option creates custom images in a centralized project and exposes them globally to all authenticated Google Cloud identities using allAuthenticatedUsers, while requiring developers to hardcode specific image release names into infrastructure templates.
allAuthenticatedUsers exposes proprietary configurations, internal tooling, and agent setups to any external Google Cloud identity outside the organization.compute.trustedImageProjects), allowing development teams to continue deploying non-compliant public images.allAuthenticatedUsers includes any identity with a valid Google Account, completely bypassing organizational security boundaries.You were a public software vendor publishing open-source or commercial appliance images to the broader Google Cloud ecosystem on Cloud Marketplace.
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