Instance templates in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an instance template in Google Cloud Platform?

An instance template is a reusable configuration that defines the settings for virtual machine instances, like machine type, boot disk image, and network settings. It helps create consistent VM instances easily.

beginner

Why use instance templates instead of creating VM instances manually?

Instance templates save time and reduce errors by letting you create many VM instances with the same settings quickly. They ensure consistency and simplify scaling your infrastructure.

intermediate

Can you change an instance template after creating it?

No, instance templates are immutable. To change settings, you create a new template and use it for new instances or managed instance groups.

intermediate

How do instance templates relate to managed instance groups?

Managed instance groups use instance templates to create and manage identical VM instances automatically, helping with load balancing and auto-scaling.

beginner

What are some key settings you define in an instance template?

You define machine type, boot disk image, network tags, metadata, and service accounts in an instance template.

What is the main purpose of an instance template in GCP?

A To create firewall rules

B To store data permanently

C To define a reusable VM configuration

D To monitor VM performance

Instance templates define reusable VM configurations for creating consistent instances.

Can you edit an existing instance template in GCP?

A No, you must create a new template

B Only if no instances use it

C Yes, anytime

D Only through the API

Instance templates are immutable; you create a new one to change settings.

Which GCP service commonly uses instance templates to manage VM instances?

A Cloud Storage

B Managed Instance Groups

C Cloud Functions

D BigQuery

Managed Instance Groups use instance templates to create and manage VM instances.

Which of the following is NOT typically set in an instance template?

A Machine type

B Network tags

C Boot disk image

D User passwords

User passwords are not set in instance templates; security is managed differently.

Why are instance templates useful for scaling VM instances?

A They allow quick creation of identical VMs

B They reduce VM costs automatically

C They monitor VM health

D They backup VM data

Instance templates enable fast creation of identical VM instances, helping scale easily.

Explain what an instance template is and why it is useful in Google Cloud Platform.

Think about how you can create many similar VMs without repeating settings.

Describe how instance templates work with managed instance groups to support auto-scaling.

Consider how groups of VMs grow or shrink automatically using templates.

Practice

1. What is the main purpose of an instance template in Google Cloud Platform?

easy

A. To store data permanently for virtual machines

B. To manage user access to virtual machines

C. To monitor the performance of virtual machines

D. To save VM configuration settings for creating identical instances quickly

Solution

1. Step 1: Understand what instance templates store

   Instance templates save the configuration details like machine type, disk image, and network settings.

2. Step 2: Identify their main use

   They allow quick creation of many identical VM instances without repeating setup.

3. Final Answer:

   To save VM configuration settings for creating identical instances quickly -> Option D

4. Quick Check:

   Instance templates = VM settings saved [OK]

Hint: Instance templates store VM setup for easy reuse [OK]

Common Mistakes:

• Confusing instance templates with storage or monitoring
• Thinking instance templates manage user permissions
• Assuming instance templates hold data permanently

2. Which of the following is the correct gcloud command to create an instance template named web-template with machine type e2-medium?

easy

A. gcloud compute instance-templates new web-template --type=e2-medium

B. gcloud compute instance-templates create web-template --machine-type=e2-medium

C. gcloud compute instances create web-template --machine-type=e2-medium

D. gcloud create instance-template web-template --machine e2-medium

Solution

1. Step 1: Identify the correct gcloud command for instance templates

   The command to create instance templates starts with gcloud compute instance-templates create.

2. Step 2: Check the machine type flag

   The correct flag is --machine-type= followed by the machine type.

3. Final Answer:

   gcloud compute instance-templates create web-template --machine-type=e2-medium -> Option B

4. Quick Check:

   Correct command syntax = gcloud compute instance-templates create web-template --machine-type=e2-medium [OK]

Hint: Use 'instance-templates create' with '--machine-type' flag [OK]

Common Mistakes:

• Using 'instances create' instead of 'instance-templates create'
• Wrong flag names like '--machine' or '--type'
• Incorrect command order or missing 'compute'

3. Given this snippet:

gcloud compute instance-templates create my-template \
  --machine-type=n1-standard-1 \
  --image-family=debian-11 \
  --image-project=debian-cloud

What will be the machine type of instances created from my-template?

medium

A. debian-11

B. e2-medium

C. n1-standard-1

D. debian-cloud

Solution

1. Step 1: Identify the machine type flag in the command

   The flag --machine-type=n1-standard-1 sets the machine type.

2. Step 2: Understand other flags

   --image-family and --image-project specify the OS image, not machine type.

3. Final Answer:

   n1-standard-1 -> Option C

4. Quick Check:

   Machine type flag sets instance type [OK]

Hint: Look for '--machine-type' flag for VM size [OK]

Common Mistakes:

• Confusing image family with machine type
• Choosing project name as machine type
• Ignoring the '--machine-type' flag

4. You tried to create an instance template with this command:

gcloud compute instance-templates create test-template --machine-type e2-small

But it failed. What is the likely error?

medium

A. Missing image or boot disk specification

B. Instance template name 'test-template' is invalid

C. Machine type 'e2-small' does not exist

D. Command should be 'gcloud create instance-template'

Solution

1. Step 1: Check required arguments for instance-templates create

   Instance templates require a machine type AND a boot disk specification (e.g., --image-family and --image-project).

2. Step 2: Validate other parts

   The instance template name and machine type are valid, and the command starts correctly with gcloud compute instance-templates create. Flag syntax with space is accepted.

3. Final Answer:

   Missing image or boot disk specification -> Option A

4. Quick Check:

   Instance templates need image spec [OK]

Hint: Include --image-family & --image-project flags [OK]

Common Mistakes:

• Forgetting to specify image or boot disk flags
• Wrong command order or missing 'compute'
• Assuming machine type is invalid without checking

5. You want to create a managed instance group that automatically updates all VMs when the instance template changes. Which approach should you use?

hard

A. Create a managed instance group with the instance template and enable rolling updates

B. Manually delete and recreate each VM after changing the template

C. Use an unmanaged instance group with the new template

D. Create a new instance template but keep the old managed group unchanged

Solution

1. Step 1: Understand managed instance groups and updates

   Managed instance groups can use instance templates and support rolling updates to replace VMs smoothly.

2. Step 2: Identify the best method for automatic updates

   Enabling rolling updates on the managed group with the new template applies changes automatically.

3. Final Answer:

   Create a managed instance group with the instance template and enable rolling updates -> Option A

4. Quick Check:

   Managed groups + rolling updates = automatic VM updates [OK]

Hint: Use managed groups with rolling updates for auto changes [OK]

Common Mistakes:

• Thinking unmanaged groups support automatic updates
• Manually recreating VMs instead of using rolling updates
• Ignoring instance template updates in managed groups