Maintain Pipelines AZ-400 Practice Questions (Page 7)

Questions 31–35

1. 31foundation · easy

   What is the primary trade-off when increasing the concurrency of a pipeline?

   • AReduced cost but increased pipeline duration
   • BIncreased storage but reduced compute
   • CReduced pipeline duration but increased cost
   • DImproved reliability but reduced performance
   Reveal Solution Discussion Select an answer first
2. 32application · medium

   Your organization's security team requires that build artifacts be retained for 90 days for audit purposes, but the compliance team wants to minimize storage costs. The pipeline currently retains all artifacts indefinitely. You need to implement a retention strategy that meets the audit requirement and controls storage costs. What should you do?

   • ASet the pipeline's artifact retention policy to 90 days and apply it to all runs.
   • BDisable artifact publishing to avoid storage costs.
   • CRetain artifacts for 30 days and export them to an external archive for 90 days.
   • DKeep the indefinite retention policy and rely on manual cleanup by the operations team.
   Reveal Solution Discussion Select an answer first
4. 33foundation · easy

   In a YAML pipeline, which keyword is used to specify the number of days to retain pipeline runs?

   • Acondition
   • Btimeout
   • Cretention
   • Dpool
   Reveal Solution Discussion Select an answer first
5. 34application · medium

   Your team notices that the CI pipeline often fails on the same test, but the test passes when run locally. The team wants to identify whether the test is flaky and improve pipeline reliability. What should you do first?

   • AReview the pipeline's test results over the last 30 days to see the failure rate of that test.
   • BDelete the test from the test suite to stop the pipeline from failing.
   • CIncrease the pipeline timeout to give the test more time to pass.
   • DRun the test on a different agent to see if it passes.
   Reveal Solution Discussion Select an answer first
6. 35expert · hard

   Your team has a classic release pipeline with multiple stages, manual approvals, and a complex set of variables that differ per environment. The team wants to migrate to YAML to improve maintainability and take advantage of templates. However, the team also needs to keep the manual approval process and ensure that the migration does not break the release process. What is the best approach?

   • AKeep the classic pipeline and create a new YAML pipeline for future releases only.
   • BCreate a YAML pipeline with stages that mirror the classic pipeline, using environment approvals for each stage.
   • CUse a YAML pipeline with a single stage and use a script to prompt for approvals.
   • DConvert the classic pipeline to a single YAML job that deploys to all environments without approvals.
   Reveal Solution Discussion Select an answer first