Interview Q&A

What is a release pipeline and how does it differ from a build pipeline?

Answer:

A build pipeline (CI) compiles, tests, and packages your code — it produces artifacts.

A release pipeline (CD) takes those artifacts and deploys them to different environments

like Dev, QA, or Production.

Example:

• Build Pipeline: Compiles your .NET app and outputs a .zip file.
• Release Pipeline: Takes that .zip and deploys it to Azure App Service.

So, the build pipeline = create, and release pipeline = deliver.

What is a build pipeline in Azure DevOps?

Answer:

A build pipeline in Azure DevOps automates how your code is compiled, tested, and

packaged whenever you make changes.

It’s part of Continuous Integration (CI) — where every code check-in triggers an automatic

build to ensure nothing is broken.

Example:

When a developer pushes code to main, Azure Pipelines automatically compiles your .NET

app, runs unit tests, and generates a build artifact (like a .zip or .dll) ready for

deployment.

What is a project in Azure DevOps and what resources can it include?

Answer:

A project in Azure DevOps is like a container for everything related to a specific application

or product.

It can include:

• Code repositories
• Work items (stories, bugs)
• Pipelines (build/release)
• Test cases
• Artifacts

Example:

You might have a project named “ShoppingCartApp” that includes its code repo, CI/CD

pipeline, and all user stories related to that app.

A project in Azure DevOps is like a container for everything related to a specific application

or product.

It can include:

• Code repositories
• Work items (stories, bugs)
• Pipelines (build/release)
• Test cases
• Artifacts

Example:

You might have a project named “ShoppingCartApp” that includes its code repo, CI/CD

pipeline, and all user stories related to that app.

6⃣ How do you organize repositories and teams in Azure DevOps for large

applications?

For large systems, you can:

• Use multiple repositories (one per microservice or component).
• Create teams inside the project to manage different modules.
• Use Areas and Iterations in Boards to track team-specific work.

Follow:

Example:

An e-commerce platform might have separate repos for PaymentService,

CatalogService, and OrderService. Each has its own team and pipelines but shares

the same Azure DevOps project for visibility.

7⃣ What are service connections in Azure DevOps?

A service connection is a secure link between Azure DevOps and external systems (like

Azure, AWS, GitHub, or Docker Hub).

Example:

If your pipeline needs to deploy code to Azure App Service, you create an Azure Resource

Manager service connection. It stores credentials securely so the pipeline can deploy

automatically.

8⃣ What is the difference between an organization, project, and repository

in Azure DevOps?

• Organization: The top-level container (like a company or department).
• Project: A workspace for a specific product or app.
• Repository: Where your source code lives.

Example:

Organization: ContosoTech

→ Project: MobileApp

→ Repository: ContosoApp-Frontend

9⃣ How do you manage permissions and access control in Azure

DevOps?

Follow:

You manage access using security groups and permissions at different levels

(Organization, Project, Repo, or Pipeline).

Example:

Developers may have Contribute rights on code, testers may have Edit Test Cases, and

managers may have View Only access to dashboards.

You can even integrate with Azure AD to sync user roles automatically.

🔟 How does Azure DevOps integrate with Active Directory or Azure

AD?

Azure DevOps integrates directly with Azure Active Directory for user authentication and

access control.

• You can use your company credentials to log in.
• Groups and roles from Azure AD can be mapped to DevOps permissions.
• SSO (Single Sign-On) makes it easier for teams to manage access securely.

Example:

When a new developer joins your company, you add them to the “Developers” group in

Azure AD — they automatically get access to the right projects in Azure DevOps.

Source Control (Azure Repos / Git)

1⃣ How do you create and manage branches in Azure Repos?

In Azure Repos, you create branches to work on features or fixes without disturbing the

main codebase.

You can create branches in multiple ways:

• From the Azure DevOps portal (Repos → Branches → New Branch).

Follow:

Using Git commands:

git checkout -b feature/add-login

git push origin feature/add-login

Managing branches means keeping them clean — deleting old ones after merges, naming

them properly (like feature/, bugfix/, release/), and ensuring they stay up to date

with main or develop.

Example:

When adding a “Dark Mode” feature, you create a branch called feature/dark-mode,

work there, and merge it back after review.

2⃣ What branching strategies have you used (e.g., Git Flow, trunk-based)?

There’s no one-size-fits-all strategy — it depends on team size and release frequency.

Common ones:

• Git Flow:

Uses main, develop, and feature branches. Ideal for structured release cycles.

Example: A large enterprise team doing monthly releases.

• Trunk-Based Development:

Everyone commits to main frequently with short-lived branches. Faster delivery.

Example: A DevOps team deploying multiple times a day.

• Feature Branching:

Simple approach — create a new branch per feature, merge when ready.

Example:

In my last project, we used Git Flow — developers worked off develop, created

feature/* branches, and merged through pull requests.

3⃣ How do you set up branch policies in Azure Repos?

Follow:

Branch policies ensure quality and control before merging code.

Steps:

Azure Artifacts is a service in Azure DevOps that lets you store, share, and manage

packages like NuGet, npm, Maven, or Python packages — all in one secure place.

It’s basically your private package feed, just like NuGet.org, but private to your

organization.

Example:

Imagine your company has multiple .NET teams.

Each team builds shared libraries (like logging, authentication, or email helpers).

Instead of everyone copying DLLs, they publish them to Azure Artifacts — and others

can easily consume them as NuGet packages.

2⃣ How do you host and consume NuGet packages in Azure DevOps?

You can host and consume packages in Azure Artifacts with just a few steps.

🏗 To host (publish) a package:

Azure Artifacts is a service in Azure DevOps that lets you store, share, and manage

packages like NuGet, npm, Maven, or Python packages — all in one secure place.

It’s basically your private package feed, just like NuGet.org, but private to your

organization.

Example:

Imagine your company has multiple .NET teams.

Each team builds shared libraries (like logging, authentication, or email helpers).

Instead of everyone copying DLLs, they publish them to Azure Artifacts — and others

can easily consume them as NuGet packages.

2⃣ How do you host and consume NuGet packages in Azure DevOps?

You can host and consume packages in Azure Artifacts with just a few steps.

🏗 To host (publish) a package:

What is the purpose of the dotnet build, dotnet test, and dotnet

publish commands in pipelines?

Answer:

• dotnet build → Compiles your code and checks for errors.
• dotnet test → Runs all your unit tests.
• dotnet publish → Packages your app for deployment (e.g., to Azure Web App).

Example:

In a pipeline:

• script: dotnet build
• script: dotnet test
• script: dotnet publish -c Release -o

$(Build.ArtifactStagingDirectory)

The final publish step outputs deployable files like .dll or .zip.

What is the difference between an organization, project, and repository

in Azure DevOps?

Answer:

• Organization: The top-level container (like a company or department).
• Project: A workspace for a specific product or app.
• Repository: Where your source code lives.

Example:

Organization: ContosoTech

→ Project: MobileApp

→ Repository: ContosoApp-Frontend