Resource naming and labels in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding GCP resource naming constraints

Which of the following resource names are valid for a Google Cloud Storage bucket? (Select all that apply)

A my_bucket_2024

B my-bucket-2024

C my.bucket.2024

D MyBucket2024

💡 Hint

Bucket names must contain only lowercase letters, numbers, dashes (-), and dots (.). No uppercase letters or underscores.

Google Cloud Storage bucket names must be globally unique, 3-63 characters long, lowercase, and can include letters, numbers, dashes, and dots. Underscores are not allowed. Options B and C follow these rules. Option A contains underscores, which are invalid. Option D has uppercase letters.

❓ Configuration

intermediate

Applying labels to GCP Compute Engine instances

You want to add labels to a Compute Engine instance to identify its environment and owner. Which of the following gcloud commands correctly applies labels env=prod and owner=alice to an instance named web-server-1?

A gcloud compute instances set-labels web-server-1 --labels=env=prod,owner=alice

B gcloud compute instances add-labels web-server-1 --labels=env=prod,owner=alice

C gcloud compute instances update web-server-1 --labels env=prod owner=alice

D gcloud compute instances set-label web-server-1 env=prod owner=alice

💡 Hint

Use the set-labels command with the --labels flag and comma-separated key=value pairs.

The correct command to apply labels is gcloud compute instances set-labels with the --labels flag. Option A uses the correct syntax.

❓ Architecture

advanced

Designing label strategy for cost tracking

Your company wants to track cloud costs by project, team, and environment using labels. Which label key set follows GCP best practices for naming and helps avoid conflicts?

A cost_project, cost_team, cost_environment

B costing/project, costing/team, costing/environment

C gcp-project, gcp-team, gcp-environment

D project, team, environment

💡 Hint

Label keys should be simple, lowercase, and avoid special characters like slashes.

GCP recommends label keys to be lowercase, start with a letter, and contain only letters, numbers, underscores, and dashes. Option D uses simple keys without special characters or prefixes, which is best practice.

❓ security

advanced

Impact of labels on IAM policy enforcement

You want to restrict access to resources based on labels using IAM conditions. Which statement about using labels in IAM conditions is correct?

A Labels can be used in IAM conditions for any resource, regardless of label support.

B Labels can be used in IAM conditions only if the resource supports labels and the condition uses <code>resource.labels</code> attribute.

C IAM conditions cannot use labels; they only support resource names and types.

D Labels used in IAM conditions must be encrypted before use.

💡 Hint

Check if the resource supports labels and use the correct attribute in the condition.

IAM conditions can use labels only if the resource supports them, and the condition must reference resource.labels. Option B correctly states this.

❓ service_behavior

expert

Effect of label changes on billing reports

You update labels on a Google Cloud project resource. How soon will the updated labels appear in the billing reports for cost tracking?

A After 24 to 48 hours, due to billing data processing delays.

B Within a few minutes, as billing data updates in real-time.

C Immediately after the label update is saved.

D Only after the next monthly billing cycle.

💡 Hint

Billing data processing can take time before reflecting label changes.

Billing data and reports typically update with a delay of 24 to 48 hours after label changes due to batch processing. Option A is correct.

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