In Azure DevOps, what are artifacts?

Artifacts in Azure DevOps refer specifically to the outputs generated during the build process, which typically include binaries, libraries, and other files that are produced as a result of building the code. These artifacts are essential for the deployment and release processes, as they represent the tangible results of the development effort.

In a typical continuous integration/continuous deployment (CI/CD) pipeline, artifacts are archived after a successful build and can then be used in release pipelines to deploy to various environments. This allows teams to maintain consistency by deploying the same build outputs across different environments, thereby reducing the risk of errors that can arise from differences in the code or configurations.

The other options, while they cover important aspects of software development, do not accurately define artifacts within the context of Azure DevOps. Tools for creating documentation focus on project documentation but do not pertain to the outputs of building software. Methods for tracking application performance relate to monitoring and analytics rather than the results of the build process. Standards for coding practices provide guidelines for writing code but are not outputs generated by the build. Thus, artifacts in Azure DevOps clearly align with option B as they embody the actual deliverables produced through the build operations.