You use GitHub for source control.
You are evaluating whether to use proxying to add a private upstream MyGet package feed to your MyGet feed.
What are two possible advantages of this approach? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Proxying an upstream MyGet package feed can minimize the impact of upstream source availability issues because it allows caching of packages. This means that even if the upstream source is temporarily unavailable, the packages can still be accessed from the cache, ensuring continuous availability to your development workflow. Additionally, proxying provides automatic authentication by handling the authentication process with the upstream source, simplifying access and credentials management for users. These two advantages enhance both reliability and ease of use for the MyGet feed.
Anwers is correct, see link from Hector1812: Benefits: (C) Cupstream packages do not count against your MyGet storage quota (D) authentication against upstream, private MyGet feeds happens automatically
https://docs.myget.org/docs/reference/upstream-sources
Proxy packages from an upstream source You can configure an upstream source to proxy upstream packages through your MyGet feed to your feed consumers. Proxying makes it easy to have a single MyGet feed aggregate packages from multiple sources. Package consumers need only to configure a single MyGet feed, and all packages available on upstream, proxied package sources will become available to them. Benefits: upstream packages do not count against your MyGet storage quota authentication against upstream, private MyGet feeds happens automatically (see Upstream Source Credentials)
C, D then
It should be C, D
Resilience against Upstream Outages (A): When proxying, your MyGet feed acts as a cache for the upstream feed. If the upstream feed becomes unavailable, your developers can still access packages from the cached copies within your MyGet feed, minimizing disruptions to their workflow. Simplified Authentication (C): MyGet handles authentication against the upstream private feed automatically during the proxying process. This eliminates the need for developers to configure individual credentials in their tools or manage complex authentication mechanisms.
From https://docs.myget.org/docs/reference/upstream-sources Benefits: upstream packages do not count against your MyGet storage quota authentication against upstream, private MyGet feeds happens automatically
Benefits: upstream packages do not count against your MyGet storage quota authentication against upstream, private MyGet feeds happens automatically https://docs.myget.org/docs/reference/upstream-sources#Proxy_packages_from_an_upstream_source
a. minimizes the impact of upstream source availability issues C. provides automatic authentication A&C correct answers
Proof? Do you have a link that supports the provided answer? Or at least give an explanation yourself.
https://docs.myget.org/docs/reference/upstream-sources
Correct AC
A doesn't make sense as proxying something that's unavailable still means that it is unavailable.
https://docs.myget.org/docs/reference/upstream-sources
Response from ChatGPT - A. Minimizes the impact of upstream source availability issues. C. Provides automatic authentication. Explanation: A. Proxying a private upstream MyGet package feed to your MyGet feed helps minimize the impact of upstream source availability issues. If the upstream source experiences downtime or availability issues, your local proxy can still serve packages from its cache, ensuring continuous availability to your team. C. Proxying provides automatic authentication. When you set up a proxy, it handles authentication with the upstream source on your behalf. This means you don't have to manage authentication separately for every user or system accessing packages from the upstream source, simplifying the authentication process.
I choose A,D Proxying is a way of adding packages from an upstream source to your MyGet feed without copying the package itself. Two possible advantages of this approach are: A. minimizes the impact of upstream source availability issues. If the upstream source is down or unreachable, you can still access the package metadata from your MyGet feed and download the package from a cached location. D. minimizes the impact on your storage quota. Since the package is not stored on your MyGet feed, you do not consume any storage space for it. This can help you save costs and manage your storage quota more efficiently.