Instance states (running, stopped, terminated) in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you stop a Google Compute Engine instance?

You have a Google Compute Engine virtual machine instance currently in the running state. You issue a stop command on this instance. What is the resulting state and behavior of the instance?

A The instance state changes to <em>stopped</em>, the VM is shut down, and you stop incurring charges for the VM's CPU and memory, but persistent disk charges continue.

B The instance state changes to <em>terminated</em>, the VM is deleted permanently and all data on the persistent disk is lost.

C The instance state remains <em>running</em>, but the VM is paused and you continue to be charged for CPU and memory.

D The instance state changes to <em>stopped</em>, but the VM continues running in the background and you continue to be charged for CPU and memory.

💡 Hint

Think about what happens to billing and data when you stop a VM but do not delete it.

Stopping a VM shuts it down and changes its state to stopped. You stop paying for CPU and memory, but persistent disk charges continue because the disk still exists. The VM is not deleted.

🧠 Conceptual

intermediate

Which instance state indicates a VM has been permanently deleted?

In Google Cloud Platform, which instance state means the virtual machine no longer exists and cannot be restarted?

A Terminated

B Stopped

C Running

D Paused

💡 Hint

Consider which state means the VM is gone for good.

The terminated state means the VM has been deleted permanently and cannot be restarted. Running means active, stopped means shut down but still exists, paused is not a standard GCP state.

❓ Architecture

advanced

Designing a cost-efficient VM lifecycle using instance states

You want to design a system where your VM instances are only charged for CPU and memory during business hours (9am-5pm), but data must persist 24/7. Which instance state transitions should your automation perform daily?

A Create new instances at 9am, delete instances at 5pm.

B Start instances at 9am (state: running), stop instances at 5pm (state: stopped).

C Pause instances at 5pm, resume instances at 9am.

D Terminate instances at 5pm, recreate instances at 9am.

💡 Hint

Think about which states preserve data and reduce charges.

Starting instances at 9am and stopping at 5pm keeps data on persistent disks and stops CPU/memory charges outside business hours. Deleting or terminating would lose data or incur recreation overhead.

❓ security

advanced

Security implications of instance states in GCP

Which instance state poses the highest security risk if an attacker gains access to your Google Cloud project, assuming no additional protections?

A Stopped - attacker can start the VM and access data on disk.

B Terminated - attacker cannot access the VM or data because it is deleted.

C Running - attacker can access the live VM and data in memory.

D Paused - attacker can resume the VM and access data.

💡 Hint

Consider which state allows immediate access to running processes and memory.

A running VM is active and accessible, so an attacker can interact with the live system and data in memory. Stopped or terminated states require additional steps to access data.

✅ Best Practice

expert

Choosing the correct instance state for disaster recovery readiness

Your company requires that VM instances be quickly recoverable after a disaster, with minimal data loss and cost efficiency. Which instance state strategy best meets this requirement?

A Keep instances in <em>running</em> state 24/7 to ensure immediate availability.

B Pause instances during off-hours and resume during business hours.

C Terminate instances daily and recreate from backups when needed.

D Keep instances <em>stopped</em> with persistent disks and snapshots taken regularly for fast restart.

💡 Hint

Balance cost, recovery speed, and data safety.

Stopping instances preserves data on disks and allows quick restart. Regular snapshots add data protection. Running 24/7 is costly, terminating loses data, pausing is not a standard GCP state.