Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company is building a containerized web application that will be hosted on Google Kubernetes Engine (GKE). You have created a Docker repository named app-repo located in the us-central1 region inside the Google Cloud project my-prod-project.
You need to properly tag the local image web-frontend with the version v1.0 so that it can be pushed to Artifact Registry and pulled by your GKE workloads.
Which image path follows the correct Artifact Registry tagging convention?
Artifact Registry organizes Docker and OCI-compliant container images using a standardized hierarchical Uniform Resource Identifier (URI) structure. The standard path structure for Docker repositories identifies the repository location, the registry service domain, the Google Cloud project ID, the repository name, the specific image name, and the tag.

To push and reference container images in Artifact Registry, the path must strictly follow the format:
LOCATION-docker.pkg.dev/PROJECT-ID/REPOSITORY/IMAGE:TAG
For this scenario:
us-central1docker.pkg.devmy-prod-projectapp-repoweb-frontendv1.0Combining these elements yields us-central1-docker.pkg.dev/my-prod-project/app-repo/web-frontend:v1.0.
us-central1) as the GKE cluster minimizes network latency during Pod scheduling and image pull operations, while eliminating cross-region egress charges.:v1.0) clearly pins the container version for Kubernetes Deployment manifests, enabling reproducible rollouts and rollbacks.This format is the standard naming scheme supported by Google Cloud Artifact Registry for Docker repositories. It allows the Docker client, Cloud Build, and GKE kubelets to resolve the exact host and repository endpoint to authenticate and fetch images securely.
This option incorrectly specifies us-central1 as a URL path segment rather than as a subdomain prefix on the hostname, and omits the required repository name.
app-repo repository name.us-central1) must precede -docker.pkg.dev as part of the hostname prefix (e.g., us-central1-docker.pkg.dev). Placing us-central1 in the path causes the client to misinterpret us-central1 as the Google Cloud project ID.PROJECT-ID.Artifact Registry used a centralized docker.pkg.dev host where the first URI path segment represented the region, which is not how Google Cloud organizes Artifact Registry domains.
This URI structure attempts to use the legacy Container Registry domain (gcr.io) while incorrectly mixing regional prefixes and repository namespaces.
docker.pkg.dev), whereas gcr.io represents the deprecated Container Registry.us.gcr.io or eu.gcr.io) and did not support custom repository names (app-repo) as intermediate namespaces. In Container Registry, paths were limited to [REGION.]gcr.io/PROJECT-ID/IMAGE:TAG.gcr.io) is the predecessor to Artifact Registry and is not recommended for new workloads.gcr.io repositories map directly to Cloud Storage buckets rather than dedicated Artifact Registry repository resources.us-central1.You were working with an existing legacy Google Container Registry repository configured with a multi-region endpoint such as us.gcr.io/my-prod-project/web-frontend:v1.0.
This string misconstructs the host header and adds an invalid docker/ subpath into the repository path.
LOCATION-docker.pkg.dev. Placing a dot (.) directly between the location and pkg.dev causes DNS resolution errors for Docker CLI and Kubernetes node image pullers.docker belongs in the host subdomain (us-central1-docker.pkg.dev), not as a separate path segment between the project ID and repository name.PROJECT-ID/REPOSITORY/IMAGE./docker/ corrupts the repository resolution in Artifact Registry.Google Cloud used generic top-level regional endpoints with format path parameters, but Artifact Registry enforces hostname-based protocol mapping.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated