A NuGet package is published to an "Azure Artifacts" feed that has separate views named Local, Prerelease, and Release. After the package passes integration testing, the team wants downstream consumers configured to the Release view to start resolving that exact build without rebuilding or re-uploading it. Which action achieves this?
- ARebuild the package with the same version number and push it again while targeting the Release view directly, so the binary lands where Release consumers resolve it.
- BPromote the existing package version to the Release view, so consumers pointed at that view resolve the already-published build with no rebuild or re-upload. Correct
- CRaise the package version by one patch segment and republish it, so the higher number naturally supersedes the tested build for Release consumers.
- DDelete the package from the Prerelease view and re-upload the same file into the Release view, so only Release consumers can then resolve the build.
Why A is wrong: Rebuilding and re-pushing the same version duplicates work the scenario rules out and risks an immutability conflict, since a published version cannot simply be overwritten in the feed.
Why B is correct: Feed views expose a slice of immutable published versions, and promoting a version into the Release view makes Release consumers resolve that exact tested build without any rebuild or re-upload.
Why C is wrong: Bumping the version produces a different, untested build rather than promoting the exact build that passed integration testing, so it changes what consumers receive instead of promoting the validated artifact.
Why D is wrong: Deleting and re-uploading is destructive, loses history, and is exactly the re-upload the scenario forbids, so it is the wrong mechanism even though it ends with the build in Release.