Cloud Scheduler for cron jobs in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Cloud Scheduler Job Execution Frequency

You create a Cloud Scheduler job with the cron expression 0 9 * * 1-5. What is the behavior of this job?

A The job runs every day at 9:00 AM, Monday through Friday.

B The job runs every hour from 9 AM to 5 PM on weekdays.

C The job runs every minute on weekdays at 9 AM.

D The job runs only once at 9 AM on Monday.

💡 Hint

Recall how cron expressions define minutes, hours, and days of the week.

The cron expression 0 9 * * 1-5 means the job triggers at minute 0 of hour 9 on every day of the month, but only on weekdays (Monday=1 through Friday=5).

❓ Configuration

intermediate

Configuring Cloud Scheduler to Trigger a Pub/Sub Topic

You want a Cloud Scheduler job to publish a message to a Pub/Sub topic every hour. Which configuration is required in the job's target settings?

A Set the target type to HTTP and provide the Pub/Sub topic URL.

B Set the target type to Pub/Sub and specify the topic name and message body.

C Set the target type to App Engine and specify the topic name.

D Set the target type to Cloud Function and specify the topic name.

💡 Hint

Cloud Scheduler supports direct Pub/Sub targets.

To publish messages to Pub/Sub, Cloud Scheduler must have the target type set to Pub/Sub with the topic name and message payload configured.

❓ security

advanced

Ensuring Least Privilege for Cloud Scheduler Job Permissions

You have a Cloud Scheduler job that triggers a Cloud Function. What is the best practice to ensure the job has the least privilege needed?

A Grant the Cloud Scheduler service account the 'Owner' role on the Cloud Function.

B Grant the Cloud Scheduler service account the 'Editor' role on the entire project.

C Grant the Cloud Scheduler service account the 'Cloud Functions Invoker' role only on the specific function.

D No permissions are needed because Cloud Scheduler can invoke any function by default.

💡 Hint

Think about the principle of least privilege and role scopes.

Granting only the 'Cloud Functions Invoker' role on the specific function limits permissions to what is necessary, avoiding over-permissioning.

❓ Architecture

advanced

Designing a Reliable Retry Strategy for Cloud Scheduler Jobs

You have a Cloud Scheduler job that triggers an HTTP endpoint. Sometimes the endpoint is temporarily unavailable. Which retry configuration ensures the job retries with exponential backoff up to 5 attempts?

A Set max retry attempts to 5 and enable exponential backoff in the retry policy.

B Set max retry attempts to 5 with fixed interval retries every 10 seconds.

C Set max retry attempts to unlimited with no backoff.

D Disable retries and rely on manual reruns.

💡 Hint

Exponential backoff helps reduce load during outages.

Configuring max attempts to 5 with exponential backoff retries helps handle temporary failures gracefully without overwhelming the endpoint.

✅ Best Practice

expert

Optimizing Cloud Scheduler for Multi-Region High Availability

You want to ensure a Cloud Scheduler job triggers reliably even if one region fails. What is the best architecture to achieve multi-region high availability?

A Deploy a single Cloud Scheduler job in the default region and rely on Google’s internal failover.

B Schedule jobs only in the region closest to your users to reduce latency.

C Use Cloud Scheduler with a global setting that automatically replicates jobs across regions.

D Deploy identical Cloud Scheduler jobs in multiple regions with the same schedule and use a deduplication mechanism downstream.

💡 Hint

Cloud Scheduler jobs are regional; think about redundancy strategies.

Cloud Scheduler does not replicate jobs globally. Deploying identical jobs in multiple regions with deduplication downstream ensures availability if one region fails.

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