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 organization is deploying a fleet of virtual machines in Compute Engine using an instance template. You need to ensure that every newly provisioned VM automatically collects and sends system metrics to Cloud Monitoring and logs to Cloud Logging. You want to automate this process to eliminate manual intervention and avoid configuration inconsistencies across the fleet.
Which method should you use to automatically install and run the Ops Agent on each VM instance?
A startup script is a script specified in Compute Engine instance metadata that automatically runs when a virtual machine boots up. When specified inside an instance template, the startup script executes on every single virtual machine provisioned from that template, ensuring uniform provisioning across both standalone VMs and Managed Instance Groups (MIGs).

apt, yum, or PowerShell).Using an instance template with a startup script delivers fully automated, repeatable, and hands-off installation. Compared to manual configuration via SSH or RDP, it prevents human error and works seamlessly with dynamic cloud architectures.
An uptime check is an external monitoring feature in Cloud Monitoring that periodically issues network requests (such as HTTP, HTTPS, or TCP pings) from geographically distributed servers to test whether a service or endpoint is publicly accessible and responding as expected.
The requirement were to periodically verify that a public-facing web server is responding with HTTP 200 OK status codes and to notify an on-call engineer when the endpoint experiences downtime.
Cloud Monitoring consumes metrics and logs produced by agents; it does not push software agents to instances via uptime checks. Package deployment must be handled by Compute Engine lifecycle tools such as startup scripts, VM Manager (OS Config), or custom images.
Manual installation involves an administrator using SSH (for Linux) or RDP (for Windows) to establish an interactive session with an individual VM after it has started, followed by manually executing shell commands to download and run the Ops Agent installation script.
This approach would be appropriate only for one-off troubleshooting, testing the Ops Agent in an isolated development environment, or evaluating custom agent configuration files on a single standalone virtual machine before rolling out an automated policy.
In modern cloud operations, manual SSH connections create unrepeatable environments. Best practices emphasize automating provisioning tasks through startup scripts, OS Config policies, or baked VM images.
A Local SSD is a high-performance physical solid-state drive that is directly attached to the physical server hosting the Compute Engine virtual machine. It is designed to provide maximum IOPS and extremely low latency for temporary storage.
The workload required a high-speed, non-durable scratch drive for temporary cache storage, memory paging, or database temporary tables where ultra-low latency is required and data loss upon instance termination is acceptable.
To ensure software is installed reliably and automatically during VM provisioning, developers should leverage startup scripts or bake the software into a custom persistent boot disk image rather than relying on ephemeral local block storage.
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