Azure Artifacts for packages - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Azure Artifacts handle package versioning?

Azure Artifacts allows teams to manage package versions. Which statement best describes how Azure Artifacts handles package versioning?

A Azure Artifacts enforces unique version numbers per package and prevents overwriting existing versions in a feed.

B Azure Artifacts allows multiple packages with the same version number to coexist in the same feed without restrictions.

C Azure Artifacts automatically overwrites existing package versions with the same version number when a new package is published.

D Azure Artifacts deletes older package versions automatically when a new version is published.

💡 Hint

Think about how package versioning helps avoid confusion and conflicts in software development.

Azure Artifacts requires each package version to be unique within a feed. It prevents overwriting existing versions to ensure consistency and traceability.

❓ Architecture

intermediate

Choosing the right feed type in Azure Artifacts

You want to share packages internally within your organization but also allow public access to some packages. Which Azure Artifacts feed type setup supports this scenario?

A Create a single public feed and share all packages there, including internal ones.

B Create one private feed for internal packages and a separate public feed for packages meant for public access.

C Use only private feeds and share access tokens with external users for public packages.

D Create multiple private feeds and manually copy packages to a public GitHub repository.

💡 Hint

Consider separation of access and security for internal vs public packages.

Using separate feeds allows you to control access properly: private feeds keep internal packages secure, while public feeds allow open access.

❓ security

advanced

Securing access to Azure Artifacts feeds

Which method provides the most secure way to restrict access to an Azure Artifacts feed to only specific users or groups?

A Disable authentication and rely on network firewall rules to restrict access to the feed.

B Use personal access tokens (PATs) shared via email to all users who need access.

C Share the feed URL publicly but require users to authenticate with any Microsoft account.

D Use feed-level permissions to grant read and contribute access only to selected Azure Active Directory groups.

💡 Hint

Think about managing permissions centrally and securely.

Feed-level permissions integrated with Azure Active Directory groups provide fine-grained, secure access control.

❓ Configuration

advanced

Configuring upstream sources in Azure Artifacts

You want your Azure Artifacts feed to automatically fetch packages from public registries like npmjs.org when they are not found in your feed. How do you configure this behavior?

A Enable upstream sources in the feed settings and add npmjs.org as an upstream source.

B Manually download packages from npmjs.org and upload them to your feed.

C Configure a build pipeline to proxy requests to npmjs.org on demand.

D Use a separate feed for public packages and merge it with your private feed.

💡 Hint

Look for a feature that allows automatic fetching from external registries.

Upstream sources let your feed automatically retrieve packages from public registries when they are missing locally, simplifying dependency management.

✅ Best Practice

expert

Optimizing package retention policies in Azure Artifacts

Your organization wants to keep the feed size manageable by automatically deleting old package versions but must retain versions used in active releases. Which approach best achieves this?

A Disable retention policies and rely on storage quotas to limit feed size.

B Manually delete old package versions weekly based on developer feedback.

C Set retention policies to delete unreferenced package versions older than a specified age, preserving those linked to active releases.

D Configure retention policies to delete all package versions older than 30 days regardless of usage.

💡 Hint

Consider how to balance cleanup with preserving important versions.

Retention policies that delete only unreferenced old versions keep the feed clean without breaking active builds or releases.