An enterprise IoT organization is planning the Google Cloud serverless compute architecture for a real-time fleet analytics application. The architecture must support two distinct microservices:
1. Telemetry Streaming Service: Receives high-throughput bi-directional gRPC streaming requests from thousands of connected vehicles simultaneously. It requires a custom-compiled C++ telemetry parsing binary bundled within the execution environment.
2. Audit Logging Service: Executes lightweight Python logic triggered automatically whenever a raw sensor log file is written to a Cloud Storage bucket, extracting metadata and publishing a summary notification without requiring container image build pipelines.
Which of the following architectural decisions should the team select for these workloads? (Select TWO.)
- Deploy the Telemetry Streaming Service to Cloud Run, because Cloud Run supports gRPC HTTP/2 bi-directional streaming, custom container runtimes with arbitrary binaries, and high request concurrency per container instance.Answer
- BDeploy the Telemetry Streaming Service to Cloud Functions (1st gen), because 1st gen functions provide dedicated low-latency hardware isolation specifically optimized for low-level compiled C++ application binaries.
- Deploy the Audit Logging Service to Cloud Functions, because it seamlessly handles direct Cloud Storage event triggers and executes code snippets without necessitating custom container management.Answer
- DDeploy the Audit Logging Service to Compute Engine unmanaged instance groups, because Cloud Storage bucket object notifications cannot directly invoke serverless compute options on Google Cloud.