Exam AZ-400 topic 1 question 20 discussion

correct Answer is B

Based on the link https://docs.microsoft.com/en-us/azure/devops/artifacts/concepts/views?view=azure-devops, use of feed - "is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet your quality bar." for Upsteam sources - "In order for other Azure Artifacts feeds to use your feed as an upstream source, you must set your feed's view visibility to members of your organization, or members of your Azure Active Directory, depending on your scenario." I think, since it deployment phase/stage, the view should be start first after that only upstream sources to control who I would like to share. I will go with - B.

Feed views enable developers to share a subset of package-versions with their consumers. A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet a certain quality bar. Feed views and upstream sources are designed to work together to provide an enterprise-level solution to share and consume packages. In order for other Azure Artifacts feeds to use your feed as an upstream source, you must set your feed's visibility to members of your organization, or members of your Azure Active Directory, depending on your scenario. If you choose the latter, all people in your organization will be able to access your feed, and all feeds in your organization and other organizations associated with the same Azure Active Directory tenant will be able to upstream to your feed.

Feed views enable developers to share a subset of package-versions with their consumers. A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet a certain quality bar. docs.microsoft.com/en-us/azure/devops/artifacts/concepts/views?view=azure-devops

What are feed views? Feed views enable developers to share a subset of package-versions with their consumers. A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet a certain quality bar. From https://docs.microsoft.com/en-us/azure/devops/artifacts/concepts/views?view=azure-devops Answer is B

B. You should make use of views. B. You should make use of views: Views in Azure Artifacts help you manage and consume packages in your feed. By default, each feed in Azure Artifacts has three views: @local, @Prerelease, and @Release. You can promote a package version from one view to another to control its visibility and availability. This can help you to restrict the release of packages that are still in development. In Azure Artifacts, Views are a feature designed to help manage the release and visibility of packages in your feed, making them the most suitable choice for this scenario.

B. You should make use of views. To restrict the release of packages that are in development, you should use views in Azure Artifacts. Views are a way to manage the visibility of packages in a feed. You can create views that are specific to certain groups or teams in your organization, and control which packages are visible to those groups. By creating a view for packages that are ready for release, you can restrict the visibility of packages that are still in development. Only the packages in the view will be available for use, while the packages that are still in development will remain hidden. Static code analysis and dynamic code analysis are techniques for analyzing code to find errors or vulnerabilities, and are not directly related to managing package visibility in Azure Artifacts. Upstream sources are used to pull packages from external sources into your feed, and are not related to managing package visibility within your feed. Therefore, options A, C, and D are not relevant for this scenario.

correct Answer is B Views in Azure Artifacts allow you to control access to specific packages within a feed. You can create views to include or exclude packages based on specific criteria, such as package version, tags, or other metadata. By configuring views, you can restrict the release of packages that are still in development to only authorized users or groups.

B is the answer. https://learn.microsoft.com/en-us/azure/devops/artifacts/concepts/views?view=azure-devops Feed views enable developers to share a subset of package-versions with their consumers. A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet a certain quality bar.

B. You should make use of views. Views in Azure Artifacts allow you to control the visibility and access to specific packages within a feed. By creating views, you can restrict the release of packages that are still in development and control who has access to them. You can configure views to include or exclude specific packages based on criteria such as version ranges, tags, or other metadata. This allows you to define separate views for different stages of development, such as a "Development" view for packages still in progress and a "Release" view for packages that have been validated and are ready for deployment. By using views, you can effectively restrict the release of packages that are in development while using a single feed in Azure Artifacts. This helps maintain control over the availability and visibility of packages to different teams and stakeholders. Options A, C, and D are not the most appropriate actions

must be D

Views allow you to create a filtered version of a feed, showing only specific packages or versions that meet your criteria. You can create a view that excludes packages marked as "development" from being accessed by users, even though they exist in the original feed.

I think views

https://learn.microsoft.com/en-us/azure/devops/artifacts/concepts/views?view=azure-devops -> A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development ...

Answer is B. Explanation: In Azure Artifacts, views allow you to control access to packages within a feed. By creating views, you can define specific rules and filters to restrict the visibility of packages based on certain criteria. This includes restricting access to packages that are still in development.

BBBBBBBBBBBBBBBBB (B)

Why doesn't someone fix this? It is clearly B.