You have an Azure subscription that contains the resources shown in the following table.
Project1 produces 9pm packages that are published to Feed1. Feed1 is consumed by multiple projects.
You need to ensure that only tested packages are available for consumption. The solution must minimize development effort.
What should you do?
A . Create a feed view named @default. After the 9pm packages test successfully, configure a release pipeline that tags the packages as release.
B. Create a feed view named @release and set @release as the default view. After the 9pm packages test successfully, configure a release pipeline that tags the packages as release.
C. Create a feed view named @release and set @release as the default view After the 9pm packages test successfully, configure a release pipeline that promotes a package to the @release view.
D. Create a feed view named @default. After the 9pm packages test successfully, configure a release pipeline that promotes a package to the @default view.
Answer: C
Explanation:
By creating a feed view named "release" and setting it as the default view, packages that are published to the feed will not be immediately available for consumption. After the 9pm packages are tested successfully, you can configure a release pipeline that promotes a package to the @release view. This ensures that only tested packages are available for consumption and minimizes development effort as it doesn’t require any additional steps to be taken by the consumer of the feed.
Reference: Azure DevOps Docs: Create a feed and views https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/create-feed?view=azure-devops
Azure DevOps Docs: Promote a package https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/promote-package?view=azure-devops
Latest AZ-400 Dumps Valid Version with 289 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund