Project configuration in GCP - Step-by-Step Execution

Process Flow - Project configuration

Start: Create GCP Project

↓

Set Project ID & Name

↓

Enable APIs & Services

↓

Configure IAM Roles

↓

Set Billing Account

↓

Deploy Resources

↓

Project Ready for Use

This flow shows the steps to set up a Google Cloud project from creation to ready state.

Execution Sample

GCP

gcloud projects create my-project-12345 --name="My Project"
gcloud services enable compute.googleapis.com --project=my-project-12345

# Assign roles
gcloud projects add-iam-policy-binding my-project-12345 --member="user:[e-mail]" --role="roles/viewer"

This code creates a GCP project, enables Compute Engine API, and assigns a viewer role to a user.

Process Table

Step	Action	Input/Command	Result	Notes
1	Create Project	gcloud projects create my-project-12345 --name="My Project"	Project 'my-project-12345' created	Project ID must be unique
2	Enable API	gcloud services enable compute.googleapis.com --project=my-project-12345	Compute Engine API enabled	Enables VM and related services
3	Add IAM Role	gcloud projects add-iam-policy-binding my-project-12345 --member="user:[e-mail]" --role="roles/viewer"	User [e-mail] granted viewer role	Allows read-only access
4	Set Billing	gcloud billing projects link my-project-12345 --billing-account=000000-000000-000000	Billing account linked	Project can now use billable services
5	Deploy Resources	gcloud compute instances create vm-1 --project=my-project-12345 --zone=us-central1-a	VM instance 'vm-1' created	Resource deployed in project
6	Project Ready	-	Project configured and ready	All steps completed successfully

💡 All configuration steps completed; project is ready for use.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Project ID	none	my-project-12345	my-project-12345	my-project-12345	my-project-12345	my-project-12345	my-project-12345
APIs Enabled	none	none	compute.googleapis.com	compute.googleapis.com	compute.googleapis.com	compute.googleapis.com	compute.googleapis.com
IAM Roles	none	none	none	user:[e-mail]:viewer	user:[e-mail]:viewer	user:[e-mail]:viewer	user:[e-mail]:viewer
Billing Linked	no	no	no	no	yes	yes	yes
Resources Deployed	none	none	none	none	none	vm-1 instance	vm-1 instance

Key Moments - 3 Insights

Why do we need to enable APIs after creating the project?

Enabling APIs (see step 2 in execution_table) activates specific services like Compute Engine, without which you cannot create resources related to those services.

What happens if billing is not linked to the project?

Without billing linked (step 4), you cannot use billable services or deploy resources that cost money, so deployment (step 5) would fail.

Why assign IAM roles during project setup?

Assigning IAM roles (step 3) controls who can access or manage the project resources, ensuring proper permissions and security.

Visual Quiz - 3 Questions

Look at the execution_table, what is the project ID after step 1?

A my-project-12345

B none

C compute.googleapis.com

D vm-1 instance

💡 Hint

Check the 'Project ID' variable in variable_tracker after Step 1.

At which step is billing linked to the project?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Look at the 'Billing Linked' variable in variable_tracker and the execution_table actions.

If the Compute Engine API was not enabled, what would happen at step 5?

A VM instance would be created successfully

B Project would be deleted

C VM instance creation would fail

D Billing would be linked automatically

💡 Hint

Refer to step 2 and step 5 in execution_table about API enabling and resource deployment.

Concept Snapshot

Project configuration in GCP:
- Create project with unique ID
- Enable required APIs (e.g., Compute Engine)
- Assign IAM roles for access control
- Link billing account to use paid services
- Deploy resources inside the project
- Project ready when all steps complete

Full Transcript

To configure a Google Cloud project, first create it with a unique project ID and name. Then enable the APIs you need, such as Compute Engine for virtual machines. Next, assign IAM roles to users to control access. After that, link a billing account so the project can use billable services. Finally, deploy resources like VM instances inside the project. When all these steps are done, the project is ready to use.

Practice

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

easy

A. To monitor internet traffic

B. To store user passwords securely

C. To group and organize cloud resources and settings

D. To create virtual machines automatically

Solution

