Google ACE Practice Question: You have pushed a new container image to Artifact…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  `gcloud run deploy app --image us-central1-docker.pkg.dev/my-project/my-repo/app:v2.0 --region us-central1`

  Why this is correct

  This is the correct deployment command because it supplies the fully qualified Artifact Registry image URI, including the region (us-central1), project ID (my-project), repository name (my-repo), and the specific tag (v2.0). The --region flag independently sets the Cloud Run service region, ensuring the new revision is created in us-central1. This single command builds the container reference exactly as Cloud Run expects and immediately deploys it as a new revision of the existing 'app' service.

• ✗

  `gcloud run services update app --tag v2.0 --region us-central1`

  Why it's wrong here

  The gcloud run services update command with --tag v2.0 does not change the container image at all; it assigns a named traffic tag to an existing revision, which creates an alternate URL (e.g., v2.0---app-abc123.a.run.app) but does not trigger a new revision or deploy a different image version. To deploy a new container image, you must use gcloud run deploy with the --image flag or update the service with a new spec; a traffic tag is only a routing/manifestation mechanism for revision traffic splitting.

• ✗

  `docker push us-central1-docker.pkg.dev/my-project/my-repo/app:v2.0` followed by a Cloud Run auto-deploy.

  Why it's wrong here

  Pushing an image to Artifact Registry with docker push only places the container artifact into the repository; Cloud Run has no passive watcher that autodetects new pushes and redeploys a service. To achieve continuous deployment, you must explicitly configure a Cloud Build trigger that listens for pushes to the repository path, builds or validates the image, and then invokes gcloud run deploy (or equivalent) with the new image reference. Without that trigger, the push updates the repository but leaves the running Cloud Run service untouched.

• ✗

  `gcloud run deploy app --image app:v2.0 --region us-central1`

  Why it's wrong here

  Using --image app:v2.0 is invalid because Cloud Run requires a fully qualified container image URI that includes the registry host and path. Cloud Run can only pull images from a known registry (Artifact Registry or Container Registry) when the complete address is provided, such as us-central1-docker.pkg.dev/my-project/my-repo/app:v2.0 or gcr.io/my-project/app:v2.0. The short form 'app:v2.0' is not resolvable by Cloud Run, and the deployment will fail with an invalid image reference error.

Go deeper

Related to this question