Implementing DevOps Solutions and Practices Using Cisco Platforms (DEVOPS) — Question 5

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?

Answer options

• 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.

Correct answer: C

Explanation

The correct answer is C because the configuration changes must be sent to the pipeline for processing before any updates to the repository can occur. Option A is incorrect as the CI server not being a Git remote wouldn't directly prevent the pipeline from starting. Option B is also wrong because it refers to the delivery of webhook notifications, which is not the core reason for the pipeline's initiation failure. Option D is incorrect since it implies manual intervention is necessary, which contradicts the automation aspect of a CI/CD pipeline.