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.

Practice

1. What is the primary purpose of Azure Artifacts in a development project?

easy

A. To monitor application performance

B. To deploy virtual machines automatically

C. To manage user identities and access

D. To store and share code packages securely

Solution

1. Step 1: Understand Azure Artifacts role

   Azure Artifacts is designed to store and share packages like libraries or tools used in development.

2. Step 2: Compare with other Azure services

   Other options relate to different Azure services: virtual machines, monitoring, and identity management.

3. Final Answer:

   To store and share code packages securely -> Option D

4. Quick Check:

   Azure Artifacts = package storage [OK]

Hint: Remember: Artifacts = packages storage and sharing [OK]

Common Mistakes:

• Confusing Azure Artifacts with Azure Monitor
• Thinking it manages virtual machines
• Mixing it up with Azure Active Directory

2. Which of the following is the correct way to configure a package manager to use an Azure Artifacts feed?

easy

A. Create a virtual machine in Azure

B. Add the feed URL to the package manager's configuration file

C. Enable Azure Monitor alerts

D. Set up Azure Active Directory users

Solution

1. Step 1: Identify configuration for package managers

   Package managers like npm or NuGet require the feed URL in their config to publish or consume packages.

2. Step 2: Eliminate unrelated options

   Creating VMs, enabling alerts, or setting up users are unrelated to package manager configuration.

3. Final Answer:

   Add the feed URL to the package manager's configuration file -> Option B

4. Quick Check:

   Feed URL in config = correct setup [OK]

Hint: Configure package manager with feed URL in config file [OK]

Common Mistakes:

• Trying to configure unrelated Azure services
• Forgetting to add the feed URL
• Confusing user setup with package feed setup

3. Given this snippet configuring npm to use Azure Artifacts feed:

npm set registry https://pkgs.dev.azure.com/contoso/_packaging/feed/npm/registry/

What will happen when you run npm install after this?

medium

A. npm will fetch packages from the Azure Artifacts feed

B. npm will fail because the URL is invalid

C. npm will install packages only from the public npm registry

D. npm will delete local packages

Solution

1. Step 1: Understand npm registry setting

   Setting the registry URL tells npm to fetch packages from that feed instead of the default public registry.

2. Step 2: Predict npm install behavior

   After setting, npm install will pull packages from the Azure Artifacts feed URL provided.

3. Final Answer:

   npm will fetch packages from the Azure Artifacts feed -> Option A

4. Quick Check:

   npm registry set = fetch from feed [OK]

Hint: npm registry URL points to Azure feed for installs [OK]

Common Mistakes:

• Assuming npm uses default registry ignoring config
• Thinking URL is invalid without checking format
• Confusing install with delete commands

4. You configured your NuGet client to use an Azure Artifacts feed but get authentication errors when restoring packages. What is the most likely cause?

medium

A. You have no internet connection

B. The feed URL is missing from NuGet.config

C. You did not authenticate with Azure DevOps before restoring

D. Your local packages folder is full

Solution

1. Step 1: Understand authentication requirement

   Azure Artifacts feeds require authentication to access private packages.

2. Step 2: Identify cause of authentication errors

   If you get authentication errors, it means you likely did not sign in or provide credentials to Azure DevOps.

3. Final Answer:

   You did not authenticate with Azure DevOps before restoring -> Option C

4. Quick Check:

   Authentication missing = errors [OK]

Hint: Always authenticate to Azure DevOps before package restore [OK]

Common Mistakes:

• Ignoring authentication step
• Assuming URL missing causes auth errors
• Blaming internet or disk space without checking auth

5. You want to share a private package with your team using Azure Artifacts. Which steps should you take to ensure only your team can access it?

hard

A. Create a private feed, add team members with permissions, publish package to feed

B. Publish package to public npm registry, share URL with team

C. Upload package to a public GitHub repo

D. Email the package files to team members

Solution

1. Step 1: Create a private feed in Azure Artifacts

   This feed restricts package access to authorized users only.

2. Step 2: Add team members with proper permissions

   Granting permissions ensures only your team can access the feed and packages.

3. Step 3: Publish the package to the private feed

   Publishing here keeps the package secure and accessible only to your team.

4. Final Answer:

   Create a private feed, add team members with permissions, publish package to feed -> Option A

5. Quick Check:

   Private feed + permissions = secure sharing [OK]

Hint: Use private feed and permissions to control package access [OK]

Common Mistakes:

• Publishing to public registries for private packages
• Sharing packages by email or public repos
• Not setting permissions on the feed