A team is using Cloud Functions with a Cloud Storage trigger. They notice that sometimes the function does not execute after a file is uploaded. What is the most likely cause?
Trap 1: The function's memory limit is too low
Incorrect. Memory limit affects execution, not triggering. The function would still be invoked but might fail during execution.
Trap 2: The Cloud Storage bucket has object versioning enabled which…
Incorrect. Object versioning does not prevent the finalize event from firing. New versions still trigger the event.
Trap 3: The function has too many concurrent invocations
Incorrect. Too many concurrent invocations might cause throttling but not total failure to trigger the function.
- A
The Cloud Functions region is different from the bucket region
Correct. If the function and bucket are in different regions, events will not be delivered.
- B
The function's memory limit is too low
Why wrong: Incorrect. Memory limit affects execution, not triggering. The function would still be invoked but might fail during execution.
- C
The Cloud Storage bucket has object versioning enabled which changes event semantics
Why wrong: Incorrect. Object versioning does not prevent the finalize event from firing. New versions still trigger the event.
- D
The function has too many concurrent invocations
Why wrong: Incorrect. Too many concurrent invocations might cause throttling but not total failure to trigger the function.