Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team plans to use VM Manager to manage operating system patches and monitor compliance across a fleet of Compute Engine virtual machine (VM) instances in a Google Cloud project. You have already verified that the OS Config agent is installed on the guest operating systems.
What steps must you complete to enable the infrastructure and allow the OS Config agent to communicate with Google Cloud?
The Chronicle API and the Chronicle Service Agent role are security operations components used by Google SecOps to ingest telemetry, analyze security events, and manage security data lakes. Setting enable-guest-attributes allows instances to read and write guest attributes through the Compute Engine metadata server.
enable-guest-attributes exposes custom key-value guest attributes to the metadata server, but it does not activate the OS Config agent. The agent specifically listens for enable-osconfig=TRUE.roles/chronicle.serviceAgent) is designed for Google-managed security services, not for Compute Engine VM service accounts communicating with OS Config endpoints.The requirement was to integrate Compute Engine telemetry and audit logs with a Google SecOps (Chronicle) instance for centralized enterprise security monitoring.
While guest attributes are occasionally referenced when collecting VM metadata, VM Manager specifically requires the enable-osconfig key to establish communication between the VM and Google Cloud.
The Gemini for Google Cloud API (cloudaicompanion.googleapis.com) provides generative AI developer assistance and code completion. Setting block-project-ssh-keys=FALSE allows project-level SSH keys to grant access to the VM, and the Cloud Asset Owner role provides full control over Cloud Asset Inventory metadata.
block-project-ssh-keys metadata flag manages SSH access keys for user logins and does not interact with the OS Config background agent.roles/cloudasset.owner) is an administrative role for viewing and managing Google Cloud asset exports, not for agent-to-service communication.block-project-ssh-keys is used for instance-level SSH isolation, not OS configuration management.The goal was to configure developer access for Gemini Code Assist while ensuring standard project-level SSH connectivity for team members.
To allow any agent running on a VM to communicate with Google services, the specific service API (in this case, osconfig.googleapis.com) must be enabled rather than auxiliary AI or inventory APIs.
The Cloud Resource Manager API is used to manage organizational hierarchy, folders, projects, and IAM policies. Setting serial-port-logging-enable sends serial console output logs to Cloud Logging for debugging boot failures, while the Project Creator role allows identities to create brand-new projects.
serial-port-logging-enable flag controls serial console output ingestion into Cloud Logging. It does not control or enable the OS Config agent.roles/resourcemanager.projectCreator gives identities the ability to provision new Google Cloud projects. This represents a severe violation of the principle of least privilege and does not grant the permissions necessary to communicate with VM Manager APIs.You were configuring diagnostic boot logging for unresponsive virtual machines and setting up administrative service accounts for automated project provisioning pipelines.
VM Manager communication does not require project-level administrative permissions; it requires identity access to OS Config endpoints and metadata flags that signal the agent to start.
VM Manager is a suite of infrastructure management tools in Google Cloud used for managing operating systems on large fleets of Compute Engine virtual machine (VM) instances. It provides automated patch management, OS configuration management, and OS inventory management. The underlying communication between VM instances and Google Cloud services relies on the OS Config agent running inside each VM, which interacts directly with the OS Config API (osconfig.googleapis.com).
To fully configure the infrastructure for VM Manager, three foundational requirements must be satisfied:
enable-osconfig=TRUE must be applied either project-wide (as project metadata) or individually on each instance (as instance metadata) to instruct the guest agent to activate its communication loops.This approach directly configures all required communication prerequisites—API enablement, metadata activation, and identity credentials—allowing the OS Config agent to communicate securely and effectively with the VM Manager backend without unnecessary privileges or architectural workarounds.
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