Centralize VM Image Management with VM Manager
Your organization relies heavily on virtual machines (VMs) in Compute Engine. Due to team growth and resource demands, VM sprawl is becoming problematic. Maintaining consistent security hardening and timely package updates poses an increasing challenge. You need to centralize VM image management and automate the enforcement of security baselines throughout the virtual machine lifecycle. What should you do?
Community Votes
60% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the distinction between runtime management (patching/config) and build-time image creation, identifying VM Manager as the tool for lifecycle enforcement rather than just static image building.
VM Manager is the designated service for centralizing patch management and configuration enforcement across Compute Engine VMs. Community consensus confirms that integrating it with a central image repository addresses both sprawl and security baseline automation.
Candidates often select Option C because it describes a robust CI/CD pipeline for hardened images, but this fails to address the ongoing requirement for timely package updates and runtime patching during the VM's lifecycle.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A correctly identifies Google Cloud VM Manager as the solution for centralized operational management. VM Manager provides agent-based capabilities to automatically distribute OS patches, manage configurations, and enforce compliance policies across fleets of VMs. By combining this with a central repository of hardened base images, you establish a consistent starting point and maintain it over time through automated updates.Why the Other Options Are Wrong
Option C focuses solely on the build phase via Cloud Build; while it creates secure images, it lacks the runtime agent required for continuous patching and drift remediation mentioned in the prompt. Option B relies on Policy Controller to restrict image sources, which is a governance control but does not automate the actual hardening or patching processes. Option D uses Security Command Center for monitoring and posture management, which detects issues but does not inherently perform the centralized management or automated patching actions described.Community Comment Notes
Comments [1] and [5] strongly support Option A, emphasizing that VM Manager handles both patching and configuration management. Comments [2], [3], and [6] argue for Option C, focusing on the 'image management' aspect, but they overlook the critical requirement for 'timely package updates' which requires a runtime agent like VM Manager.Official Reference
Exam Strategy
When questions mention 'centralized management,' 'patching,' or 'configuration enforcement' for running VMs, prioritize VM Manager over build-time tools like Cloud Build or static policies.
Frequently Asked Questions
Why isn't Cloud Build sufficient for VM image management?
Cloud Build only handles the image creation phase. It cannot patch or update already deployed VMs, which is required for ongoing security baselines.
Does VM Manager replace the need for hardened base images?
No. VM Manager manages the lifecycle (patches/config) of existing VMs. You still need hardened base images to ensure a secure starting state before deployment.