Compute commands (instances, disks) in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to list all Compute Engine instances in the current project.

GCP

gcloud compute instances [1]

Drag options to blanks, or click blank then click option'

Adelete

Bstart

Clist

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' instead of 'list' will try to make a new instance.

Using 'delete' will remove instances.

The list command shows all instances in your project.

2fill in blank

medium

Complete the command to create a new persistent disk named 'my-disk' of size 100GB in zone us-central1-a.

GCP

gcloud compute disks create my-disk --size=[1] --zone=us-central1-a

Drag options to blanks, or click blank then click option'

A100GB

B1TB

C10GB

D50GB

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the unit 'GB' causes errors.

Using a smaller size than requested.

The --size flag sets the disk size. Here, 100GB is the requested size.

3fill in blank

hard

Fix the error in the command to start an instance named 'web-server' in zone us-east1-b.

GCP

gcloud compute instances [1] web-server --zone=us-east1-b

Drag options to blanks, or click blank then click option'

Astop

Bcreate

Cdelete

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stop' will turn off the instance.

Using 'delete' removes the instance permanently.

The start command powers on a stopped instance.

4fill in blank

hard

Fill both blanks to create a new instance named 'app-server' in zone us-west1-b with machine type n1-standard-1.

GCP

gcloud compute instances [1] app-server --zone=[2] --machine-type=n1-standard-1

Drag options to blanks, or click blank then click option'

Acreate

Bdelete

Cus-west1-b

Dus-central1-a

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' instead of 'create'.

Specifying the wrong zone.

Use create to make a new instance and specify the correct zone us-west1-b.

5fill in blank

hard

Fill all three blanks to attach a disk named 'data-disk' to instance 'db-server' in zone us-east1-c with device name 'data1'.

GCP

gcloud compute instances [1] db-server --zone=[2] --disk=[3] --device-name=data1

Drag options to blanks, or click blank then click option'

Aattach-disk

Bus-east1-c

Cdata-disk

Ddetach-disk

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'detach-disk' instead of 'attach-disk'.

Wrong zone or disk name.

Use attach-disk to add a disk, specify the correct zone us-east1-c, and the disk name data-disk.

Practice

1. What does the command gcloud compute instances list do?

easy

A. It shows all virtual machines in your project.

B. It creates a new virtual machine.

C. It deletes a virtual machine.

D. It attaches a disk to a virtual machine.

Solution

1. Step 1: Understand the command purpose

   The command gcloud compute instances list is used to display existing virtual machines in your project.

2. Step 2: Compare with other options

   Creating, deleting, or attaching disks require different commands, not this one.

3. Final Answer:

   It shows all virtual machines in your project. -> Option A

4. Quick Check:

   List instances = show VMs [OK]

Hint: List commands show current resources, not create or delete [OK]

Common Mistakes:

• Confusing list with create or delete commands
• Not specifying resource type
• Assuming it modifies resources

2. Which of the following is the correct syntax to create a new VM instance named web-server in zone us-central1-a?

easy

A. gcloud instances create web-server --zone=us-central1-a

B. gcloud create instance web-server zone us-central1-a

C. gcloud compute instances create web-server --zone=us-central1-a

D. gcloud compute create instance web-server --zone us-central1-a

Solution

1. Step 1: Identify correct command structure

   The correct command starts with gcloud compute instances create followed by the instance name and zone flag.

2. Step 2: Check option syntax

   gcloud compute instances create web-server --zone=us-central1-a matches the correct syntax exactly with proper flags and order.

3. Final Answer:

   gcloud compute instances create web-server --zone=us-central1-a -> Option C

4. Quick Check:

   Create instance syntax = gcloud compute instances create web-server --zone=us-central1-a [OK]

Hint: Remember: 'gcloud compute instances create' + name + --zone [OK]

Common Mistakes:

• Mixing order of words in command
• Omitting 'compute' or 'instances'
• Using wrong flag format

3. What will be the output of the command gcloud compute disks list --filter="zone:(us-central1-a)" if there are two disks named disk1 and disk2 in zone us-central1-a and one disk named disk3 in zone us-east1-b?

medium

A. Lists disk1, disk2, and disk3

B. Shows an error due to filter syntax

C. Lists only disk3

D. Lists only disk1 and disk2

Solution

1. Step 1: Understand the filter usage

   The filter limits results to disks in zone us-central1-a only.

2. Step 2: Apply filter to disk list

   Disks disk1 and disk2 are in us-central1-a, so they appear; disk3 is in a different zone and is excluded.

3. Final Answer:

   Lists only disk1 and disk2 -> Option D

4. Quick Check:

   Filter by zone shows matching disks only [OK]

Hint: Filter narrows results to matching zone disks only [OK]

Common Mistakes:

• Assuming filter includes all disks
• Misreading filter syntax
• Expecting syntax error incorrectly

4. You run gcloud compute instances delete my-vm but get an error saying the zone is missing. What is the best fix?

medium

A. Add --project=PROJECT_ID flag instead.

B. Add the flag --zone=ZONE_NAME with the correct zone.

C. Run the command without any flags again.

D. Use gcloud delete instances my-vm instead.

Solution

1. Step 1: Identify missing required parameter

   The error indicates the zone is not specified, which is required to delete an instance.

2. Step 2: Correct the command by adding zone

   Adding --zone=ZONE_NAME specifies the location of the instance to delete.

3. Final Answer:

   Add the flag --zone=ZONE_NAME with the correct zone. -> Option B

4. Quick Check:

   Zone flag required for instance delete [OK]

Hint: Always specify zone when deleting or managing instances [OK]

Common Mistakes:

• Ignoring zone requirement
• Using wrong command syntax
• Assuming project flag fixes zone error

5. You want to create a new persistent disk named data-disk of size 100GB in zone europe-west1-b and attach it to an existing instance app-server. Which sequence of commands is correct?

hard

A. 1) gcloud compute disks create data-disk --size=100GB --zone=europe-west1-b2) gcloud compute instances attach-disk app-server --disk=data-disk --zone=europe-west1-b

B. 1) gcloud compute instances attach-disk app-server --disk=data-disk --zone=europe-west1-b2) gcloud compute disks create data-disk --size=100GB --zone=europe-west1-b

C. 1) gcloud compute disks create data-disk --zone=europe-west1-b2) gcloud compute instances attach-disk app-server --disk=data-disk

D. 1) gcloud compute disks create data-disk --size=100 --zone=europe-west1-b2) gcloud compute instances attach-disk app-server --disk=data-disk --zone=europe-west1-b

Solution

1. Step 1: Create the disk first with correct size and zone

   The disk must be created before attaching. 1) gcloud compute disks create data-disk --size=100GB --zone=europe-west1-b
   2) gcloud compute instances attach-disk app-server --disk=data-disk --zone=europe-west1-b uses correct size format '100GB' and specifies zone.

2. Step 2: Attach the created disk to the instance with zone specified

   Attaching requires the disk and instance zone flags; 1) gcloud compute disks create data-disk --size=100GB --zone=europe-west1-b
   2) gcloud compute instances attach-disk app-server --disk=data-disk --zone=europe-west1-b includes these correctly.

3. Final Answer:

   First create disk with size and zone, then attach with disk and zone flags. -> Option A

4. Quick Check:

   Create disk before attach, specify size with GB [OK]

Hint: Create disk before attach; size needs units like GB [OK]

Common Mistakes:

• Attaching disk before creating it
• Omitting size units (GB)
• Missing zone flags on commands