AZ-400 Question 98
Single answerYou work for a software company that hosts all code in GitHub and uses GitHub Actions for CI/CD. Your teams develop .NET microservices that require private Docker images and also publish internal npm packages for front-end projects. They want one system that reliably stores and shares both Docker images and npm packages, using GitHub credentials for access control. Which solution best meets these requirements?
- A
Use GitHub Packages registry to store both private Docker images and npm packages
- B
Use Azure Artifacts for npm packages and Azure Container Registry for Docker images
- C
Use public npm for front-end packages and GitHub Packages registry for Docker images
- D
Use an on-premises repository solution for both Docker images and npm packages
Show answer and explanation
Correct answer: A
Explanation
GitHub Packages registry can host both Docker images and various package formats like npm and NuGet, making it suitable for teams already using GitHub for code and CI/CD. It leverages GitHub� authentication, ensuring a streamlined experience. According to GitHub� documentation (https://docs.github.com/en/packages), combining GitHub Actions with GitHub Packages provides consistent pipelines for building, testing, and publishing artifacts in one place.
- A. Correct.
Option 1 is correct. GitHub Packages registry supports multiple package types, including Docker images and npm packages. Because your organization already uses GitHub for version control and GitHub Actions for CI/CD, relying on GitHub Packages registry allows a unified authentication model (GitHub credentials) and a seamless development workflow.
- B. Incorrect.
Option 2 is incorrect. Azure Artifacts can store npm packages, and Azure Container Registry can store container images, but this splits your solutions between two services. It may also elevate complexity and does not leverage a single GitHub credential system for both package types.
- C. Incorrect.
Option 3 is incorrect. Storing internal npm packages in the public npm registry would expose them externally or require complicated private-scoped configurations. This also contradicts the requirement for a unified environment governed by GitHub credentials.
- D. Incorrect.
Option 4 is incorrect. An on-premises repository adds overhead and complexity. It does not integrate easily with GitHub Actions or GitHub credentials, and there is no indication that an on-prem solution is preferred or required.