Correct Answer: Increase the function timeout to 540s and scale memory to 1GB or 2GB to handle large payloads within the single invocation
Cloud Functions (2nd gen) support up to 60 minutes timeout and 32GB RAM. For large file processing, increasing timeout (up to 540s for 1st gen, 3600s for 2nd gen) and memory alloca...
Correct Answer
Increase the function timeout to 540s and scale memory to 1GB or 2GB to handle large payloads within the single invocation
Why This Answer Is Correct
Cloud Functions (2nd gen) support up to 60 minutes timeout and 32GB RAM. For large file processing, increasing timeout (up to 540s for 1st gen, 3600s for 2nd gen) and memory allocation is the simplest fix if the workload fits within one invocation. Cloud Run is better for complex, long-running or containerized workloads. Cloud Tasks adds asynchronous processing but increases complexity — better when you need reliable retry logic across distributed workloads.
A Cloud Function triggered by Pub/Sub is executing duplicate processing for some messages. Your team suspects at-least-once delivery is causing duplicate triggers. What is the recommended pattern to achieve exactly-once processing?
A developer uses Cloud Shell to run `gcloud` commands that modify production resources. As a Cloud Architect, what control should you implement to prevent accidental production changes from Cloud Shell?
A Cloud Architect needs to run a resource-intensive script (processing 10GB of data) that takes 2+ hours to complete. Cloud Shell sessions terminate after 20 minutes of inactivity. What is the best approach?
What persists between Cloud Shell sessions?
A developer needs to preview a web application running on port 8080 inside Cloud Shell without exposing it publicly. What feature enables this?