Azure Artifacts for packages - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Azure Artifacts feed using Azure CLI.

Azure

az artifacts feed create --name [1] --project MyProject

Drag options to blanks, or click blank then click option'

AMyPackage

BMyProject

CMyRepo

DMyFeed

Attempts:

3 left

💡 Hint

Common Mistakes

Using the project name instead of the feed name.

Confusing feed name with package or repository names.

The --name parameter specifies the name of the new feed. Here, MyFeed is the correct feed name.

2fill in blank

medium

Complete the command to list all packages in an Azure Artifacts feed.

Azure

az artifacts package list --feed [1] --project MyProject

Drag options to blanks, or click blank then click option'

AMyFeed

BMyRepo

CMyPackage

DMyProject

Attempts:

3 left

💡 Hint

Common Mistakes

Using project name instead of feed name.

Using package name instead of feed name.

The --feed parameter requires the feed name to list packages inside it. MyFeed is the correct feed name.

3fill in blank

hard

Fix the error in the command to publish a package to Azure Artifacts.

Azure

az artifacts universal publish --feed [1] --name MyPackage --version 1.0.0 --path ./package

Drag options to blanks, or click blank then click option'

AMyFeed

BMyPackage

CMyProject

DMyRepo

Attempts:

3 left

💡 Hint

Common Mistakes

Using package name instead of feed name.

Using project name instead of feed name.

The --feed parameter must be the feed name where the package will be published. MyFeed is correct.

4fill in blank

hard

Fill both blanks to configure npm to use an Azure Artifacts feed.

Azure

npm set registry https://pkgs.dev.azure.com/[1]/_packaging/[2]/npm/registry/

Drag options to blanks, or click blank then click option'

AMyOrganization

BMyProject

CMyFeed

DMyPackage

Attempts:

3 left

💡 Hint

Common Mistakes

Using project name instead of organization.

Using package name instead of feed.

The URL requires the organization name and the feed name. MyOrganization is the organization, and MyFeed is the feed.

5fill in blank

hard

Fill all three blanks to authenticate npm with Azure Artifacts using a personal access token.

Azure

echo //pkgs.dev.azure.com/[1]/_packaging/[2]/npm/registry/:_authToken=[3] >> ~/.npmrc

Drag options to blanks, or click blank then click option'

AMyOrganization

BMyFeed

CPERSONAL_ACCESS_TOKEN

DMyProject

Attempts:

3 left

💡 Hint

Common Mistakes

Using project name instead of organization.

Using package name instead of feed.

Not using the actual token placeholder.

The authentication line needs the organization name, feed name, and the personal access token to allow npm to access the feed.

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