Cloud Scheduler for cron jobs in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the frequency of the Cloud Scheduler job using a cron expression.

GCP

schedule: '[1]'

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

Aevery 5 minutes

B5 * * * *

C'*/5 * * * *'

D0 5 * * *

Attempts:

3 left

💡 Hint

Common Mistakes

Using natural language like 'every 5 minutes' instead of a cron expression.

Omitting quotes around the cron expression string.

The schedule field requires a valid cron expression string. The correct cron expression for every 5 minutes is '*/5 * * * *'.

2fill in blank

medium

Complete the code to specify the timezone for the Cloud Scheduler job.

GCP

timeZone: '[1]'

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

AUTC

BGMT+5

CPST

DAmerica/New_York

Attempts:

3 left

💡 Hint

Common Mistakes

Using timezone abbreviations like 'PST' which can be ambiguous.

Using GMT offsets instead of IANA timezone names.

The timeZone field expects an IANA timezone name like 'America/New_York' for correct scheduling.

3fill in blank

hard

Fix the error in the Cloud Scheduler job definition by completing the missing field for the HTTP target URL.

GCP

httpTarget:
  uri: '[1]'
  httpMethod: 'POST'

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

Ahttps://example.com/api/job

Bexample.com/api/job

Chttp://example.com/api/job

Dftp://example.com/api/job

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the scheme (http/https) in the URL.

Using 'http://' instead of 'https://'.

Using unsupported protocols like 'ftp://'.

The URI must be a valid HTTPS URL starting with 'https://'. Using 'http://' or missing the scheme causes errors.

4fill in blank

hard

Fill both blanks to define a Cloud Scheduler job with a Pub/Sub target and set the message body.

GCP

pubsubTarget:
  topicName: '[1]'
  data: '[2]'

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

Aprojects/my-project/topics/my-topic

Bmy-topic

CSGVsbG8gd29ybGQ=

DHello world

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the topic short name instead of full path.

Providing plain text instead of base64 encoded data.

The topicName must be the full resource path. The data must be base64 encoded string.

5fill in blank

hard

Fill all three blanks to configure a Cloud Scheduler job with an App Engine HTTP target, setting the service, version, and relative URI.

GCP

appEngineHttpTarget:
  service: '[1]'
  version: '[2]'
  relativeUri: '[3]'

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

Adefault

Bv1

C/tasks/cleanup

Dv2

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect service names.

Using version names that do not exist.

Omitting the leading slash in relativeUri.

The service is usually 'default' unless you have multiple services. Version is the deployed version like 'v1'. The relativeUri is the path to the handler.