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

Questions 26–28

1. 26foundation · easy

   A CI/CD pipeline fails, and the developer needs to determine which stage caused the failure. Which artifact should the developer examine first?

   • AThe pipeline logs, which show the output of each stage.
   • BThe application's runtime logs from the production environment.
   • CThe project's documentation.
   • DThe source code repository's commit history.
   Reveal Solution Discussion Select an answer first
2. 27expert · hard

   A CI/CD pipeline for a microservices application fails during the integration test stage. The test logs show a connection refused error when one service tries to call another. The services are deployed in a Kubernetes cluster. The pipeline runs tests in a separate namespace. The test was passing in the previous build. What is the most likely cause of this failure?

   • AThe services are using incompatible versions of a shared library.
   • BThe service-to-service communication is broken because the services are not in the same Kubernetes namespace.
   • CThe integration test is failing because the database is not seeded.
   • DThe test is flaky due to timing issues.
   Reveal Solution Discussion Select an answer first
3. 28foundation · easy

   In a CI/CD pipeline, which stage is most likely to catch a syntax error in the application source code?

   • ARelease stage
   • BMonitoring stage
   • CBuild stage
   • DDeploy stage
   Reveal Solution Discussion Select an answer first