Interview Q&A

Model Description Example for .NET

IaaS

(Infrastructure)

Provides virtual machines,

networking, storage

zure VM running Windows + IIS

hosting ASP.NET app

PaaS (Platform) Managed hosting environment

for apps

zure App Service, Azure Functions

SaaS (Software) Fully managed software

ccessible via browser

Office 365, Dynamics 365

Answer: zure assigns identity to service Example: App Service → accesses Key Vault securely Real-world Example: Instead of: var secret = "hardcoded-key"; We use: Managed Identity + Key Vault Why interviewers ask: To check security maturity level

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: A set of NuGet packages to interact with Azure resources from .NET apps. Includes services like Storage, Cosmos DB, Key Vault, Event Hubs, and more.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

dvanced insight: Configure rules based on: CPU % Request count

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: PI? Strong Answer: Feature Azure Function Web API Execution Event-driven Request-drive Scaling Auto Manual/Auto Use case Background jobs Business APIs Real-world Example: API → user requests Function → email sending

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Azure App Service is a fully managed PaaS platform for hosting web apps, REST PIs, and mobile backends. It handles infrastructure, scaling, security, and patching automatically.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Web Apps: Designed for websites, support Razor Pages, MVC, and Blazor. API Apps: Optimized for RESTful APIs, includes built-in Swagger support and API uthentication features.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Defines the compute resources (CPU, memory, storage) for your App Service. Determines pricing tier, scaling, and availability.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: zure? Strong Answer CQRS separates: Read operations Write operations Implementation: Commands → Service Bus Queries → Read DB Real-world Example: E-commerce: Writes → Order DB Reads → Optimized read DB

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Method Description Use Case

Zip Deploy Upload a zip file; replaces app

content

Quick automated

deployments

FTP/FTPS Manual file upload via FTP client Small apps or manual

updates

WebDeploy

(MSDeploy)

Incremental deployment with config

& db sync

Complex apps with

dependencies

Answer: developers make in Azure?” Strong Answer: Not designing for failure and scalability. Common mistakes: No caching Tight coupling No retry logic Hardcoded secrets Real-world impact: System crashes under load.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Kudu is the deployment engine behind Azure App Service. Provides: Console access to the app environment Process explorer Deployment logs File explorer for troubleshooting

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

• A deployment slot is a separate environment for your App Service, e.g., staging,

testing, QA, or production.

• Each slot runs as a full App Service instance with its own hostname, configuration,

nd settings.

• Enables zero-downtime deployments by swapping slots.

Answer: In-process: Runs within the same process as the Functions runtime. Direct access to runtime APIs. Isolated process: Runs in a separate process, providing better dependency isolation and .NET version flexibility.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

• A trigger defines how and when a function is invoked.
• Examples: HTTP requests, queue messages, blob changes, timer events.
• Every function must have exactly one trigger.

Example (HTTP trigger):

[FunctionName("HttpTriggerFunction")]

public static IActionResult Run(

[HttpTrigger(AuthorizationLevel.Function, "get", "post")]

HttpRequest req,

ILogger log)

{

log.LogInformation("HTTP trigger executed.");

return new OkObjectResult("Hello from Azure Function!");
}

Answer: Trigger: Invokes the function. Every function must have one trigger. Binding: Connects function inputs/outputs to external resources. Optional, can have multiple.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Azure SQL Database is a fully managed relational database service on Azure. Provides automatic backups, patching, scaling, high availability, and security.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Azure Cosmos DB is a globally distributed, multi-model NoSQL database. Supports key-value, document, graph, and column-family data models. Provides automatic scaling, low latency, and global replication.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Serverless compute tier auto-scales based on workload and pauses during inactivity. Cost-efficient for intermittent workloads.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: DTU (Database Transaction Unit): Bundled measure of CPU, memory, IOPS. vCore: Separate allocation of virtual cores, memory, and storage. vCore allows flexible scaling and cost optimization.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Restricts database access to specific IP ranges or VNets. Ensures only authorized clients can connect.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Provisioned throughput: Fixed Request Units (RUs) per second. Serverless: Automatically scales and billed per request. Use serverless for low or intermittent traffic.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Azure.Cosmos NuGet package (v3+) is preferred. Example: var cosmosClient = new CosmosClient(endpointUri, primaryKey); var container = cosmosClient.GetContainer("DatabaseId", "ContainerId");

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Cosmos DB automatically indexes all properties by default. You can customize index paths for performance. { "indexingMode": "consistent", "includedPaths": [ {"path": "/name/?"}, {"path": "/age/?"} }

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Azure Key Vault is a cloud service for securely storing and managing secrets, keys, and certificates. Helps protect sensitive information like connection strings, passwords, API keys, nd encryption keys.

What interviewers expect

• A clear definition tied to Azure in Microsoft Azure projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microsoft Azure application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microsoft Azure architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.