Resource naming and labels in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of resource naming in GCP?

Resource naming helps identify and organize cloud resources clearly and consistently, making management easier and avoiding confusion.

beginner

What are labels in GCP and why are they useful?

Labels are key-value pairs attached to resources to group and filter them for billing, management, and automation purposes.

intermediate

Name two best practices for resource naming in GCP.

1. Use lowercase letters, numbers, and hyphens only.
2. Keep names short but descriptive to easily identify the resource purpose.

intermediate

How do labels help with billing in GCP?

Labels let you group resources by project, team, or environment so you can see detailed cost reports and track spending accurately.

beginner

What characters are NOT allowed in GCP resource names?

Spaces, uppercase letters, special characters like @, #, $, %, and underscores (_) are not allowed in resource names.

Which of the following is a valid GCP resource name?

A my-project-01

B MyProject01

C my_project_01

D my project 01

Valid names use lowercase letters, numbers, and hyphens only. 'my-project-01' fits this rule.

What is a label in GCP?

A A billing account number

B A resource name

C A type of virtual machine

D A key-value pair to organize resources

Labels are key-value pairs used to organize and filter resources.

Why should resource names be consistent?

A To avoid confusion and simplify management

B To increase resource speed

C To reduce billing costs

D To enable automatic backups

Consistent naming helps identify and manage resources easily.

Which character is NOT allowed in GCP resource names?

A -

B _

C a

D 1

Underscores (_) are not allowed in GCP resource names.

How can labels help with cost management?

A By encrypting billing data

B By reducing the price of resources

C By grouping resources to track spending by team or project

D By automatically deleting unused resources

Labels group resources so you can see detailed cost reports by team or project.

Explain why consistent resource naming and labeling are important in GCP.

Think about how you find things in a messy room versus a tidy one.

Describe best practices for creating resource names and labels in GCP.

Imagine naming folders on your computer clearly and tagging photos.

Practice

1. What is the main purpose of labels in Google Cloud Platform (GCP)?

easy

A. To organize and filter cloud resources using key-value pairs

B. To set the resource's IP address

C. To define the resource's billing account

D. To encrypt the resource data

Solution

1. Step 1: Understand what labels do in GCP

   Labels are simple key-value pairs attached to resources to help organize and filter them easily.

2. Step 2: Compare options with label purpose

   Only To organize and filter cloud resources using key-value pairs correctly describes labels as tools for organization and filtering.

3. Final Answer:

   To organize and filter cloud resources using key-value pairs -> Option A

4. Quick Check:

   Labels = Organize and filter resources [OK]

Hint: Labels are for organizing and filtering resources [OK]

Common Mistakes:

• Confusing labels with IP or billing settings
• Thinking labels encrypt data
• Assuming labels set resource addresses

2. Which of the following is a valid resource name in GCP?

easy

A. my-instance-01

B. My_Instance_01

C. instance@01

D. instance 01

Solution

1. Step 1: Recall GCP resource naming rules

   Resource names must be lowercase letters, numbers, and hyphens only, no spaces or special characters.

2. Step 2: Check each option

   my-instance-01 uses lowercase letters, numbers, and hyphens correctly. Options A, B, and C contain uppercase letters, spaces, special characters, or underscores, which are invalid.

3. Final Answer:

   my-instance-01 -> Option A

4. Quick Check:

   Valid names use lowercase, numbers, hyphens only [OK]

Hint: Valid names use only lowercase letters, numbers, and hyphens [OK]

Common Mistakes:

• Using uppercase letters in names
• Including spaces or special characters
• Using underscores instead of hyphens

3. Given these labels on a VM instance: {"env":"prod", "team":"alpha", "priority":"high"}, which filter will correctly select this instance?

medium

A. labels.env = "dev" OR labels.priority = "low"

B. labels.priority = "medium"

C. labels.team = "beta"

D. labels.env = "prod" AND labels.team = "alpha"

Solution

1. Step 1: Understand the instance's labels

   The instance has labels: env=prod, team=alpha, priority=high.

2. Step 2: Evaluate each filter

   labels.env = "prod" AND labels.team = "alpha" matches env=prod and team=alpha, so it selects the instance. Options A, C, and D do not match the instance's labels.

3. Final Answer:

   labels.env = "prod" AND labels.team = "alpha" -> Option D

4. Quick Check:

   Filter matches labels exactly [OK]

Hint: Match filter keys and values exactly to labels [OK]

Common Mistakes:

• Using wrong label keys or values
• Mixing AND/OR incorrectly
• Assuming partial matches select resource

4. You try to create a GCP resource with the name my_resource_01 but get an error. What is the likely cause?

medium

A. Resource names cannot start with a letter

B. Underscores are not allowed in resource names

C. Resource names must be uppercase

D. Resource names must contain spaces

Solution

1. Step 1: Recall resource naming restrictions

   GCP resource names allow only lowercase letters, numbers, and hyphens. Underscores are not allowed.

2. Step 2: Analyze the given name

   The name contains underscores, which violates the naming rules, causing the error.

3. Final Answer:

   Underscores are not allowed in resource names -> Option B

4. Quick Check:

   Underscores invalid in names [OK]

Hint: Avoid underscores; use hyphens instead [OK]

Common Mistakes:

• Thinking uppercase letters are required
• Assuming names must start with numbers
• Believing spaces are allowed

5. You want to organize your GCP resources by environment and project. Which is the best way to do this using naming and labels?

hard

A. Use labels only for billing, not for environment or project

B. Use random resource names and no labels

C. Use resource names like prod-db-01 and labels {"env":"prod", "project":"sales"}

D. Use resource names with spaces and no labels

Solution

1. Step 1: Understand best practices for naming and labeling

   Resource names should be descriptive and labels should add metadata for filtering and organization.

2. Step 2: Evaluate options for organizing by environment and project

   Use resource names like prod-db-01 and labels {"env":"prod", "project":"sales"} uses clear naming and labels for environment and project, making management easy. Other options ignore labels or use invalid names.

3. Final Answer:

   Use resource names like prod-db-01 and labels {"env":"prod", "project":"sales"} -> Option C

4. Quick Check:

   Descriptive names + labels = best organization [OK]

Hint: Combine clear names with labels for best organization [OK]

Common Mistakes:

• Ignoring labels for organization
• Using invalid characters in names
• Not linking names and labels logically