Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data engineer needs to configure Cloud Scheduler to trigger a downstream HTTP endpoint that initiates a weekly BigQuery data aggregation job. The workflow has the following operational requirements:
Which Cloud Scheduler configuration satisfies these requirements?
* 1 * * 0, select the UTC time zone, and set the maximum retry duration to unlimited with App Engine strict delivery.This option sets an asterisk in the minute field (* 1 * * 0) and specifies an unlimited retry duration alongside App Engine target settings.
* 1 * * 0 triggers the job every single minute during the 1:00 AM hour (from 1:00 AM through 1:59 AM) on Sundays, resulting in 60 separate invocations rather than a single weekly run.*) in the minute position denotes wildcard matching (every minute).The task required continuous minute-by-minute execution exclusively during the 1:00 AM window on Sunday mornings to trigger an internal App Engine handler.
0 1 0 * *, select the America/New_York time zone, and enable linear retry polling.This option attempts to construct a cron schedule using an invalid day-of-month value (0), applies a regional North American time zone, and proposes linear retry polling.
1 and 31 (or an asterisk * for every day). A value of 0 is invalid syntax and fails validation.America/New_York) introduces clock shifts twice a year, causing irregular execution cadence.1 and cannot be 0 in standard unix-cron format.The target workflow specifically needed to align with New York local business hours (such as running strictly at 1:00 AM Eastern Time regardless of UTC shifts) and used valid syntax such as 0 1 * * 0.
0 1 * * 0, select the UTC time zone, and configure the job's retry policy with exponential backoff.Cloud Scheduler is a fully managed enterprise cron job service that enables automated, periodic execution of units of work across Google Cloud services and external endpoints. A Cloud Scheduler job combines a target destination (such as an HTTP/S endpoint, Pub/Sub topic, or App Engine application), a execution frequency defined using standard cron expressions, and execution parameters including time zone and retry policies.
0 1 * * 0): Standard unix-cron syntax consists of five fields: minute (0), hour (1), day of month (*), month (*), and day of week (0 for Sunday). This pattern ensures that the job triggers precisely at 01:00 every Sunday.X-CloudScheduler-ScheduleTime to assist downstream targets in avoiding duplicate execution side effects.This configuration leverages Cloud Scheduler's native scheduling syntax and built-in error handling. By combining standard unix-cron scheduling, UTC alignment, and exponential backoff retry settings, the pipeline achieves dependable automated triggering without requiring external orchestration infrastructure or custom retry scripts.
1 0 * * 7, select the UTC time zone, and configure an attempt deadline of zero seconds with no retries.This option specifies a misconfigured cron expression (1 0 * * 7) and sets an attempt deadline of zero seconds while disabling retry attempts completely.
1 0 * * 7 defines minute 1 and hour 0, which evaluates to 12:01 AM (00:01) rather than 1:00 AM (01:00). Standard unix-cron expects minute in the first field and hour in the second field.minute (0-59) hour (0-23) day-of-month (1-31) month (1-12) day-of-week (0-6).5xx or 429).The requirement specifically called for running a non-critical task at 12:01 AM where duplicate or retried invocations are strictly forbidden under any circumstances.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated