Cloud Tasks for async processing in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Cloud Tasks client.

GCP

from google.cloud import tasks_v2

client = tasks_v2.CloudTasksClient([1])

Drag options to blanks, or click blank then click option'

Aproject='my-project'

Bqueue='my-queue'

Clocation='us-central1'

Dclient_options=None

Attempts:

3 left

💡 Hint

Common Mistakes

Passing project or location directly to the client constructor causes errors.

Trying to pass queue name in client constructor is invalid.

The CloudTasksClient constructor accepts client_options as an optional argument. Passing None means default options are used.

2fill in blank

medium

Complete the code to build the fully qualified queue path.

GCP

parent = client.queue_path('[1]', 'us-central1', 'my-queue')

Drag options to blanks, or click blank then click option'

Aproject_id

Blocation

Cqueue_name

Dclient

Attempts:

3 left

💡 Hint

Common Mistakes

Passing location or queue name as the first argument causes errors.

Passing the client object instead of project ID.

The queue_path method requires the project ID as the first argument.

3fill in blank

hard

Fix the error in the task creation code by completing the blank.

GCP

task = {
    'http_request': {
        'http_method': tasks_v2.HttpMethod.POST,
        'url': '[1]',
        'headers': {'Content-Type': 'application/json'},
        'body': b'{"message": "Hello"}'
    }
}

Drag options to blanks, or click blank then click option'

Aexample.com/taskhandler

Bhttps://example.com/taskhandler

Chttp://example.com/taskhandler

Dftp://example.com/taskhandler

Attempts:

3 left

💡 Hint

Common Mistakes

Using URLs without https:// prefix causes errors.

Using http:// or ftp:// protocols is not allowed.

The URL must be a valid HTTPS URL starting with https:// for Cloud Tasks HTTP requests.

4fill in blank

hard

Fill both blanks to schedule a task with a delay of 60 seconds.

GCP

import datetime

schedule_time = datetime.datetime.utcnow() + datetime.timedelta(seconds=[1])
task['schedule_time'] = schedule_time.[2]()

Drag options to blanks, or click blank then click option'

A60

Btimestamp

Cisoformat

Dnow

Attempts:

3 left

💡 Hint

Common Mistakes

Using isoformat instead of timestamp causes errors.

Using now() instead of timestamp() is incorrect.

To schedule a task, add 60 seconds delay and convert to a timestamp using timestamp().

5fill in blank

hard

Fill all three blanks to create and send a task to the queue.

GCP

response = client.[1](
    parent=[2],
    task=[3]
)

Drag options to blanks, or click blank then click option'

Acreate_task

Bparent

Ctask

Ddelete_task

Attempts:

3 left

💡 Hint

Common Mistakes

Using delete_task instead of create_task.

Passing incorrect parameter names.

The method to send a task is create_task, with parameters parent and task.

Practice

1. What is the main purpose of Google Cloud Tasks in an application?

easy

A. To host static websites

B. To store large amounts of data

C. To provide real-time video streaming

D. To manage and execute asynchronous background work

Solution

1. Step 1: Understand Cloud Tasks role

   Cloud Tasks is designed to handle background jobs asynchronously, so the main app stays responsive.

2. Step 2: Compare options with Cloud Tasks purpose

   Storing data, streaming video, or hosting websites are not Cloud Tasks functions.

3. Final Answer:

   To manage and execute asynchronous background work -> Option D

4. Quick Check:

   Cloud Tasks = async background work [OK]

Hint: Cloud Tasks = async job manager, not storage or hosting [OK]

Common Mistakes:

• Confusing Cloud Tasks with storage services
• Thinking Cloud Tasks handles real-time streaming
• Assuming Cloud Tasks hosts websites

2. Which of the following is the correct way to create a Cloud Task using the Google Cloud Tasks client library in Python?

easy

A. client.create_task(parent=queue_path, task=task)

B. client.add_task(queue=queue_path, task=task)

C. client.new_task(queue=queue_path, task=task)

D. client.push_task(queue=queue_path, task=task)

Solution

1. Step 1: Recall Cloud Tasks Python client method

   The official method to create a task is create_task with parameters parent and task.

2. Step 2: Check other options for validity

   Methods add_task, new_task, and push_task do not exist in the client library.

3. Final Answer:

   client.create_task(parent=queue_path, task=task) -> Option A

4. Quick Check:

   Use create_task() to add tasks [OK]

Hint: Use create_task() method with parent and task params [OK]

Common Mistakes:

• Using non-existent methods like add_task or push_task
• Confusing parameter names like queue instead of parent
• Trying to create tasks without specifying the queue path

3. Given the following Python code snippet using Google Cloud Tasks client, what will be the output if the task is successfully created?

from google.cloud import tasks_v2
client = tasks_v2.CloudTasksClient()
queue_path = client.queue_path('my-project', 'us-central1', 'my-queue')
task = {"http_request": {"http_method": "POST", "url": "https://example.com/taskhandler"}}
response = client.create_task(parent=queue_path, task=task)
print(response.name)

medium

A. The full resource name of the created task

B. A boolean True indicating success

C. The URL of the task handler

D. An error message

Solution

1. Step 1: Understand create_task return value

   The create_task method returns a Task object, which includes the task's full resource name.

2. Step 2: Analyze the print statement

   Printing response.name outputs the full resource name string of the created task.

3. Final Answer:

   The full resource name of the created task -> Option A

4. Quick Check:

   response.name = task resource name [OK]

Hint: create_task returns Task object; print response.name for ID [OK]

Common Mistakes:

• Expecting a boolean or URL instead of resource name
• Confusing response with request parameters
• Assuming print outputs error on success

4. You wrote this code to create a Cloud Task but get an error: TypeError: create_task() got an unexpected keyword argument 'queue'. What is the likely cause?

medium

A. Incorrect HTTP method in the task definition

B. Missing authentication credentials

C. Using 'queue' instead of 'parent' as the parameter name

D. Queue does not exist

Solution

1. Step 1: Analyze the error message

   The error says create_task got an unexpected keyword argument 'queue', meaning 'queue' is not a valid parameter.

2. Step 2: Recall correct parameter name

   The correct parameter for specifying the queue is 'parent', not 'queue'.

3. Final Answer:

   Using 'queue' instead of 'parent' as the parameter name -> Option C

4. Quick Check:

   Use 'parent' param, not 'queue' [OK]

Hint: create_task uses 'parent' param, not 'queue' [OK]

Common Mistakes:

• Confusing parameter names in method calls
• Assuming error is due to credentials or queue existence
• Ignoring exact error message details

5. You want to delay task execution by 10 minutes using Cloud Tasks. Which field should you set in the task definition to achieve this?

hard

A. retry_config with max_attempts set to 10

B. schedule_time with a timestamp 10 minutes in the future

C. http_method set to DELAY

D. dispatch_deadline set to 10 minutes

Solution

1. Step 1: Identify how to delay task execution

   Cloud Tasks supports delaying execution by setting schedule_time to a future timestamp.

2. Step 2: Evaluate other options

   dispatch_deadline controls max execution time, http_method DELAY is invalid, retry_config controls retries, not delay.

3. Final Answer:

   schedule_time with a timestamp 10 minutes in the future -> Option B

4. Quick Check:

   Use schedule_time to delay tasks [OK]

Hint: Set schedule_time to future timestamp for delay [OK]

Common Mistakes:

• Confusing dispatch_deadline with scheduling
• Using invalid HTTP methods to delay tasks
• Misusing retry_config for delaying execution