Examkin

Question

Difficulty: MediumPlanning Serverless Compute Options (Cloud Run and Cloud Functions)

A digital asset management platform needs to deploy an image resizing service on Google Cloud. The service requires a custom-compiled C++ graphic library dependency, processes incoming HTTP POST requests with payloads up to 20 MB, and must handle multiple concurrent requests per container instance to reduce operational cost. The solution must scale to zero instances when idle. Which Google Cloud compute option should you recommend?

  1. Cloud Run, because it allows packaging custom system binaries into container images and supports multi-concurrency per instance.Answer
  2. B
    Cloud Functions (1st gen), because it automatically compiles system-level C++ binaries upon deployment and scales per request.
  3. C
    Compute Engine unmanaged instance group, because serverless services cannot process HTTP requests containing binary payloads.
  4. D
    Cloud Functions (2nd gen), because it provides dedicated node isolation without support for custom system libraries.

Answer

Cloud Run, because it allows packaging custom system binaries into container images and supports multi-concurrency per instance.
The correct choice highlights Cloud Run's ability to run custom container images containing any compiled binaries (such as C++ graphics libraries) while serving multiple concurrent HTTP requests per instance, making it both technically compatible and cost-efficient.

Step-by-Step Solution

1
Analyze the operational requirements: custom C++ binary dependencies, stateless HTTP workload, multi-concurrency per instance, and scaling to zero.
Identified that custom system libraries require custom container packaging.
Standard managed runtime environments in Cloud Functions do not allow arbitrary C++ library installations outside standard package managers.
2
Evaluate Cloud Run capabilities against requirements.
Cloud Run supports custom Docker/OCI container images (allowing custom C++ compilation) and configurable container concurrency (processing up to 80+ concurrent requests per instance).
Cloud Run combines serverless scaling-to-zero with the flexibility of custom container images and efficient request concurrency.

Key Concept

Evaluating serverless compute options based on runtime customization, binary dependencies, and concurrency model.
Rate this question

Topics

Planning Serverless Compute Options (Cloud Run and Cloud Functions)

More questions from this topic