Why Instance states (running, stopped, terminated) in GCP? - Purpose & Use Cases

The Big Idea

What if you could instantly know which cloud machines are costing you money without opening each one?

The Scenario

Imagine you have many virtual machines (VMs) running on your computer, and you need to keep track of which ones are on, which are off, and which you have deleted.

Doing this by opening each VM one by one and checking its status is like walking through a big office and asking every person if they are working or on break.

The Problem

This manual checking is slow and tiring. You might forget to turn off some VMs, wasting money. Or you might accidentally delete a VM you still need because you lost track.

It's easy to make mistakes, and fixing them takes even more time.

The Solution

Cloud providers like GCP give clear states for each VM: running, stopped, or terminated.

This helps you quickly see what each VM is doing without opening it. You can automate actions based on these states, saving time and avoiding errors.

Before vs After

✗ Before

Check each VM status by logging into each one manually.

✓ After

Use GCP commands or dashboard to list VM states at once.

What It Enables

Instantly know and control your VMs' status to save money and keep your cloud organized.

Real Life Example

A company stops unused VMs automatically at night to reduce costs, then starts them again in the morning, all by checking instance states.

Key Takeaways

Manual VM status checks are slow and error-prone.

Instance states give clear, quick info about VM activity.

Using states helps automate management and save resources.

Practice

1. What does the RUNNING state of a Google Cloud VM instance indicate?

easy

A. The VM is paused and cannot be restarted

B. The VM is permanently deleted

C. The VM is active and ready to use

D. The VM is being created

Solution

1. Step 1: Understand VM states

   The RUNNING state means the virtual machine is powered on and operational.

2. Step 2: Compare with other states

   TERMINATED means stopped but restartable; DELETED means removed permanently.

3. Final Answer:

   The VM is active and ready to use -> Option C

4. Quick Check:

   RUNNING = active and ready [OK]

Hint: RUNNING means VM is active and ready [OK]

Common Mistakes:

• Confusing TERMINATED with RUNNING
• Thinking DELETED means stopped
• Assuming RUNNING means VM is paused

2. Which command correctly stops a running Google Cloud VM instance named my-vm using gcloud CLI?

easy

A. gcloud compute instances stop my-vm

B. gcloud compute instances delete my-vm

C. gcloud compute instances terminate my-vm

D. gcloud compute instances suspend my-vm

Solution

1. Step 1: Identify the correct stop command

   The command to stop a VM is gcloud compute instances stop.

2. Step 2: Check other commands

   delete removes the VM, terminate is not a valid gcloud command, suspend preserves memory state but is different from stop.

3. Final Answer:

   gcloud compute instances stop my-vm -> Option A

4. Quick Check:

   Stop VM = gcloud compute instances stop [OK]

Hint: Use 'stop' to halt VM without deleting [OK]

Common Mistakes:

• Using delete instead of stop
• Typing terminate which is invalid
• Confusing suspend with stop

3. Given this gcloud command output:

NAME    ZONE       STATUS
vm-1    us-central1-a  TERMINATED
vm-2    us-central1-a  RUNNING
vm-3    us-central1-a  TERMINATED

Which VM(s) can be restarted without creating a new instance?

medium

A. Only vm-2

B. vm-1 and vm-3

C. All vm-1, vm-2, and vm-3

D. None of them

Solution

1. Step 1: Understand TERMINATED state

   TERMINATED means the VM is stopped but can be restarted later.

2. Step 2: Identify which VMs are TERMINATED

   vm-1 and vm-3 are TERMINATED, so they can be restarted; vm-2 is already RUNNING.

3. Final Answer:

   vm-1 and vm-3 -> Option B

4. Quick Check:

   TERMINATED = restartable VMs [OK]

Hint: TERMINATED means stopped but restartable [OK]

Common Mistakes:

• Thinking RUNNING VMs need restart
• Assuming TERMINATED means deleted
• Selecting all VMs regardless of state

4. You tried to restart a VM but got an error saying the instance does not exist. What is the most likely cause?

medium

A. The VM was DELETED and no longer exists

B. The VM is in SUSPENDED state

C. The VM is in TERMINATED state

D. The VM is in RUNNING state

Solution

1. Step 1: Analyze error message

   Error 'instance does not exist' means the VM resource is gone.

2. Step 2: Match with VM states

   Only DELETED means the VM is removed permanently; RUNNING, TERMINATED, SUSPENDED still exist.

3. Final Answer:

   The VM was DELETED and no longer exists -> Option A

4. Quick Check:

   Deleted VM = does not exist error [OK]

Hint: Deleted VM no longer exists, causing errors [OK]

Common Mistakes:

• Confusing TERMINATED with DELETED
• Assuming STOPPED means deleted
• Ignoring error message meaning

5. You want to save costs by stopping a VM but keep its data and configuration intact for later use. Which state should you put the VM in, and why?

hard

A. RUNNING, because it keeps the VM active and ready

B. SUSPENDED, because it pauses the VM without data loss

C. DELETED, because it frees all resources immediately

D. TERMINATED, because it stops the VM but preserves data and allows restart

Solution

1. Step 1: Understand cost-saving states

   Stopping a VM saves costs but keeps data if the VM is TERMINATED.

2. Step 2: Evaluate options

   RUNNING uses full resources; DELETED removes VM and data; SUSPENDED preserves memory but standard stop uses TERMINATED.

3. Final Answer:

   TERMINATED, because it stops the VM but preserves data and allows restart -> Option D

4. Quick Check:

   Stop VM = TERMINATED state for cost saving [OK]

Hint: TERMINATED stops VM but keeps data for restart [OK]

Common Mistakes:

• Choosing RUNNING to save costs
• Deleting VM to save costs but losing data
• Choosing SUSPENDED instead of TERMINATED