AZ-400 Question 96
Select 2You are designing a package management strategy in Azure DevOps for multiple development teams. Each team has unique dependencies, but they also share some libraries and need to consume external packages from publicly available sources. Additionally, your organization wants to ensure package version compliance and manage storage costs by removing older package versions that are no longer needed. Which approaches should you implement?
- A
Create a single feed for all teams and disable upstream sources to restrict external dependencies.
- B
Set up separate Azure Artifacts feeds for each team and enable upstream sources to fetch external packages when needed.
- C
Use personal, local developer-defined feeds on each workstation without any central repository.
- D
Implement version retention policies and naming conventions in Azure Artifacts for better lifecycle management.
Show answer and explanation
Correct answers: B, D
Explanation
When designing a package management strategy with Azure DevOps, it is best practice to store packages in centrally managed feeds and configure upstream sources to fetch external dependencies. Each team can have its own feed to manage version control and dependencies effectively. Additionally, implementing retention policies and versioning/naming conventions ensures that outdated or unwanted package versions are cleaned up, improving compliance and reducing storage overhead. For more details, refer to the Microsoft Azure DevOps Artifacts documentation: https://learn.microsoft.com/azure/devops/artifacts.
- A. Incorrect.
Option A is incorrect. Creating one feed and disabling upstream sources restricts the teams� ability to consume necessary external dependencies. This would make package sharing difficult and limit access to external libraries without manual workarounds.
- B. Correct.
Option B is correct. Having separate feeds per team allows for cleaner isolation of dependencies, and enabling upstream sources ensures the teams can directly consume external packages without duplicating them in every feed. This is a recommended practice for managing shared libraries while still providing team-level autonomy.
- C. Incorrect.
Option C is incorrect. Using only personal, local feeds with no central repository prevents broader collaboration and consistency. It also increases the chances of version mismatches, as developers would have to manually synchronize packages across machines.
- D. Correct.
Option D is correct. Version retention policies and proper naming conventions in Azure Artifacts help enforce compliance, reduce storage consumption, and maintain a clearer lifecycle for each package version. This practice supports best practices in enterprise environments, where uncontrolled growth of package versions can lead to significant maintenance challenges.