Your team is running an on-premises ecommerce application. The application contains a complex set of microservices written in Python, and each microservice is running on Docker containers…

Question

Options

• AUse your existing CI/CD pipeline. Use the generated Docker images and deploy them to Cloud
• BUse your existing continuous integration and delivery (CI/CD) pipeline. Use the generated Docker
• CUse the existing codebase and deploy each service as a separate Cloud Function. Update the
• DUse your existing codebase and deploy each service as a separate Cloud Run. Use the same

• A
  76% (19)
• B
  8% (2)
• C
  12% (3)
• D
  4% (1)

Explanation

Option A is correct because Cloud Run is Google Cloud's serverless platform purpose-built for containerized workloads - it runs Docker images directly, making it a natural lift-and-shift target for an already-containerized application with zero refactoring required, and it natively supports environment variable configuration injection.

Option B is wrong likely because it targets a non-serverless or less appropriate destination (such as GKE or Compute Engine), which would require managing infrastructure rather than being truly serverless.

Option C is wrong because Cloud Functions is designed for single-purpose event-driven functions, not full microservices running inside Docker containers - migrating each service to Cloud Functions would require significant code refactoring, defeating the goal of reusing the existing codebase.

Option D is wrong because it suggests redeploying from the raw codebase rather than leveraging the existing Docker images already produced by the CI/CD pipeline, introducing unnecessary extra steps and diverging from the established build process.

Memory tip: Think "Docker = Cloud Run" - whenever an exam question involves existing containers needing a serverless home on GCP, Cloud Run is almost always the answer. Cloud Functions = code snippets; Cloud Run = containers.

No community discussion yet for this question.