Your application development team has created Docker images for an application that will be deployed on Google Cloud. Your team does not want to manage the infrastructure associated with this applicat

Question

Options

• ACreate an instance template with the container image, and deploy a Managed Instance Group
• BUpload Docker images to Artifact Registry, and deploy the application on Google Kubernetes
• CUpload Docker images to the Cloud Storage, and deploy the application on Google Kubernetes
• DUpload Docker images to Artifact Registry, and deploy the application on Cloud Run.

• A
  7% (2)
• B
  4% (1)
• C
  11% (3)
• D
  78% (21)

Explanation

Option D is correct because Cloud Run is a fully managed serverless platform that natively accepts Docker images from Artifact Registry, requires zero infrastructure management, and automatically scales from zero to handle any traffic demand - perfectly matching all three requirements.

Why the others are wrong:

• A (Managed Instance Group): Requires managing VMs, instance templates, and autoscaling configuration - the team explicitly does not want to manage infrastructure.
• B (Google Kubernetes Engine): GKE still requires managing a Kubernetes cluster (node pools, upgrades, networking), which is infrastructure management, even if less than raw VMs.
• C (Cloud Storage + GKE): Double-wrong - Cloud Storage is for storing objects (files, backups), not Docker images (that's Artifact Registry's job), and GKE still involves infrastructure management.

Memory tip: Think of the two keywords - "no infrastructure management" → serverless → Cloud Run; "container image storage" → Artifact Registry (not Cloud Storage, which is for blobs). If a question pairs "Docker + no infra management + auto-scale," Cloud Run with Artifact Registry is almost always the answer.

No community discussion yet for this question.