Startup scripts for automation in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Startup Script Execution Timing on GCP VM

You add a startup script to a Google Compute Engine VM instance metadata to install software on boot. When exactly does this script run?

A Only once, the very first time the VM boots after creation.

B Every time the VM boots or restarts.

C Only when the VM is stopped and then started again, not on reboot.

D Only when the VM is manually triggered to run the script via SSH.

💡 Hint

Think about when startup scripts are designed to automate setup.

Startup scripts run every time the VM boots or restarts, ensuring the setup steps are applied on each boot.

❓ Configuration

intermediate

Correct Metadata Key for GCP Startup Script

Which metadata key must you use to add a startup script that runs on a Google Compute Engine VM instance?

A startup-script

B user-data

C init-script

D boot-script

💡 Hint

Check the official GCP documentation for the exact metadata key name.

The correct metadata key for startup scripts on GCP VM instances is 'startup-script'.

❓ security

advanced

Security Risk of Startup Scripts in GCP

What is a major security risk when using startup scripts on GCP VM instances?

A Startup scripts can expose sensitive data if they contain secrets in plain text.

B Startup scripts always run with limited permissions, so they cannot modify system files.

C Startup scripts are encrypted by default, so there is no risk of exposure.

D Startup scripts cannot access network resources, so they pose no security risk.

💡 Hint

Consider what happens if secrets are stored directly in scripts.

Storing secrets like passwords or API keys in plain text inside startup scripts can expose them to anyone with access to the metadata or VM.

❓ Architecture

advanced

Automating Software Installation with Startup Scripts

You want to ensure a custom monitoring agent is installed and running on all new VM instances automatically. Which approach best uses startup scripts for this?

A Manually SSH into each VM after creation and run the installation commands.

B Use a firewall rule to block all traffic except monitoring agent ports.

C Create a snapshot of a VM with the agent installed and use it as a base image for new VMs.

D Add a startup script in instance metadata that downloads, installs, and starts the agent on every boot.

💡 Hint

Think about automating installation at boot time without manual steps.

Startup scripts automate installation and startup of software on every boot, ensuring consistency across VMs.

🧠 Conceptual

expert

Effect of Startup Script Failure on VM Boot

If a startup script on a GCP VM instance fails during execution, what is the effect on the VM's boot process?

A The VM boots but disables network interfaces until the script succeeds.

B The VM fails to boot and enters a stopped state automatically.

C The VM continues booting normally; the startup script failure does not stop the boot.

D The VM boots but deletes the startup script from metadata automatically.

💡 Hint

Consider how startup scripts relate to the VM's core boot process.

Startup scripts run after the VM boots; failure in the script does not prevent the VM from booting.