AZ400-Q: Upstream sources in Azure Artifacts
Q: A team wants developers to consume both private NuGet packages (published to their own feed) and public packages from nuget.org through a single feed, without manually adding nuget.org as a separate source. Which Azure Artifacts feature enables this?
- A) Upstream sources ✓
- B) Package views
- C) Feed retention policies
- D) Semantic versioning
Answer: A. An upstream source (e.g., nuget.org, npmjs, PyPI) is connected to your feed so that packages requested but not found locally are automatically pulled/cached from the upstream registry — consumers use one feed for private + public packages. Views manage promotion/release visibility; retention and semantic versioning manage lifecycle/versioning, not registry aggregation.
Why it helps
Upstream sources and feed configuration are core “dependency management with Azure Artifacts” AZ-400 objectives.
Related
azure-artifacts · package-feed · upstream-sources · semantic-versioning