Pipeline scheduling and triggers in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding pipeline trigger types

Which pipeline trigger type will start a pipeline automatically when new code is pushed to the main branch?

A Webhook trigger

B Scheduled trigger

C Manual trigger

D Pull request trigger

💡 Hint

Think about what happens immediately after code changes are pushed.

A webhook trigger listens for events like code pushes and starts the pipeline automatically. Scheduled triggers run pipelines at set times. Manual triggers require user action. Pull request triggers start pipelines on PR events.

💻 Command Output

intermediate

Output of a cron schedule in pipeline config

Given this cron schedule in a pipeline YAML config, what is the next run time if today is Monday 10:00 AM?

schedule: '0 12 * * 1'

A Today at 12:00 PM

B Next Monday at 12:00 PM

C Tomorrow at 12:00 PM

D Today at 10:00 AM

💡 Hint

Check what the cron expression means: minute hour day month weekday.

The cron '0 12 * * 1' means every Monday at 12:00 PM. If today is Monday 10:00 AM, the next run is today at 12:00 PM.

🔀 Workflow

advanced

Pipeline trigger order with multiple triggers

A pipeline has both a scheduled trigger set for daily 2 AM and a webhook trigger on code push. If code is pushed at 1:50 AM, which triggers will start the pipeline and in what order?

A Only webhook trigger starts pipeline immediately at 1:50 AM

B Scheduled trigger runs at 2 AM, webhook ignored

C Webhook trigger starts pipeline at 1:50 AM, then scheduled trigger runs again at 2 AM

D Pipeline runs only once at 2 AM combining both triggers

💡 Hint

Consider if triggers are independent or if one cancels the other.

Webhook triggers start the pipeline immediately on code push. Scheduled triggers run at their set time regardless. Both triggers cause separate runs.

❓ Troubleshoot

advanced

Troubleshooting pipeline not triggering on code push

A pipeline with a webhook trigger does not start when code is pushed. Which is the most likely cause?

A The code push was to a branch not monitored by the webhook

B The pipeline is scheduled to run only at midnight

C The pipeline YAML file has syntax errors

D The webhook URL is incorrect or missing in the code repository settings

💡 Hint

Check the connection between the code repository and the pipeline system.

If the webhook URL is wrong or missing, the code repository cannot notify the pipeline system to start. Scheduled triggers and YAML errors do not affect webhook triggers directly. Branch filters can also cause issues but are less common than webhook misconfiguration.

✅ Best Practice

expert

Best practice for combining scheduled and event triggers

What is the best practice when configuring a pipeline with both scheduled and event-based triggers to avoid redundant runs?

A Disable one trigger type to avoid any overlap

B Use a flag file or state check in the pipeline to skip runs if recent event-triggered run occurred

C Set both triggers to run at the exact same time

D Ignore redundancy; pipelines can run multiple times without issues

💡 Hint

Think about how to prevent running the same work twice unnecessarily.

Using a flag or state check allows the pipeline to detect if a recent run already processed the latest changes, avoiding duplicate work. Disabling triggers or running simultaneously is not efficient. Ignoring redundancy can waste resources.