Courseiva

Cloud Digital Leader Fundamental Cloud Concepts Practice Question

A DevOps engineer notices that a Cloud Function is timing out after 9 minutes. The function performs a long-running data transformation. They need to increase the timeout. What is the maximum timeout they can set for a Cloud Function (1st gen)?

⚠ Common exam trap

GCDL often tests the exact numeric limits of Cloud Functions 1st gen vs 2nd gen, and candidates who remember '60 minutes' from Cloud Run or 2nd gen incorrectly pick it for a 1st gen question.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

9 minutes

For Google Cloud Functions (1st gen), the maximum configurable timeout is 9 minutes (540 seconds). The question states the function is already timing out at 9 minutes, which is the ceiling — the engineer cannot increase it further in 1st gen. To exceed 9 minutes, they must migrate to Cloud Functions 2nd gen (which supports up to 60 minutes) or use Cloud Run.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    15 minutes

    Why it's wrong here

    15 minutes exceeds the maximum timeout allowed for 1st gen Cloud Functions, which is hard-capped at 540 seconds (9 minutes). The deployment will be rejected if you try to set a value above this limit, so this option is not valid for a 1st gen function.

  • ✓

    9 minutes

    Why this is correct

    9 minutes (540 seconds) is the correct maximum timeout for 1st gen Cloud Functions. This is a platform-enforced hard limit; you can configure the timeout field to any value between 1 and 540 seconds, but values above that are not accepted.

  • ✗

    30 minutes

    Why it's wrong here

    30 minutes is not a supported timeout for 1st gen Cloud Functions, whose ceiling is 9 minutes. Even though 2nd gen functions and Cloud Run support timeouts up to 60 minutes, 30 minutes is not an available option for this generation and would fail configuration validation.

  • ✗

    60 minutes

    Why it's wrong here

    60 minutes is a valid timeout for 2nd gen Cloud Functions and Cloud Run, but it is far above the 9-minute maximum for 1st gen functions. The 1st gen service is restricted to 540 seconds per invocation, so this value cannot be used. This limitation is a common reason to migrate long-running workloads to 2nd gen.

Quick reference

Cloud Service Model Comparison

ModelYou ManageProvider ManagesExamples
IaaSOS, runtime, apps, dataHardware, hypervisor, networkingEC2, Azure VMs, GCP Compute Engine
PaaSApps and dataOS, runtime, middleware, hardwareElastic Beanstalk, Azure App Service
SaaSData and settings onlyEverything elseMicrosoft 365, Salesforce, Workday
FaaS / ServerlessFunction code onlyInfra, scaling, runtimeLambda, Azure Functions, Cloud Run
CaaSContainers and appsKubernetes, OS, hardwareEKS, AKS, GKE

About these practice questions

Courseiva writes every GCDL question from scratch — 848 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Google Cloud exam blueprint

This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.