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.