Cloud Tasks for async processing in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Cloud Tasks handle task retries by default?

When a task in Cloud Tasks fails to execute, what is the default behavior for retries?

A Cloud Tasks retries the task immediately without delay until it succeeds.

B Cloud Tasks retries the task only once after a fixed delay of 5 minutes.

C Cloud Tasks does not retry failed tasks automatically; manual retry is required.

D Cloud Tasks retries the task with exponential backoff and a maximum retry limit.

💡 Hint

Think about how systems avoid overwhelming services with repeated immediate retries.

Cloud Tasks uses exponential backoff with a maximum retry limit to avoid flooding the target service and to handle transient failures gracefully.

❓ Architecture

intermediate

Best architecture to process user uploads asynchronously with Cloud Tasks

You want to process user-uploaded images asynchronously to avoid blocking the upload response. Which architecture best uses Cloud Tasks?

A Upload images directly to Cloud Storage and process them synchronously in the upload request handler.

B Upload images directly to Cloud Storage, then enqueue a Cloud Task to process the image asynchronously.

C Upload images to the app server, process them immediately, then enqueue a Cloud Task for logging only.

D Upload images to the app server and store them locally before enqueuing a Cloud Task.

💡 Hint

Consider decoupling upload and processing to improve user experience.

Uploading directly to Cloud Storage and then enqueuing a Cloud Task for processing decouples upload from processing, improving responsiveness and scalability.

❓ security

advanced

Securing Cloud Tasks HTTP targets with authentication

You want to ensure that only Cloud Tasks can invoke your HTTP endpoint. Which method provides the best security?

A Allow all requests and rely on IP filtering to restrict access.

B Use a shared secret in the URL query parameters to authenticate requests.

C Configure Cloud Tasks to add an OIDC token in the Authorization header for the HTTP request.

D Use basic authentication with username and password in the HTTP headers.

💡 Hint

Think about secure, token-based authentication methods supported by Cloud Tasks.

Cloud Tasks supports OIDC tokens for authentication, which is more secure than shared secrets or basic auth and integrates well with Google Cloud IAM.

❓ Configuration

advanced

Configuring Cloud Tasks queue rate limits

You want to limit your Cloud Tasks queue to process no more than 10 tasks per second. Which configuration achieves this?

A Set the queue's maxRateLimit property to 10.

B Set the queue's maxConcurrentDispatches property to 10.

C Set the queue's maxTasksPerSecond property to 10.

D Set the queue's maxDispatchesPerSecond property to 10.

💡 Hint

Look for the property that controls how many tasks are dispatched per second.

The maxRateLimit property controls the rate at which tasks are dispatched from the queue, limiting it to 10 tasks per second.

✅ Best Practice

expert

Handling task deduplication in Cloud Tasks

You want to ensure that duplicate tasks are not processed multiple times in Cloud Tasks. Which approach is best?

A Implement idempotency in the task handler to safely process repeated tasks.

B Set the queue to discard tasks with identical payloads automatically.

C Rely on Cloud Tasks to automatically detect and discard duplicate payloads.

D Use task names with unique IDs and enable task name deduplication in Cloud Tasks.

💡 Hint

Think about how to handle duplicates at the processing level rather than relying on the queue.

Cloud Tasks does not automatically deduplicate tasks by payload. Implementing idempotency in the task handler ensures safe processing even if duplicates occur.