An enterprise is modernizing its application infrastructure and needs to select the appropriate serverless compute deployment models for two distinct backend services: Service A: A lightweight event processor that needs to trigger automatically upon new file uploads in Cloud Storage, process metadata in Python, and finish in under 30 seconds. The development team prefers to deploy source code directly without creating or managing container build configurations. Service B: A document-processing API written in C++ that relies on custom operating system packages and system-level shared libraries. The application is already built and packaged as an Open Container Initiative (OCI)-compliant container image and handles HTTP requests from internal client applications. Which serverless deployment architecture should the cloud architect recommend?

Deploy Service A as an event-driven Cloud Function with a Cloud Storage trigger, and deploy Service B as a containerized Cloud Run service.: What the Recommended Architecture Is This architecture pairs Cloud Functions (Cloud Run functions) for source-deployed, event-driven compute with Cloud Run for running arbitrary containerized web applications and microservices. How It Meets the Requirements Service A (Cloud Functions): Cloud Functions provides a source-centric deployment experience where developers deploy raw Python code directly without writing Dockerfiles or managing container registries. It integrates natively with Cloud Storage through Eventarc triggers, reacting instantly to object creation events with executions completing well within the platform's time limits. Service B (Cloud Run): Cloud Run is purpose-built to execute arbitrary container images listening on an HTTP port. It supports any programming language, including C++, and allows custom operating system libraries bundled within an OCI-compliant container image, making it ideal for existing containerized workflows. Key Advantages and Capabilities Source-to-Cloud deployment: Cloud Functions automatically builds and deploys code using underlying buildpacks, minimizing maintenance overhead for lightweight event handlers. Universal language and runtime portability: Cloud Run supports any binary, language, or system dependency packaged in a container container image. Automatic horizontal scaling: Both services scale automatically down to zero when idle and scale up rapidly to handle concurrent spikes. Granular triggers: Eventarc natively filters and delivers Cloud Storage mutation events directly to function instances. Why This Is Optimal This architecture leverages the specific strengths of both serverless products: source-based event simplicity for Service A and arbitrary runtime container execution for Service B.

Serverless Compute Selection Cloud Run Cloud Functions

IntermediateProfessional Cloud Architect

An enterprise is designing a decoupled, event-driven processing pipeline on Google Cloud. When new image files are uploaded to a private Cloud Storage bucket, an Eventarc trigger must capture the event and deliver it directly to a backend processing service. The backend service is hosted at an internal HTTP endpoint within a private Virtual Private Cloud (VPC) network and is addressed using an internal DNS domain name managed by Cloud DNS. To ensure private network connectivity and follow the principle of least privilege, which combination of networking and Identity and Access Management (IAM) configurations should you implement?

Serverless computing

IntermediateProfessional Cloud Architect

An e-commerce organization hosts a latency-sensitive public web service on Google Cloud using App Engine standard environment with automatic scaling. The service currently scales down to zero instances during inactive overnight periods to save costs. However, during sudden morning traffic spikes, users experience latency degradation caused by instance cold starts and request queuing before new instances can spin up. You need to optimize the autoscaling behavior to satisfy the following requirements: Eliminate cold-start latency for initial incoming morning requests Proactively scale out new instances based on concurrent connections before current instances reach full capacity Retain automatic scaling capabilities during high-traffic periods Which configuration should you specify in the application's automatic scaling configuration?

Serverless computing

IntermediateProfessional Cloud Architect

BigQuery ML Remote Models for Vertex AI

Cloud and technology improvements

IntermediateProfessional Cloud Architect

Cloud Logging, Cloud Trace, and Error Reporting

Troubleshooting/root cause analysis best practices

IntermediateProfessional Cloud Architect

An enterprise financial application hosted on Google Cloud requires strict business continuity targets. Stakeholders have established the following requirements: Recovery Point Objective (RPO): Near zero (synchronous data replication across zones to prevent transaction loss during a zonal outage) Recovery Time Objective (RTO): Under 5 minutes (automatic failover with minimal disruption) Failure scope: Must seamlessly tolerate a full zonal infrastructure failure without data loss or manual database failover procedures Which database and compute architecture on Google Cloud best aligns with these defined recovery objectives?

Business continuity

AdvancedProfessional Cloud Security Engineer

An enterprise operates automated, long-running data processing pipelines deployed across Compute Engine instances and Google Kubernetes Engine (GKE) clusters. These workloads continuously ingest data from Cloud Storage buckets and write analytics results into BigQuery datasets without end-user interaction. The security team previously discovered that some pipelines failed because they relied on human developer credentials that were suspended during employee offboarding. Which identity architecture should the organization implement to ensure stable, long-term authorization independent of user account lifecycles while enforcing the principle of least privilege?

Identifying scenarios requiring service accounts.

Professional Cloud Architect

Serverless Compute Selection Cloud Run Cloud Functions

Related questions

BigQuery ML Remote Models for Vertex AI

Cloud Logging, Cloud Trace, and Error Reporting

Professional Cloud Architect

Serverless Compute Selection Cloud Run Cloud Functions

What the Recommended Architecture Is

How It Meets the Requirements

Key Advantages and Capabilities

Why This Is Optimal

Related questions

BigQuery ML Remote Models for Vertex AI

Cloud Logging, Cloud Trace, and Error Reporting

What the Recommended Architecture Is

How It Meets the Requirements

Key Advantages and Capabilities

Why This Is Optimal