Artifact Registry creation in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Artifact Registry in Google Cloud?

Artifact Registry is a service in Google Cloud that stores and manages container images and language packages securely and reliably.

beginner

Which command creates a new Artifact Registry repository in Google Cloud?

The command is:
gcloud artifacts repositories create REPOSITORY_NAME --repository-format=FORMAT --location=LOCATION
Replace REPOSITORY_NAME, FORMAT (like docker), and LOCATION with your values.

intermediate

Why do you specify a location when creating an Artifact Registry repository?

The location defines where your artifacts are stored physically, which affects latency and compliance with data regulations.

intermediate

What repository formats can Artifact Registry support?

Artifact Registry supports formats like Docker images, Maven packages, npm packages, Python packages, and more.

intermediate

What IAM role is typically needed to create an Artifact Registry repository?

The role 'roles/artifactregistry.admin' or equivalent permissions are needed to create and manage Artifact Registry repositories.

Which gcloud command option specifies the repository format when creating an Artifact Registry repository?

A --format-repository

B --repository-format

C --repo-format

D --format

The correct option is --repository-format to specify the type of repository like docker or maven.

What is the default location if none is specified when creating an Artifact Registry repository?

A global

B us-east1

C us-central1

D No default; location is required

You must specify a location; there is no default location for Artifact Registry repositories.

Which of these is NOT a supported repository format in Artifact Registry?

A RubyGems

B npm

C Maven

D Docker

Artifact Registry does not currently support RubyGems format.

What IAM role allows a user to create Artifact Registry repositories?

A roles/storage.objectViewer

B roles/compute.admin

C roles/artifactregistry.admin

D roles/viewer

The roles/artifactregistry.admin role grants permissions to create and manage Artifact Registry repositories.

Which Google Cloud service is Artifact Registry replacing?

A Container Registry

B Cloud Storage

C Cloud Build

D Cloud Functions

Artifact Registry is the next-generation service replacing Container Registry for storing container images.

Explain the steps to create an Artifact Registry repository in Google Cloud.

Think about the command and required options.

Describe why choosing the right location for an Artifact Registry repository is important.

Consider performance and legal reasons.

Practice

1. What is the main purpose of creating an Artifact Registry in Google Cloud?

easy

A. To host virtual machines

B. To securely store and manage software packages

C. To monitor network traffic

D. To create databases

Solution

1. Step 1: Understand Artifact Registry purpose

   Artifact Registry is designed to store and manage software packages securely.

2. Step 2: Compare options with purpose

   Options B, C, and D relate to other services like Compute Engine, VPC, and Cloud SQL, not Artifact Registry.

3. Final Answer:

   To securely store and manage software packages -> Option B

4. Quick Check:

   Artifact Registry = Secure package storage [OK]

Hint: Artifact Registry = package storage, not VMs or databases [OK]

Common Mistakes:

• Confusing Artifact Registry with Compute Engine
• Thinking it manages databases
• Assuming it monitors network traffic

2. Which of the following is the correct command syntax to create an Artifact Registry repository with Docker format in region us-central1?

easy

A. gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1

B. gcloud artifacts create repository my-repo --format=docker --region=us-central1

C. gcloud create artifacts repository my-repo --format=docker --location=us-central1

D. gcloud artifacts repositories new my-repo --repository-format=docker --location=us-central1

Solution

1. Step 1: Recall correct gcloud command structure

   The correct command is 'gcloud artifacts repositories create' followed by repository name and flags '--repository-format' and '--location'.

2. Step 2: Match options with correct syntax

   gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1 matches the correct syntax exactly. Other options have wrong order or wrong flags.

3. Final Answer:

   gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1 -> Option A

4. Quick Check:

   Correct command syntax = gcloud artifacts repositories create my-repo --repository-format=docker --location=us-central1 [OK]

Hint: Use 'gcloud artifacts repositories create' with format and location [OK]

Common Mistakes:

• Using 'create' before 'artifacts repositories'
• Mixing up --region and --location flags
• Incorrect flag names like --format instead of --repository-format

3. What will be the result of running this command?

gcloud artifacts repositories create test-repo --repository-format=maven --location=us-east1

medium

A. Creates a Docker format repository ignoring the format flag

B. Fails because 'maven' is not a valid repository format

C. Creates a Maven format Artifact Registry repository in us-east1 region

D. Creates a repository but defaults location to global

Solution

1. Step 1: Check repository format validity

   'maven' is a valid repository format supported by Artifact Registry.

2. Step 2: Check location flag effect

   Specifying '--location=us-east1' sets the repository region correctly.

3. Final Answer:

   Creates a Maven format Artifact Registry repository in us-east1 region -> Option C

4. Quick Check:

   Valid format and location = Creates a Maven format Artifact Registry repository in us-east1 region [OK]

Hint: Supported formats include maven, docker, npm, etc. [OK]

Common Mistakes:

• Assuming 'maven' is invalid format
• Thinking location defaults to global if specified
• Believing format flag is ignored

4. You run this command but get an error:

gcloud artifacts repositories create my-repo --repository-format=pip --location=us-west1

What is the likely cause?

medium

A. Missing project flag in the command

B. The location 'us-west1' is invalid

C. Repository name 'my-repo' is invalid

D. The repository format 'pip' is not supported

Solution

1. Step 1: Verify supported repository formats

   Artifact Registry does not support 'pip' as a repository format; common formats are docker, maven, npm, etc.

2. Step 2: Check location and name validity

   'us-west1' is a valid location and 'my-repo' is a valid name; missing project flag usually defaults to current project.

3. Final Answer:

   The repository format 'pip' is not supported -> Option D

4. Quick Check:

   Unsupported format causes error = The repository format 'pip' is not supported [OK]

Hint: Check format spelling and support before creating repo [OK]

Common Mistakes:

• Assuming all language names are valid formats
• Ignoring error messages about format
• Thinking location or name is the problem

5. You want to create an Artifact Registry repository that supports both Docker and npm packages in the us-central1 region. What is the best approach?

hard

A. Create two separate repositories: one with format docker and one with format npm, both in us-central1

B. Create one repository with format docker,npm in us-central1

C. Create a repository with format docker and upload npm packages to it

D. Create a repository with format npm and upload docker images to it

Solution

1. Step 1: Understand repository format limitation

   Artifact Registry repositories support only one format each; you cannot mix formats in one repository.

2. Step 2: Plan repository creation accordingly

   To support both Docker and npm, create two repositories with respective formats in the same region.

3. Final Answer:

   Create two separate repositories: one with format docker and one with format npm, both in us-central1 -> Option A

4. Quick Check:

   One format per repo = Create two separate repositories: one with format docker and one with format npm, both in us-central1 [OK]

Hint: One repo = one format; use multiple repos for multiple formats [OK]

Common Mistakes:

• Trying to combine formats in one repository
• Uploading wrong package types to a repo
• Ignoring regional consistency