Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesMedium
A global financial institution uses Azure DevOps for its mission-critical applications. They need to ensure that their release pipelines adhere to strict compliance and auditing requirements. Specifically, they must track every change to a release pipeline definition, including who made the change and when. Additionally, they need the ability to revert a pipeline definition to a previous working state if an unauthorized or faulty change is introduced. Which Azure DevOps feature directly supports these requirements?
- ARelease pipeline history
- BRetention policies
- CDeployment conditions
- DPipeline permissions
Show answer & explanationAnswer & explanation
Correct answer: A. Release pipeline history
Release pipeline history in Azure DevOps provides a full audit trail of all changes made to a release pipeline definition, including the user, timestamp, and the specific changes. It also allows reverting to previous versions, directly addressing the compliance and revert capability requirements.
Why the other options are wrong
- B. Retention policies control how long release runs and associated artifacts are kept, not changes to the pipeline definition.
- C. Deployment conditions define when a stage should run, not track changes to the pipeline definition.
- D. Pipeline permissions control who can modify or run pipelines but do not provide a detailed audit trail of changes or a revert mechanism for the definition itself.
Release Pipeline History
The Release Pipeline History in Azure DevOps provides an audit trail of all modifications made to a release pipeline's definition, including details on the change, the user who made it, and the timestamp. It also enables reverting to prior versions.
- Logs all definition changes (who, what, when).
- Supports compliance and auditing requirements.
- Allows reverting to any previous version of the pipeline definition.
Memory trick: History remembers all, and allows going back.