Interview Q&A

Short answer: 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 code

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.

Real-world example (ShopNest)

ShopNest’s YAML pipeline builds on every PR, runs unit tests, then deploys to a staging slot on main-branch merges.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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 code

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.

Real-world example (ShopNest)

ShopNest’s YAML pipeline builds on every PR, runs unit tests, then deploys to a staging slot on main-branch merges.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

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

Explain a bit more

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.

Real-world example (ShopNest)

Azure DevOps holds ShopNest repos, boards, and release pipelines in one place so build + deploy stay repeatable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short 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.

Real-world example (ShopNest)

A “Add UPI payment” feature is a User Story with Tasks. Testers link bugs to the same work item for traceability.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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.

Real-world example (ShopNest)

Azure DevOps holds ShopNest repos, boards, and release pipelines in one place so build + deploy stay repeatable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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.

Real-world example (ShopNest)

Azure DevOps holds ShopNest repos, boards, and release pipelines in one place so build + deploy stay repeatable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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 code

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.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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

Real-world example (ShopNest)

Azure DevOps holds ShopNest repos, boards, and release pipelines in one place so build + deploy stay repeatable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.