Design and Implement a Package Management Strategy AZ-400 Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A company uses GitHub for source control and Azure DevOps for CI/CD. They need to publish packages that are consumed by both GitHub Actions and Azure Pipelines. They also want to enforce that only approved package versions are used across both platforms. What should you recommend?

   • AUse two separate feeds: one for GitHub and one for Azure DevOps.
   • BUse GitHub Packages as the single feed and configure Azure Pipelines to authenticate with a GitHub token.
   • CUse Azure Artifacts as the single feed and configure GitHub Actions to authenticate with an Azure Artifacts token.
   • DUse a public package registry for all packages.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   Your team publishes a NuGet package to Azure Artifacts. You want the release pipeline to consume only packages that have passed integration testing, while developers should be able to consume all published versions. You have already created a 'release' view. What should you do in the release pipeline?

   • APromote the package version to the 'release' view after tests pass and configure the release pipeline to use the view
   • BCreate a new feed for tested packages and copy them after testing
   • CDelete packages that fail testing from the feed
   • DConfigure the release pipeline to use the default view and filter by version range
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   Your organization has multiple Azure Artifacts feeds for different teams. You need to reduce duplication of packages across feeds while maintaining isolation for teams that require it. You also need to ensure that a critical security patch to a shared package is immediately available to all consumers. What should you do?

   • AConfigure upstream sources between feeds so that one feed can consume packages from another, and use views to control promotion of the security patch.
   • BCreate a single feed for all teams and remove team-specific feeds.
   • CUse GitHub Packages as a central feed and configure all Azure Artifacts feeds to use it as an upstream source.
   • DManually copy the patched package to each feed.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   Your organization has a library that is consumed by multiple teams. You are planning a major release that introduces breaking changes. You also need to continue shipping bug fixes for the previous major version for existing consumers. You want to minimize the number of feeds and keep the release pipeline simple. What versioning and feed strategy should you adopt?

   • ACreate a separate feed for the new major version and keep the old feed for the previous version
   • BDelete the old major version from the feed after publishing the new one
   • CPublish the new major version under the same feed and use SemVer to differentiate; maintain the old version in the same feed
   • DUse CalVer for the new major version and SemVer for the old version
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A team uses Azure Pipelines to produce a deployable artifact. They want to ensure that the artifact version is unique and traceable to the pipeline run, and they also want to include a human-readable version number. What should they use as the artifact version?

   • AThe source commit ID alone (e.g., abc123)
   • BThe date and time of the build (e.g., 2024-03-15T10:30:00)
   • CThe pipeline run ID (e.g., 20240315.1)
   • DA combination of the build ID and the source commit ID (e.g., 20240315.1-abc123)
   Reveal Solution Discussion Select an answer first