Continuous Integration Tools DSE Practice Questions (Page 6)

Questions 26–30

1. 26application · medium

   A company is evaluating CI tools for a project that uses a mix of .NET and Python components. They require the CI tool to support both ecosystems, integrate with their existing Azure DevOps boards, and provide built-in security scanning. Which CI tool should they select?

   • ATravis CI
   • BCircleCI
   • CJenkins with custom plugins
   • DAzure Pipelines
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A team uses Jenkins and Bitbucket. They want builds to start automatically only when a developer pushes a commit to the 'develop' branch, not on every branch. What should they configure?

   • AConfigure a Bitbucket hook to call the Jenkins REST API after every push, with no branch filter.
   • BUse the Jenkins 'Build after other projects are built' trigger with a downstream job.
   • CSet Jenkins to poll SCM every minute and let the job run on all branches.
   • DCreate a Bitbucket webhook that triggers the Jenkins job, and set the job's branch specifier to 'develop'.
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   A team's CI pipeline takes 45 minutes to run, and developers often wait a long time to find out if their code compiles. They want to provide faster feedback on basic code quality and compilation errors without waiting for the full pipeline. Which practice should they adopt?

   • AIncrease the number of parallel stages in the pipeline to reduce overall runtime.
   • BMove all tests to a nightly build so that the main pipeline only compiles the code.
   • CRequire developers to run the full pipeline locally before pushing to the repository.
   • DRun a fast 'smoke test' stage that compiles the code and runs a few key tests, and have it execute before the full pipeline.
   Reveal Solution Discussion Select an answer first
5. 29expert · hard

   A team's Jenkins pipeline has a stage that runs a long integration test suite. The pipeline is configured with a global timeout of 30 minutes, but the integration tests sometimes take up to 45 minutes. The team wants to keep the global timeout for other stages but allow this stage more time. What is the best configuration?

   • AAdd a 'timeout' directive inside the specific stage to override the global timeout for that stage.
   • BIncrease the global timeout to 60 minutes.
   • CRemove the timeout from the pipeline entirely.
   • DSplit the integration tests into a separate job with its own timeout.
   Reveal Solution Discussion Select an answer first
6. 30application · medium

   A team uses Azure DevOps and wants a build to start automatically when a pull request is created, but not when changes are pushed to the target branch directly. Which trigger configuration should they use?

   • ACreate a webhook in the repository that triggers the pipeline on any push event.
   • BSet the pipeline to trigger on every push to the target branch.
   • CConfigure a branch policy on the target branch that requires the build to pass, and set the pipeline trigger to 'Pull request validation'.
   • DUse a scheduled trigger that runs the build every hour.
   Reveal Solution Discussion Select an answer first