Why container registry matters in GCP - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the container image path in Google Container Registry.

GCP

image_path = "gcr.io/my-project/[1]"

Drag options to blanks, or click blank then click option'

Amy-image

Bmy-project

Ccontainer

Dregistry

Attempts:

3 left

💡 Hint

Common Mistakes

Using project ID again instead of image name

Using 'container' or 'registry' as image name

The container image path must include the image name after the project ID in Google Container Registry.

2fill in blank

medium

Complete the command to push a Docker image to Google Container Registry.

GCP

docker push [1]

Drag options to blanks, or click blank then click option'

Aregistry.hub.docker.com/my-image

Bdocker.io/my-image

Clocal/my-image

Dgcr.io/my-project/my-image

Attempts:

3 left

💡 Hint

Common Mistakes

Using Docker Hub paths instead of gcr.io

Using local image names without registry path

To push an image to Google Container Registry, use the full path starting with gcr.io followed by your project and image name.

3fill in blank

hard

Fix the error in the command to authenticate Docker with Google Container Registry.

GCP

gcloud auth configure-[1]

Drag options to blanks, or click blank then click option'

Akubectl

Bcontainer

Cdocker

Dgke

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kubectl' or 'gke' instead of 'docker'

Using 'container' which is not a valid option

The correct command is 'gcloud auth configure-docker' to allow Docker to authenticate with Google Container Registry.

4fill in blank

hard

Fill both blanks to create a command that lists images in Google Container Registry.

GCP

gcloud container images [1] gcr.io/my-project/[2]

Drag options to blanks, or click blank then click option'

Alist

Bdelete

Cmy-image

Ddescribe

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' or 'describe' instead of 'list'

Using project ID instead of image name in second blank

The command 'gcloud container images list' lists images, and you specify the image repository after the project path.

5fill in blank

hard

Fill all three blanks to tag a local Docker image before pushing it to Google Container Registry.

GCP

docker tag [1] gcr.io/[2]/[3]

Drag options to blanks, or click blank then click option'

Alocal-image

Bmy-project

Cmy-image

Ddocker-image

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up local and registry image names

Using incorrect project ID or image names

You tag your local image with the full Google Container Registry path including project and image name before pushing.

Practice

1. What is the main purpose of a container registry in cloud infrastructure?

easy

A. To write code for containers

B. To store and manage container images securely

C. To monitor container performance

D. To run containers directly on the cloud

Solution

1. Step 1: Understand container registry role

   A container registry is a place to keep container images safe and organized.

2. Step 2: Differentiate from other services

   Running containers or monitoring them are done by other services, not the registry.

3. Final Answer:

   To store and manage container images securely -> Option B

4. Quick Check:

   Container registry = secure storage [OK]

Hint: Registry stores images, not runs or monitors containers [OK]

Common Mistakes:

• Confusing registry with container runtime
• Thinking registry monitors container health
• Assuming registry writes code

2. Which of the following is the correct command to push a container image to Google Container Registry (GCR)?

easy

A. gcloud container push my-image

B. gcloud push container my-image

C. kubectl push my-image

D. docker push gcr.io/my-project/my-image

Solution

1. Step 1: Identify correct tool for pushing images

   Docker CLI is used to push images to GCR with the format docker push gcr.io/project/image.

2. Step 2: Eliminate incorrect commands

   Commands with gcloud push or kubectl push are invalid for pushing images.

3. Final Answer:

   docker push gcr.io/my-project/my-image -> Option D

4. Quick Check:

   Use docker push with gcr.io URL [OK]

Hint: Push images with docker push and gcr.io URL [OK]

Common Mistakes:

• Using gcloud or kubectl to push images
• Missing gcr.io prefix in image name
• Wrong command syntax

3. Given this snippet, what will happen when you run it?

docker tag my-app gcr.io/my-project/my-app:v1
docker push gcr.io/my-project/my-app:v1

medium

A. The image is pushed without tagging

B. The image is deleted from local storage

C. The image is tagged and pushed to Google Container Registry

D. The command will fail due to syntax error

Solution

1. Step 1: Understand docker tag command

   The docker tag command assigns a new name and tag to the local image.

2. Step 2: Understand docker push command

   The docker push command uploads the tagged image to the specified registry.

3. Final Answer:

   The image is tagged and pushed to Google Container Registry -> Option C

4. Quick Check:

   Tag then push = upload image [OK]

Hint: Tag image before push to registry [OK]

Common Mistakes:

• Assuming push deletes local image
• Pushing without tagging first
• Thinking commands have syntax errors

4. You tried to push a container image but got an error: denied: Permission denied. What is the most likely cause?

medium

A. You do not have permission to push to the registry

B. The image size is too large

C. You forgot to tag the image

D. Docker is not installed

Solution

1. Step 1: Analyze error message

   The error denied: Permission denied indicates access is blocked.

2. Step 2: Identify permission issue

   Permission errors usually mean the user lacks rights to push to the registry.

3. Final Answer:

   You do not have permission to push to the registry -> Option A

4. Quick Check:

   Permission denied = access issue [OK]

Hint: Check registry permissions if push is denied [OK]

Common Mistakes:

• Assuming tagging error causes permission denied
• Blaming image size for permission errors
• Ignoring Docker installation status

5. You want to deploy a new version of your app quickly and safely. How does using a container registry help in this process?

hard

A. It stores and versions container images for easy rollback

B. It automatically scales your app without configuration

C. It writes deployment scripts for you

D. It monitors app performance in real time

Solution

1. Step 1: Understand deployment needs

   Quick and safe deployment requires storing app versions to revert if needed.

2. Step 2: Role of container registry in versioning

   Container registries keep images with tags, enabling easy rollback to previous versions.

3. Step 3: Exclude unrelated features

   Scaling, script writing, and monitoring are done by other services, not the registry.

4. Final Answer:

   It stores and versions container images for easy rollback -> Option A

5. Quick Check:

   Registry = version control for containers [OK]

Hint: Registry keeps versions for safe rollback [OK]

Common Mistakes:

• Thinking registry auto-scales apps
• Expecting registry to write scripts
• Confusing registry with monitoring tools