A CI/CD pipeline for a Go application fails during the build stage. The log shows: 'go: github.com/foo/bar@v1.2.3: read tcp 192.168.1.1:443: i/o timeout'. The go.mod file lists the dependency. The build runs on a self-hosted runner. What is the most likely cause of this failure?

The runner does not have Go installed.

The dependency version is incompatible with the Go version.

The runner cannot reach the Go module proxy.

The go.mod file has a syntax error.

A CI/CD pipeline fails, and the log shows an error in the deployment stage: 'Error: The process '/usr/bin/docker' failed with exit code 1'. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?

The application's database is not reachable.

The Docker daemon is not running on the runner.

The pipeline is using an incorrect Docker image tag.

The deployment script has a syntax error.

A CI/CD pipeline fails, and the log shows an error in the deployment stage: 'Error: Unable to connect to the server at https://api.example.com:443'. The application was working previously. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?

The pipeline is using an incorrect API key.

The application's database is not reachable.

The API endpoint is down or unreachable from the runner's network.

The deployment script has a syntax error.

A CI/CD pipeline for a Java application fails during the build stage. The log shows a dependency resolution error for a library that is hosted on a private Maven repository. The repository requires authentication. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?

The Maven settings.xml file on the runner does not contain the credentials for the private repository.

The pom.xml file has a typo in the repository URL.

The library version is not available in the private repository.

The runner does not have Java installed.

A CI/CD pipeline for a Java application fails during the test stage. The test report shows that a test for the user service failed. The test was passing in the previous build. The pipeline runs tests in a Docker container with a clean environment. The test uses a mock database. What is the most likely cause of this failure?

The test framework version has changed.

The application code has a bug that affects the user service.

The mock database is not being initialized in the test setup.

The test code has a bug that was introduced in the latest commit.

CiscoCertified DevNet Professional

Domain 4Objective 1

Diagnose a CI/CD Pipeline Failure (such as Missing Dependency, Incompatible Versions of Components, and Failed Tests) 350-901 Practice Questions (Page 3)

Part of the 4.0 Application Deployment and Security domain, which accounts for 20% of the 350-901 exam. Cisco does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–16 in this domain), expect 1–1 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

7concepts

20%of the exam

Questions 11–15

11application · medium
A CI/CD pipeline for a Go application fails during the build stage. The log shows: 'go: github.com/foo/bar@v1.2.3: read tcp 192.168.1.1:443: i/o timeout'. The go.mod file lists the dependency. The build runs on a self-hosted runner. What is the most likely cause of this failure?
Select an answer first
12application · medium
A CI/CD pipeline fails, and the log shows an error in the deployment stage: 'Error: The process '/usr/bin/docker' failed with exit code 1'. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?
Select an answer first
13application · medium
A CI/CD pipeline fails, and the log shows an error in the deployment stage: 'Error: Unable to connect to the server at https://api.example.com:443'. The application was working previously. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?
Select an answer first
14expert · hard
A CI/CD pipeline for a Java application fails during the build stage. The log shows a dependency resolution error for a library that is hosted on a private Maven repository. The repository requires authentication. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?
Select an answer first
15application · medium
A CI/CD pipeline for a Java application fails during the test stage. The test report shows that a test for the user service failed. The test was passing in the previous build. The pipeline runs tests in a Docker container with a clean environment. The test uses a mock database. What is the most likely cause of this failure?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 350-901

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “350-901” is a trademark of its owner, used for identification only.

Diagnose a CI/CD Pipeline Failure (such as Missing Dependency, Incompatible Versions of Components, and Failed Tests) 350-901 Practice Questions (Page 3)

Questions 11–15

A CI/CD pipeline for a Go application fails during the build stage. The log shows: 'go: github.com/foo/bar@v1.2.3: read tcp 192.168.1.1:443: i/o timeout'. The go.mod file lists the dependency. The build runs on a self-hosted runner. What is the most likely cause of this failure?

A CI/CD pipeline fails, and the log shows an error in the deployment stage: 'Error: The process '/usr/bin/docker' failed with exit code 1'. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?

A CI/CD pipeline fails, and the log shows an error in the deployment stage: 'Error: Unable to connect to the server at https://api.example.com:443'. The application was working previously. The pipeline runs on a self-hosted runner. What is the most likely cause of this failure?

Keep studying — 4.0 Application Deployment and Security