Configuration changes to the production network devices are performed by a CI/CD pipeline. The code repository and the CI tool are running on separate servers. Some configuration changes are pushed to the code repository, but the pipeline did not start.
Why did the pipeline fail to start?
- The CI server was not configured as a Git remote for the repository.
- The webhook call from the code repository did not reach the CI server.
- Configuration changes must be sent to the pipeline, which then updates the repository.
- The pipeline must be started manually after the code repository is updated.
Answer(s): B
Explanation:
A webhook is basically a callback URL that is triggered when certain events occur, such as a code commit. If the webhook call from the code repository does not reach the CI server, then the pipeline will not start. According to the Cisco Implementing DevOps Solutions and Practices using Cisco Platforms (DEVOPS) Study Manual, "A webhook is a web-based feature that enables a remote service to communicate with a local service, usually through a web server. Webhooks are used to trigger an action when a specific event occurs, usually in a remote service or application."