Interview Q&A

Short answer: How do you design a production-grade ASP.NET Core application in Azure? is a common interview topic in Microsoft Azure. Give a clear definition, then one concrete example.

Real-world example (ShopNest)

ShopNest on Azure typically uses App Service + SQL Database + Blob Storage + Application Insights for monitoring.

How to answer in 60 seconds

1. Define it in one simple sentence.
2. Say where you used it (API, DB, UI, cloud).
3. Mention one benefit and one trade-off.

Short answer: pplication in Azure?

Real-world example (ShopNest)

ShopNest on Azure typically uses App Service + SQL Database + Blob Storage + Application Insights for monitoring.

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: zure Function processes it asynchronously. Trigger: QueueTrigger Use Case: Payment processing, inventory updates, email notifications. }

Example code

public record Order(int Id, string Product, int Qty); ✅ 2. Schedule Daily Database Backup (Timer Trigger) Scenario: Run SQL backup, archive logs, or clean old data every night. Trigger: TimerTrigger Use Case: Automation jobs, scheduled cleanups, maintenance tasks. Code Example public static class DailyBackup
{ [FunctionName("DailyDatabaseBackup")] public static async Task Run( [TimerTrigger("0 0 2 * * *")] TimerInfo timer, ILogger log) { log.LogInformation("Starting daily database backup..."); // Call SQL API / storage account to create backup wait BackupService.RunBackupAsync(); log.LogInformation("Backup completed."); }
} ⏰ "0 0 2 * * *" → runs daily at 2 AM ✅ 3. Generate Thumbnails for Uploaded Images (Blob Trigger) Scenario: When a user uploads an image, automatically create a thumbnail and store it. Trigger: BlobTrigger Use Case: Photo apps, e-commerce product images, document workflows. Code Example [FunctionName("GenerateThumbnail")] public static async Task Run( [BlobTrigger("uploads/{name}", Connection = "StorageConn")] Stream input, string name, [Blob("thumbnails/{name}", FileAccess.Write, Connection = "StorageConn")] Stream output, ILogger log) { log.LogInformation($"Creating thumbnail for {name}"); using var image = Image.Load(input);
var data = eventGridEvent.Data.ToObjectFromJson<UserEvent>(); log.LogInformation($"New user signup: {data.Email}"); wait EmailService.SendWelcomeEmail(data.Email); } ✅ 5. Serverless REST API (HTTP Trigger) Scenario: Build lightweight APIs without using App Services. Trigger: HttpTrigger Use Case: Microservices, webhooks, backend-for-frontend APIs. Code Example [FunctionName("GetUserById")] public static IActionResult Run( [HttpTrigger(AuthorizationLevel.Function, "get", Route = "users/{id}")] HttpRequest req, string id, ILogger log) {
var user = UserDb.GetUser(id);
if (user == null)
return new NotFoundResult();
return new OkObjectResult(user);
} ✅ 6. Process Messages from Service Bus (Service Bus Trigger) Scenario: Enterprise integration between microservices. Trigger: ServiceBusTrigger Use Case: Order processing, billing, messaging between systems. Code Example [FunctionName("ProcessPayment")] public static async Task Run( [ServiceBusTrigger("payments", Connection = "ServiceBusConn")] string message, ILogger log) {
var payment = JsonSerializer.Deserialize<Payment>(message); log.LogInformation($"Processing payment {payment.Id}"); wait PaymentService.CompleteAsync(payment); } ✅ 7. Auto-Delete Expired Files (Blob + Timer + Logic) Scenario: Remove files older than 30 days to reduce storage costs. Trigger: TimerTrigger Use Case: Data lifecycle automation. Code Example [FunctionName("DeleteOldFiles")] public static async Task Run( [TimerTrigger("0 */30 * * * *")] TimerInfo timer, ILogger log) {
var client = new BlobContainerClient( Environment.GetEnvironmentVariable("StorageConn"), "logs"); wait foreach (var blob in client.GetBlobsAsync()) {
if (blob.Properties.CreatedOn < DateTimeOffset.UtcNow.AddDays(-30)) { wait client.DeleteBlobAsync(blob.Name); log.LogInformation($"Deleted old file: {blob.Name}"); }
}
}

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: You can use XML or JSON transformation tasks in your release pipeline to adjust settings per environment. Example (Classic): Add a File Transform or Replace Tokens task.

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: dd and commit: git add . git commit git push

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: You enforce them with branch policies. zure DevOps lets you require: A minimum number of reviewers (e.g., 2).

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: Each build or release agent runs under a specific identity that needs permissions to deploy or access resources. Best practices: Use Managed Identity for self-hosted agents (so no credentials are stored).

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: Each build or release agent runs under a specific identity that needs permissions to deploy or access resources. Best practices: Use Managed Identity for self-hosted agents (so no credentials are stored).

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: Azure DevOps includes built-in Analytics and Reporting tools to help track performance, quality, and productivity. Common reports: Pipeline Analytics: Success/failure trends, duration, frequency of builds.

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: Common tasks: UseDotNet@2 → Installs .NET SDK. NuGetCommand@2 → Restores NuGet packages.

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: Feature Git TFVC Type Distributed Centralized History Full copy on each developer’s machine Stored on server Branching Lightweight and fast Heavier and slower Offline work Possible Needs connection Common use Modern DevOps projects Legacy TFS projects Example: In Git, you can commit locally even offline on a flight — with TFVC, you’d need… server ccess.

Explain a bit more

Git is now the default in Azure DevOps for flexibility and collaboration.

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 tasks are commonly used in .NET build pipelines? Answer: Common tasks: UseDotNet@2 → Installs .NET SDK. NuGetCommand@2 → Restores NuGet packages. DotNetCoreCLI@2 → Builds, tests, and publishes your app. PublishBuildArtifacts@1 → Stores your compiled output. Example: A .NET Core pipeline may use: task: DotNetCoreCLI@2 inputs: command: 'build'

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: company using Jenkins moves to Azure DevOps to unify code and pipelines. They convert Jenkinsfile logic to YAML, using tasks like DotNetCoreCLI@2 and zureWebApp@1.

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: .NET Core API gets built automatically when code is pushed to main. If tests pass, it’s deployed to staging — and after approval, to production.

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: Zero-downtime means your API stays live while deploying new versions. Ways to achieve it: Use Azure App Service Deployment Slots (swap after warm-up).

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: 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: How do you restore NuGet packages in a build pipeline? Answer: Use either: script: dotnet restore or task: NuGetCommand@2 inputs: command: 'restore' This pulls dependencies from NuGet.org or an internal feed. Example: If your project uses private packages, you can add a NuGet service connection or Azure Artifacts feed to authenticate.

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: 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: How do you perform rollback in case of a failed deployment?

Explain a bit more

Answer: There are several ways: Use deployment slots — just swap back to the previous slot. Re-deploy a previous successful release in Azure DevOps. Use versioned artifacts — keep your last working package and redeploy it. Example: If your new API build breaks production, you can quickly redeploy the previous successful release version from Azure DevOps → Releases → “Redeploy”.

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: How do you run unit tests and publish test results in a pipeline? Answer: You use the DotNetCoreCLI@2 task with test command and publish results. Example (YAML): task: DotNetCoreCLI@2 inputs: command: 'test' projects: '**/*Tests.csproj' publishTestResults: true Azure Pipelines will then display test results (passed, failed, duration) in the build summary.

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 are service connections in Azure DevOps? Answer: 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.

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.