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.

Practice

1. What is the main purpose of Google Cloud Scheduler?

easy

A. To store large amounts of data

B. To create virtual machines

C. To run tasks automatically at scheduled times

D. To monitor network traffic

Solution

1. Step 1: Understand Cloud Scheduler's role

   Cloud Scheduler is designed to run jobs automatically based on a schedule you set.

2. Step 2: Compare options with this role

   The incorrect options describe storing large amounts of data, creating virtual machines, and monitoring network traffic, which are other GCP services.

3. Final Answer:

   To run tasks automatically at scheduled times -> Option C

4. Quick Check:

   Cloud Scheduler = automatic task runner [OK]

Hint: Cloud Scheduler runs jobs on a timer, like an alarm clock [OK]

Common Mistakes:

• Confusing with storage or VM services
• Thinking it monitors traffic
• Assuming it manages databases

2. Which of the following is the correct format for a cron schedule in Cloud Scheduler?

easy

A. day month year hour minute

B. year month day hour minute

C. hour minute second day month

D. minute hour day month day-of-week

Solution

1. Step 1: Recall cron format used by Cloud Scheduler

   Cloud Scheduler uses the standard cron format: minute, hour, day of month, month, day of week.

2. Step 2: Match options to this format

   minute hour day month day-of-week matches this order exactly; others have incorrect sequences or extra fields.

3. Final Answer:

   minute hour day month day-of-week -> Option D

4. Quick Check:

   Cron format = minute hour day month day-of-week [OK]

Hint: Cron starts with minute, then hour, then day [OK]

Common Mistakes:

• Mixing up order of fields
• Including year field incorrectly
• Confusing day and month positions

3. Given this cron expression in Cloud Scheduler: 0 9 * * 1, when will the job run?

medium

A. Every Monday at 9:00 AM

B. Every day at 9:00 AM

C. Every hour on the first day of the month

D. Every Monday at 12:00 AM

Solution

1. Step 1: Decode the cron expression

   The expression means: minute=0, hour=9, day=any, month=any, day-of-week=1 (Monday).

2. Step 2: Interpret the schedule

   This runs the job every Monday at 9:00 AM.

3. Final Answer:

   Every Monday at 9:00 AM -> Option A

4. Quick Check:

   0 9 * * 1 = Monday 9 AM [OK]

Hint: Day-of-week 1 means Monday in cron [OK]

Common Mistakes:

• Thinking it runs daily
• Confusing day-of-week with day-of-month
• Mixing up hour and minute fields

4. You created a Cloud Scheduler job with cron expression 60 12 * * *. What is the issue?

medium

A. Minute value 60 is invalid; must be 0-59

B. Hour value 12 is invalid; must be 0-11

C. Day of month cannot be *

D. Cron expression is correct and will run daily at 12:00

Solution

1. Step 1: Check minute field validity

   The minute field must be between 0 and 59. 60 is invalid.

2. Step 2: Verify other fields

   Hour 12 is valid (represents noon), and day/month/day-of-week as * means every day.

3. Final Answer:

   Minute value 60 is invalid; must be 0-59 -> Option A

4. Quick Check:

   Minute must be 0-59, 60 is invalid [OK]

Hint: Minutes max at 59, 60 causes error [OK]

Common Mistakes:

• Using 60 for minutes
• Thinking hour 12 is invalid
• Assuming * is not allowed for day

5. You want a Cloud Scheduler job to run every weekday at 7:30 AM and trigger a Cloud Function via HTTP. Which cron expression and target setup is correct?

hard

A. Cron: 7 30 * * 1-5, Target: Pub/Sub topic

B. Cron: 30 7 * * 1-5, Target: HTTP with Cloud Function URL

C. Cron: 30 7 * * 0,6, Target: HTTP with Cloud Function URL

D. Cron: 30 7 * * *, Target: Cloud Storage bucket

Solution

1. Step 1: Choose correct cron expression for weekdays at 7:30 AM

   The expression 30 7 * * 1-5 means minute 30, hour 7, any day/month, weekdays (Monday=1 to Friday=5).

2. Step 2: Select proper target for Cloud Function trigger

   Cloud Scheduler triggers Cloud Functions via HTTP target using the function's URL.

3. Final Answer:

   Cron: 30 7 * * 1-5, Target: HTTP with Cloud Function URL -> Option B

4. Quick Check:

   Weekdays 7:30 AM + HTTP trigger = Cron: 30 7 * * 1-5, Target: HTTP with Cloud Function URL [OK]

Hint: Weekdays are 1-5 in cron; Cloud Functions use HTTP triggers [OK]

Common Mistakes:

• Swapping hour and minute
• Using weekend days instead of weekdays
• Wrong target type for Cloud Function