Learn the key differences between scheduled and triggered events for code scanning in GitHub Advanced Security. Understand how each type of event is configured and when scans are run to secure your code effectively.
Table of Contents
Question
What is the difference between scheduled versus triggered events in code scanning?
A. Scheduled events are more difficult to configure than triggered events.
B. Scheduled events run based on a specified schedule and triggered events run on code events such a push.
C. Triggered events run less frequently than scheduled events.
Answer
B. Scheduled events run based on a specified schedule and triggered events run on code events such a push.
Explanation
Scheduled events are specified by the developer and triggered events are set by default but can also be configured by the developer.
Scheduled events and triggered events are two distinct ways to configure code scanning in GitHub Advanced Security, but they differ in when the scans are executed:
Scheduled Events:
- Run code scanning on a specified schedule that you configure, such as daily or weekly
- Allow you to set a recurring schedule to regularly scan your code for vulnerabilities
- Provide ongoing, periodic code scanning not tied to any specific code changes
Triggered Events:
- Run code scanning when certain events occur in your GitHub repository
- Triggered by code-related events such as pushes, pull requests, or merges
- Scan code as it is being changed and updated by developers
- Allow for more real-time, change-based scanning to catch issues quickly
So in summary, the key difference is that scheduled events run code scans on a predetermined, recurring schedule, while triggered events kick off scans in real-time as code is being modified through events like pushes and pull requests. Both are useful for maintaining code security but serve different purposes in your workflow.
GitHub Advanced Security certification exam assessment practice question and answer (Q&A) dump including multiple choice questions (MCQ) and objective type questions, with detail explanation and reference available free, helpful to pass the GitHub Advanced Security exam and earn GitHub Advanced Security certification.