AZ-400 Question 102
Select 2Your organization manages a private npm feed in Azure Artifacts. You also want to incorporate the public npm registry as an upstream source so developers can access external packages without manually connecting to npmjs.com. However, you need to separate prerelease versions from stable releases and ensure that only stable versions from the public registry are used in production. Which two actions should you take to set up your feed and views correctly?
- A
Add the public npm registry as an upstream source, then create a 'PreRelease' and 'Release' view in your Azure Artifacts feed.
- B
Configure the feed to only store stable versions from the public registry by filtering out prerelease tagged versions, then associate that upstream with a 'Release' view.
- C
Enable 'Inherit feed permissions' in the public view to automatically hide prerelease packages from downstream consumers.
- D
Create an additional feed specifically for prerelease packages, disallowing any upstream connections to the public registry.
Show answer and explanation
Correct answers: A, B
Explanation
Azure Artifacts supports adding external package sources (e.g., npmjs.com) as upstreams and using views to segment different package versions or states (such as pre-release vs. release). Following official Microsoft documentation (https://learn.microsoft.com/azure/devops/artifacts/) ensures best practices for configuring multiple views and filtering packages so that only stable versions flow into production, while prerelease packages remain in development or testing environments.
- A. Correct.
Correct: By adding the public npm registry as an upstream source, you can seamlessly consume both local and external packages. Creating separate views (e.g., 'PreRelease' and 'Release') allows you to segregate prerelease packages from production-ready versions, matching common best practices in Azure Artifacts.
- B. Correct.
Correct: You can filter out prerelease versions when configuring the feed's upstream source, so only stable releases from npmjs.com are cached. Associating the upstream source with a 'Release' view ensures that only stable versions are displayed in that view, keeping development and production packages organized.
- C. Incorrect.
Incorrect: 'Inherit feed permissions' does not specifically hide or filter prerelease packages. This option manages permission inheritance, not package filtering. Relying on inherited permissions alone will not achieve the requirement of separating prerelease from stable packages.
- D. Incorrect.
Incorrect: Creating an entirely separate feed for prerelease packages without allowing upstream connections to npmjs.com ignores the need to pull external prerelease packages if needed. Additionally, you lose the capability to manage stable and prerelease packages within a single feed structure that uses multiple views.