Why did the pipeline fail to start?

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?
A . The CI server was not configured as a Git remote for the repository.
B . The webhook call from the code repository did not reach the CI server.
C . Configuration changes must be sent to the pipeline, which then updates the repository.
D . The pipeline must be started manually after the code repository is updated.

View Answer

Answer: C