When proxying a private upstream MyGet feed into your MyGet feed while using GitHub, which two advantages can this proxying provide? (Select two.)

Proxying a private upstream MyGet feed offers two key advantages. First, it provides automatic authentication. When you configure a proxy, your MyGet feed handles the authentication to the private upstream feed on your behalf. This means individual developers or build agents don't need separate credentials for the upstream feed, simplifying access and security management. Second, it minimizes the impact on your storage quota. When a package is requested through the proxy, it's cached in your MyGet feed. Subsequent requests for the same package are served from your cache, reducing the number of times the package needs to be downloaded from the upstream source. This conserves bandwidth and can help manage storage if the upstream feed has usage limits. Minimizing the impact of upstream source availability issues is incorrect because if the upstream source is unavailable, the proxy will eventually fail to retrieve new packages, though cached packages might still be available. Minimizing latency when accessing the package is also incorrect; while caching can reduce latency for subsequent requests, the initial request still incurs the latency of fetching from the upstream source.