Exam AZ-400 topic 5 question 45 discussion

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

https://docs.myget.org/docs/reference/upstream-sources#Proxy_packages_from_an_upstream_source Answers are C & D Proxy packages from an upstream source. Benefits: upstream packages do not count against your MyGet storage quota. authentication against upstream, private MyGet feeds happens automatically. As A & B are for Mirror packages from an upstream source. This configuration is similar to package proxying, but takes it one step further. Benefits: No additional latency (except for the first hit that triggers the package mirroring). Protected against upstream source availability issues. Protected against upstream package removal. authentication against upstream, private MyGet feeds happens automatically.

Answers are CD Some of you guys are confusing the proxying with mirroring. if it was mirroring then it minimizes the impact of upstream source availability issues

Minimizes the impact of upstream source availability issues Explanation: Proxying ensures that packages from the upstream feed are cached in the MyGet feed. If the upstream source becomes unavailable, the cached packages remain accessible. This reduces downtime and dependency issues for projects relying on those packages. Why it matters: Ensures consistent access to dependencies even if the original source is temporarily unavailable. 2. Minimizes latency when accessing the package Explanation: By caching packages locally in the MyGet feed, proxying reduces the need to repeatedly fetch them from the upstream feed, which might be slower due to network distance or other factors. Why it matters: Improves build times and developer productivity by reducing delays in accessing dependencies.

https://docs.myget.org/docs/reference/upstream-sources

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.

Correct AC

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

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.

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

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.

It should be C, D

a. minimizes the impact of upstream source availability issues C. provides automatic authentication A&C correct answers