Bird
0
0

A developer attempts to deploy a container image to Cloud Functions but encounters an error. What is the most probable reason?

medium📝 Debug Q6 of 15
GCP - Cloud Run
A developer attempts to deploy a container image to Cloud Functions but encounters an error. What is the most probable reason?
AThe container image is too large for Cloud Functions limits
BThe container image is missing a valid entry point
CCloud Functions does not support deploying arbitrary container images directly
DThe container image is not stored in a Google Container Registry
Step-by-Step Solution
Solution:
  1. Step 1: Understand Cloud Functions deployment model

    Cloud Functions only supports source code or prebuilt runtimes, not arbitrary container images.
  2. Step 2: Contrast with Cloud Run

    Cloud Run supports deploying any container image, but Cloud Functions does not.
  3. Final Answer:

    Cloud Functions does not support deploying arbitrary container images directly -> Option C
  4. Quick Check:

    Container images? Use Cloud Run, not Cloud Functions [OK]
Quick Trick: Cloud Functions can't deploy arbitrary containers; use Cloud Run instead [OK]
Common Mistakes:
  • Assuming Cloud Functions supports container images like Cloud Run
  • Blaming image size or registry location instead of service limitation
  • Ignoring the difference between Cloud Functions and Cloud Run deployment models

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes