An engineering group wants its npm restores to keep working during public registry slowdowns, and wants each third-party package fetched from the public registry only once. Which Azure Artifacts feature achieves this?
Show answer and explanation
Answer: D
An upstream source links a feed to an external registry such as npmjs.org. When a client asks for a package the feed does not yet hold, the feed retrieves it from the upstream, stores a copy, and serves it from then on. Subsequent installs come from the internal feed, which reduces dependence on the public service's availability and speeds restores. Promotion between views only moves packages already in the feed. Renaming a feed or pruning old versions does not fetch anything from a public source.
Why the other options are wrong
- A. Promotion between views moves packages that already exist in the feed. It never pulls a package in from an outside registry for the first time.
- B. Feed names do not change how packages are resolved. Renaming a feed has no effect on caching or on where a missing package is retrieved from.
- C. Version retention rules control how many old package versions are kept, not whether third-party packages are fetched from a public source and stored locally.