Cloud Scheduler for cron jobs in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Cloud Scheduler in Google Cloud Platform?

Cloud Scheduler is a fully managed service that allows you to schedule and automate tasks, such as running cron jobs, at specified times or intervals.

beginner

How does Cloud Scheduler trigger a job?

Cloud Scheduler triggers jobs by sending HTTP requests, publishing messages to Pub/Sub topics, or invoking App Engine services at scheduled times.

beginner

What format does Cloud Scheduler use to define job schedules?

Cloud Scheduler uses the cron format, which specifies schedules with fields for minute, hour, day of month, month, and day of week.

intermediate

Why is Cloud Scheduler preferred over traditional cron jobs on a VM?

Cloud Scheduler is fully managed, reliable, scales automatically, and does not require managing servers or uptime, unlike traditional cron jobs on a VM.

intermediate

What permissions are needed to create and run Cloud Scheduler jobs?

You need the 'cloudscheduler.jobs.create' permission to create jobs and 'cloudscheduler.jobs.run' to run them. These are included in roles like 'Cloud Scheduler Admin'.

What service does Cloud Scheduler use to trigger asynchronous messages?

A Pub/Sub

B Cloud Storage

C BigQuery

D Cloud Functions

Cloud Scheduler can publish messages to Pub/Sub topics to trigger asynchronous processing.

Which of the following is NOT a valid way to trigger a Cloud Scheduler job?

A Sending an HTTP request

B Publishing a message to Pub/Sub

C Directly running a shell script on your local machine

D Invoking an App Engine service

Cloud Scheduler cannot run local shell scripts directly; it triggers cloud services remotely.

What is the correct cron expression to run a job every day at 3:30 AM?

A 3 30 * * *

B 30 3 * * *

C 30 15 * * *

D 0 3 * * *

The cron format is 'minute hour day month day-of-week'. '30 3 * * *' means 3:30 AM every day.

Which role includes permissions to create and manage Cloud Scheduler jobs?

A BigQuery User

B Storage Admin

C Compute Admin

D Cloud Scheduler Admin

The 'Cloud Scheduler Admin' role includes permissions to create and manage scheduler jobs.

Why is Cloud Scheduler considered more reliable than running cron jobs on a VM?

A It automatically scales and is fully managed by Google Cloud

B It requires manual server maintenance

C It only works during business hours

D It needs a dedicated VM for each job

Cloud Scheduler is fully managed and scales automatically, reducing maintenance and downtime.

Explain how Cloud Scheduler works to automate tasks in Google Cloud.

Think about how you set a timer to remind you, but for cloud tasks.

Describe the benefits of using Cloud Scheduler instead of traditional cron jobs on a virtual machine.

Consider the difference between managing your own alarm clock versus using a smart assistant.

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