Projects as resource containers in GCP - Commands & Configuration

Introduction

When you use Google Cloud, you organize your resources inside projects. A project is like a box that holds all your cloud tools and settings together. This helps keep things neat and separate for different apps or teams.

When you want to keep your app's cloud resources separate from other apps to avoid confusion.

When you need to control who can access certain cloud resources by managing permissions at the project level.

When you want to track costs and billing separately for different apps or teams.

When you are starting a new app or service and want a clean space to build and manage resources.

When you want to apply policies or security settings that affect all resources inside a project.

Commands

This command creates a new Google Cloud project named 'Example Project' with the ID 'example-project-12345'.

Terminal

gcloud projects create example-project-12345 --name="Example Project"

Expected Output

Created project [example-project-12345].

→

--name - Sets the display name of the project.

This command lists all the Google Cloud projects you have access to, so you can see your projects and their IDs.

Terminal

gcloud projects list

Expected Output

PROJECT_ID           NAME             PROJECT_NUMBER

example-project-12345 Example Project  123456789012

This command sets the active project to 'example-project-12345' so that future commands run in the context of this project.

Terminal

gcloud config set project example-project-12345

Expected Output

Updated property [core/project].

This command shows detailed information about the project, such as its name, number, and lifecycle state.

Terminal

gcloud projects describe example-project-12345

Expected Output

createTime: '2024-06-01T12:00:00.000Z'

lifecycleState: ACTIVE

name: Example Project

projectId: example-project-12345

projectNumber: '123456789012'

Key Concept

If you remember nothing else from this pattern, remember: a Google Cloud project is your main container that holds and organizes all your cloud resources and settings.

Common Mistakes

Trying to create a project with an ID that is already taken.

Project IDs must be unique across all Google Cloud users worldwide, so duplicates are not allowed.

Choose a unique project ID by adding numbers or your company name to avoid conflicts.

Not setting the active project before running other gcloud commands.

Without setting the active project, commands may run in the wrong project or fail because no project is selected.

Always run 'gcloud config set project PROJECT_ID' to select the right project before managing resources.

Summary

Create a Google Cloud project to hold your resources using 'gcloud projects create'.

List your projects anytime with 'gcloud projects list' to see what you have.

Set the active project with 'gcloud config set project' so commands target the right place.

Describe a project with 'gcloud projects describe' to check its details and status.

Practice

1. What is the main purpose of a project in Google Cloud?

easy

A. To store files permanently

B. To run virtual machines only

C. To organize and manage cloud resources

D. To replace user accounts

Solution

1. Step 1: Understand the role of projects

   Projects act as containers that hold and organize all cloud resources.

2. Step 2: Compare options

   Only To organize and manage cloud resources correctly describes the main purpose of projects; others describe specific services or unrelated functions.

3. Final Answer:

   To organize and manage cloud resources -> Option C

4. Quick Check:

   Project = Resource container [OK]

Hint: Projects group resources for easy management [OK]

Common Mistakes:

• Thinking projects store files directly
• Confusing projects with virtual machines
• Believing projects replace user accounts

2. Which of the following is the correct way to create a new project using the gcloud CLI?

easy

A. gcloud projects new --name my-project

B. gcloud projects create my-project

C. gcloud project new my-project

D. gcloud create project my-project

Solution

1. Step 1: Recall gcloud project creation syntax

   The correct command to create a project is 'gcloud projects create PROJECT_ID'.

2. Step 2: Match options with correct syntax

   Only gcloud projects create my-project matches the correct syntax; others use wrong command order or keywords.

3. Final Answer:

   gcloud projects create my-project -> Option B

4. Quick Check:

   Correct CLI syntax = gcloud projects create my-project [OK]

Hint: Use 'gcloud projects create' to make projects [OK]

Common Mistakes:

• Swapping 'create' and 'projects' keywords
• Using 'new' instead of 'create'
• Incorrect command order

3. Given the following commands, what will be the output of gcloud projects list --filter="name:my-project" if a project named 'my-project' exists?

gcloud projects create my-project
 gcloud projects list --filter="name:my-project"

medium

A. A blank list with no projects

B. An error saying project not found

C. A list of all projects ignoring the filter

D. A list showing details of the project named 'my-project'

Solution

1. Step 1: Understand project creation and listing

   After creating 'my-project', it exists in the project list.

2. Step 2: Apply filter in list command

   The filter 'name:my-project' will show only projects matching that name, so it will show 'my-project'.

3. Final Answer:

   A list showing details of the project named 'my-project' -> Option D

4. Quick Check:

   Filter shows matching project = A list showing details of the project named 'my-project' [OK]

Hint: Filter lists only matching projects [OK]

Common Mistakes:

• Expecting error if project exists
• Thinking filter is ignored
• Assuming blank output after creation

4. You tried to create a project with the command gcloud projects create 123project but got an error. What is the most likely cause?

medium

A. Project ID cannot start with a number

B. You need to be logged in first

C. Project names must be longer than 10 characters

D. You must specify a billing account

Solution

1. Step 1: Check project ID naming rules

   Project IDs must start with a letter and can contain letters, numbers, and hyphens.

2. Step 2: Analyze the given project ID

   '123project' starts with numbers, violating the naming rule, causing the error.

3. Final Answer:

   Project ID cannot start with a number -> Option A

4. Quick Check:

   Project ID rules = Project ID cannot start with a number [OK]

Hint: Project IDs must start with a letter [OK]

Common Mistakes:

• Assuming login error without checking ID
• Thinking billing is required at creation
• Confusing project name with project ID rules

5. You want to organize your company's cloud resources by department and control access separately. Which approach using projects is best?

hard

A. Create one project per department and assign access roles per project

B. Create one project for the whole company and use folders for departments

C. Create multiple projects but assign all users full access to all projects

D. Use a single project and manage access only with IAM policies on resources

Solution

1. Step 1: Understand project use for organization and access

   Projects act as containers to group resources and control access via roles.

2. Step 2: Evaluate options for department separation and access control

   Creating one project per department allows clear separation and role assignment per project, matching best practice.

3. Final Answer:

   Create one project per department and assign access roles per project -> Option A

4. Quick Check:

   Separate projects = separate access [OK]

Hint: Use projects to separate departments and access [OK]

Common Mistakes:

• Giving all users full access defeats separation
• Relying only on IAM on resources is complex
• Using folders alone does not isolate resources