1. Step 1: Understand the role of a project in GCP

   A project acts as a container that holds all your cloud resources and settings together.

2. Step 2: Identify the correct purpose

   Among the options, grouping and organizing resources is the key function of a project.

3. Final Answer:

   To group and organize cloud resources and settings -> Option C

4. Quick Check:

   Project groups resources = D [OK]

Hint: Projects group resources and settings simply [OK]

Common Mistakes:

• Confusing projects with user accounts
• Thinking projects create resources automatically
• Assuming projects monitor traffic

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

easy

A. gcloud default project [PROJECT_ID]

B. gcloud project set default [PROJECT_ID]

C. gcloud set project default [PROJECT_ID]

D. gcloud config set project [PROJECT_ID]

Solution

1. Step 1: Recall the gcloud command syntax for setting default project

   The correct command uses 'gcloud config set project' followed by the project ID.

2. Step 2: Compare options

   Only gcloud config set project [PROJECT_ID] matches the correct syntax exactly.

3. Final Answer:

   gcloud config set project [PROJECT_ID] -> Option D

4. Quick Check:

   Set default project with 'config set project' = C [OK]

Hint: Use 'gcloud config set project' to set default [OK]

Common Mistakes:

• Mixing command order or keywords
• Using 'project set default' instead of 'config set project'
• Omitting 'config' keyword

3. Given the following commands run in order:
gcloud config set project my-project-123
gcloud projects describe my-project-123
What will the second command do?

medium

A. Describe the project with ID 'my-project-123' regardless of default project

B. Describe the currently set default project

C. Fail because the project is not set as default

D. List all projects in the account

Solution

1. Step 1: Understand the commands

   The first command sets the default project to 'my-project-123'. The second command describes the project with the given ID explicitly.

2. Step 2: Analyze the behavior of 'gcloud projects describe'

   This command describes the project specified by the ID argument, independent of the default project setting.

3. Final Answer:

   Describe the project with ID 'my-project-123' regardless of default project -> Option A

4. Quick Check:

   'gcloud projects describe' uses given ID, not default project = A [OK]

Hint: 'gcloud projects describe' uses explicit ID, not default [OK]

Common Mistakes:

• Assuming 'describe' uses default project if ID given
• Thinking it lists all projects
• Believing it fails without default project

4. You tried to set the default project with the command:
gcloud set project my-project-123
But it failed. What is the most likely reason?

medium

A. The command syntax is incorrect; 'config' keyword is missing

B. The project ID does not exist

C. You need to be logged in first

D. The project is already set as default

Solution

1. Step 1: Check the command syntax

   The correct command to set default project is 'gcloud config set project [PROJECT_ID]'. The given command misses the 'config' keyword.

2. Step 2: Evaluate other options

   While login and project existence matter, the error is most likely due to wrong syntax here.

3. Final Answer:

   The command syntax is incorrect; 'config' keyword is missing -> Option A

4. Quick Check:

   Missing 'config' in command causes failure = A [OK]

Hint: Remember 'gcloud config set project' syntax [OK]

Common Mistakes:

• Omitting 'config' keyword
• Assuming project existence error without checking syntax
• Ignoring login status

5. You want to create a new project with a unique ID and a friendly name using the gcloud CLI. Which command correctly achieves this?

hard

A. gcloud create project my-new-project --display-name="My Friendly Project"

B. gcloud projects create my-new-project --name="My Friendly Project"

C. gcloud projects new my-new-project --label="My Friendly Project"

D. gcloud project create --id=my-new-project --name="My Friendly Project"

Solution

1. Step 1: Recall the correct command to create a project

   The correct syntax is 'gcloud projects create [PROJECT_ID] --name="Friendly Name"'.

2. Step 2: Compare options to the correct syntax

   Only gcloud projects create my-new-project --name="My Friendly Project" matches the correct command and flag usage.

3. Final Answer:

   gcloud projects create my-new-project --name="My Friendly Project" -> Option B

4. Quick Check:

   Create project with 'projects create' and --name flag = B [OK]

Hint: Use 'gcloud projects create' with --name for friendly name [OK]

Common Mistakes:

• Using wrong command order or flags
• Confusing 'project' and 'projects' commands
• Using --display-name or --label instead of --name