✅ Question 1 — Best use case for Cloud Run

Which scenario is best suited for using Cloud Run instead of Cloud Run functions?

❌ Resizing images on demand when requested by a user through a web interface.
❌ Generating thumbnails for images uploaded to a Cloud Storage bucket.
🟩 Hosting a dynamic web application that allows users to upload and share photos.
❌ Sending an email notification whenever a new document is added to a folder in Cloud Storage.

Explanation:

Cloud Run is ideal for full web applications, containers, custom runtimes, and long-running or HTTP-driven services.
Cloud Run functions are for small event-driven tasks like triggers from Storage, Pub/Sub, etc.

---

✅ Question 2 — Cloud Run Functions (select 3)

Cloud Run functions:

🟩 Can be used to extend Cloud services.
🟩 Is a scalable functions-as-a-service platform.
❌ Can only be invoked by sending HTTP requests.
❌ Require servers or VMs to be provisioned.
🟩 Is integrated with Cloud Logging.

Explanation:

• Cloud Run functions can be triggered by events, not only HTTP → so that option is ❌.

• No servers or VMs are needed (serverless).

• They integrate with Cloud Logging automatically.

• They extend Cloud services (e.g., react to Storage/PubSub events).

---

✅ Question 3 — Why use Cloud Run functions?

❌ Their application has a legacy monolithic structure they want to split into microservices.
❌ Cloud Run functions is the primary way to run C++ applications in Google Cloud.
❌ Cloud Run functions is a free service for hosting compute operations.
🟩 Their application contains event-driven code that they don’t want to provision compute resources for.

Explanation:

Cloud Run functions are best for event-driven, serverless execution where you don’t want to manage servers (e.g., triggers from Storage, Pub/Sub).

---

🧾 Summary Table

---