Azure Interview Questions - Mentorstag

Azure Interview Questions

Here we have list of all the important azure interview questions which will surely help you in cracking your first job as azure developer.

This page is only focusing on Azure interview questions so If you are interested in Azure learning videos or tutorials then we have a perfect place for you here. 

Preparing for an Azure interview? Give your preparation a new edge with these frequently-asked Microsoft Azure interview questions that we have brought with the detailed answers!

In this page, we have compiled some of the common Azure interview questions that are most acceptable to understand all the basic and critical aspects to crack the interview. We present here the most frequently asked 50 questions with their appropriate answers that will enable you to crack the interview.

Please send us an email on if you have some suggestions or if you want to add or modify some of angular interview questions available in this page.

  • By creating a cloud service, you can deploy a multi-tier web application in Azure, defining multiple roles to distribute processing and allow flexible scaling of your application. A cloud service consists of one or more web roles and/or worker roles, each with its own application files and configuration. Azure Websites and Virtual Machines also enable web applications on Azure. The main advantage of cloud services is the ability to support more complex multi-tier architectures.
  • A collective name of Microsoft’s Platform as a Service (PaaS) offering which provides a programming platform, a deployment vehicle, and a runtime environment of cloud computing hosted in Microsoft datacenters.
  • A fault domain is a logical group of the underlying hardware that shares a common power source and network switch, similar to a rack within an on-premise data-centers. As you create VMs within an availability set, the Azure platform automatically distributes your VMs across these fault domains. This approach limits the impact of potential physical hardware failures, network outages, or power interruptions.
  • An update domain is a logical group of the underlying hardware that can undergo maintenance or can be rebooted at the same time. As you create VMs within an availability set, the Azure platform automatically distributes your VMs across these update domains. This approach ensures that at least one instance of your application always remains running as the Azure platform undergoes periodic maintenance. The order of update domains being rebooted may not proceed sequentially during planned maintenance, but only one update domain is rebooted at a time.
  • Microsoft Azure Redis Cache is based on the popular open source Redis Cache and can be accessed by a wide variety of Redis clients for many programming languages. Each client has its own API that makes calls to the Redis cache instance using Redis commands.
  • Because each client is different, there is not one centralized class reference on MSDN, and each client maintains its own reference documentation. In addition to the reference documentation, there are several tutorials showing how to get started with Azure Redis Cache using different languages and cache clients. To access these tutorials, see How to use Azure Redis Cache and click the desired language from the language switcher at the top of the article.

  • Storage keys or Access Keys are used as an authentication mode for accessing the storage services account to manipulate information based on our requirements. In Windows Azure, we have an option to provide a Primary Access Key and a Secondary Access Key, even though we will use a single access key to authenticate our application to the storage. The main reason to provide the secondary access key is to avoid downtime to the application. If we need to change the application access key by regenerating the access key it takes quite some time to take effect; this provides a downtime.

    To avoid this type of situation, a secondary access key is provided so that if the primary needs to be changed or regenerated we can map the secondary temporarily to the storage and regenerate the primary. Let us see step by step of how to get the Access Keys using Windows Azure Management Portal.

  • The table is one type of Azure Storage, where you can store your data as storage. Blobs are stored in container and Entity in the table.

    Following are the key concepts in the table.

    Tables allow structured data storage
    There can be 0..n tables in a storage account
    Table store data as a collection of entities
    The entity has a primary key and properties as key-value pair

  • Windows Azure data storage enables users to store, access, analyze and protect their data while making it available from anywhere and at any time. Windows Azure provides various services from storing data in SQL databases in the cloud for analysis and reporting to meet the needs of your business. Windows Azure ensures data security with a high throughput of application data in the cloud. Windows Azure typically offers the following three types of storage in the cloud atmosphere.

    BLOB: BLOBs offer a mechanism for storing large amounts of text or binary data, such as images, audio, and visual files. It can scale up to 200 terabytes and can be accessed using REST APIs. We can move BLOB data as a single volume between private and public clouds using Windows Azure Drive.

    Table: Tables represent storage locations across machines for data that reside in the form of entities and properties on the cloud. Tables store large amounts of unstructured data that can be accessed either using REST APIs from within a service running in Windows Azure or directly over the Internet using HTTP/HTTPS.

    Queue: The sole objective of a Queue is to enable communication between Web and Worker Role instances. They aid in storing messages that may be accessed by a client. Web Role instances can initiate user requests that need to be processed in the background. On the other side a Worker Role observers the queue to process the request and respond back via a queue to the Web Role instance.

  • Block blobs are comprised of blocks, each of which is identified by a block ID.
    You create or modify a block blob by uploading a set of blocks and committing them by their block IDs.
    If you are uploading a block blob that is no more than 64 MB in size, you can also upload it in its entirety with a single Put Blob operation. -Each block can be a maximum of 4 MB in size. The maximum size for a block blob in version 2009-09-19 is 200 GB, or up to 50,000 blocks.

    Page blobs are a collection of pages. A page is a range of data that is identified by its offset from the start of the blob. To create a page blob, you initialize the page blob by calling Put Blob and specifying its maximum size.
    -The maximum size for a page blob is 1 TB. A page written to a page blob may be up to 1 TB in size.
    what to use block blobs for streaming video. “The application must provide random read/write access” which is supported by Page Blobs.

  • Windows Azure supports two types of queue mechanisms: Windows Azure Queues and Service Bus Queues.

    Windows Azure Queues, which are part of the Windows Azure storage infrastructure, feature a simple REST-based Get/Put/Peek interface, providing reliable, persistent messaging within and between services.
    Service Bus Queues are part of a broader Windows Azure messaging infrastructure that supports queuing as well as publish/subscribe, Web service remoting, and integration patterns.

  • The following are some common reason for a cache disconnect.

    Client-side causes
    The client application was redeployed.
    The client application performed a scaling operation.
    In the case of Cloud Services or Web Apps, this may be due to auto-scaling.
    The networking layer on the client side changed.
    Transient errors occurred in the client or in the network nodes between the client and the server.
    The bandwidth threshold limits were reached.
    CPU bound operations took too long to complete.
    Server-side causes
    On the standard cache offering, the Azure Redis Cache service initiated a fail-over from the primary node to the secondary node.
    Azure was patching the instance where the cache was deployed
    This can be for Redis server updates or general VM maintenance.

  • Cloud computing providers offer their services according to three fundamental models: Infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS) where IaaS is the most basic and each higher model abstracts from the details of the lower models.

    Examples of IaaS include Amazon CloudFormation (and underlying services such as Amazon EC2), Rackspace Cloud, Terremark, Windows Azure Virtual Machines, Google Compute Engine. and Joyent.

    Examples of PaaS include Amazon Elastic Beanstalk, Cloud Foundry, Heroku,, EngineYard, Mendix, Google App Engine, Windows Azure Compute, and OrangeScape.

  • A cloud service role is comprised of application files and a configuration. A cloud service can have two types of role.
  • The cloud service configuration file (.cscfg) provides configuration settings for the cloud service and individual roles, including the number of role instances.
  • Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Azure Redis Cache is based on the popular open-source Redis cache. It gives you access to a secure, dedicated Redis cache, managed by Microsoft, and accessible from any application within Azure. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries.

    Apart from this Azure Interview Questions Blog, if you want to get trained from professionals on this technology.

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Azure Redis Cache is based on the popular open-source Redis cache. It gives you access to a secure, dedicated Redis cache, managed by Microsoft, and accessible from any application within Azure. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries.

    Apart from this Azure Interview Questions Blog, if you want to get trained from professionals on this technology.

  • This is the service model on which you will host your application(s), for example, IaaS, PaaS or SaaS. Each of these service models requires various levels of support and responsibilities once a system is deployed to the platform. To resolve the future challenges that you might encounter you need to understand the models carefully. Other than the service model, the second, you need to decide whether you want a Private or On-Premise cloud, or you want your application to be deployed on a Public Cloud.

    Every service model offers you some kind of resource required to operate the most web-enabled systems imaginable.

  • Redis Databases are just a logical separation of data within the same Redis instance. The cache memory is shared between all the databases and actual memory consumption of a given database depends on the keys/values stored in that database. For example, a C6 cache has 53 GB of memory. You can choose to put all 53 GB into one database or you can split it up between multiple databases.

  • The Azure Compute SLA guarantees that, when you deploy two or more role instances for every role, access to your cloud service will be maintained at least 99.95 percent of the time. Also, detection and corrective action will be initiated 99.9 percent of the time when a role instance’s process is not running.

  • Sync Services is provided by Microsoft Azure where you can keep a SQL Azure database synchronized with another database. You can take a backup of a database from one region to another region. There is a simple procedure you need to follow to configure this service. If not a complete database then you can at least keep selected tables or selected rows of tables synchronized.

    This service provides the following two ways to synchronize:

    Synchronize a SQL Azure database from one SQL Azure server to another SQL Azure server.
    Synchronize a SQL Azure Database from an Azure Server to a Local Server database.

  • This is not supported. You cannot use the Azure Resource Manager to deploy a virtual machine into a virtual network that was created using classic deployment.

  • Minimal monitoring, which is configured by default for a cloud service, uses performance counters gathered from the host operating systems for role instances (virtual machines). Verbose monitoring gathers additional metrics based on performance data within the role instances to enable closer analysis of issues that occur during application processing.

  • The main difference between the two is that an instance of a web role runs IIS, while an instance of a worker role does not. Both are managed in the same way, however, and it’s common for an application to use both. For example, a web role instance might accept requests from users, then pass them to a worker role instance for processing.

  • Windows Azure is created by Microsoft, it is a cloud computing infrastructure and platform. It is designed for working on the global network of Microsoft. It is for building, managing and deploying services and applications. Windows Azure supports various programming languages, tools, and frameworks. It can be included in both Microsoft specific and third-party systems and software. It provides an infrastructure of services and platforms as services. It is also an open and flexible cloud platform that makes it easy to work on the global network. It helps us to quickly create, manage and deploy applications on the global network.

    Features of Windows Azure

    Windows Azure runs and stores the data on Microsoft datacenters. There are many features that are specified here:

    Websites allow the developers to build the sites using ASP.NET, PHP, etc and deploy these websites using FTP, Git, etc.

    SQL Database, formally known as Azure database creates, extends and scales the application into the cloud using Microsoft SQL Server.

    This is Microsoft’s platform as a service that supports the Multi-tier applications and automated deployment.
    Windows Azure Services

    There are various types of services that are provided by Windows Azure:

    Web Sites
    Cloud services
    Virtual Machine
    Data Management

    SQL Database.

    Business Analytics

    SQL Reporting.
    Data Marketplace.
    Windows Azure Services

  • hich the two deployments are accessed. After the deployment, the DNS name for the cloud service points to the deployment that had been in the staging environment.

  • Scaling by adding additional instances is often referred to as scaling out. Windows Azure also supports scaling up by using larger role instances instead of more role instances.

    By adding and removing role instances to your Windows Azure application while it is running, you can balance the performance of the application against its running costs.

    An autoscaling solution reduces the amount of manual work involved in dynamically scaling an application.

  • Virtual Machine (VM) roles, now in Beta, enable you to deploy a custom Windows Server 2008 R2 (Enterprise or Standard) image to Windows Azure. You can use the VM role when your application requires a large number of server OS customizations and cannot be automated. The VM Role gives you full control over your application environment and lets you migrate existing applications to the cloud.

  • We use a more sophisticated strategy to lock accounts. This is based on the IP address of the request and the passwords entered. The duration of the lockout also increases based on the likelihood that it is an attack.

  • Azure AD has around 2600 pre-integrated applications. All pre-integrated applications support single sign-on (SSO). SSO let you use your organizational credentials to access your apps. Some of the applications also support automated provisioning and de-provisioning.

    Apart from this Azure Interview Questions Blog, if you want to get trained from professionals on this technology.

  • By default, one is assigned the Subscription Administrator role when he/she signs up for Azure. A subscription admin can use either a Microsoft account or a work or school account from the directory that the Azure subscription is associated with. This role is authorized to manage services in the Azure portal. If others need to sign in and access services by using the same subscription, you can add them as co-admins.

    Azure AD has a different set of admin roles to manage the directory and identity-related features. These admins will have access to various features in the Azure portal or the Azure classic portal. The admin’s role determines what they can do, like create or edit users, assign administrative roles to others, reset user passwords, manage user licenses, or manage domains.

  • The Azure Storage Queue is simple and the developer experience is quite good. It uses the local Azure Storage Emulator and debugging is made quite easy. The tooling for Azure Storage Queues allows you to easily peek at the top 32 messages and if the messages are in XML or JSON, you’re able to visualize their contents directly from Visual Studio Furthermore, these queues can be purged of their contents, which is especially useful during development and QA efforts.

    The Azure Service Bus Queues are evolved and surrounded by many useful mechanisms that make it enterprise worthy! They are built into the Service Bus and are able to forward messages to other Queues and Topics. They have a built-in dead-letter queue and messages have a time to live that you control, hence messages don’t automatically disappear after 7 days.

    Furthermore, Azure Service Bus Queues have the ability to delete themselves after a configurable amount of idle time. This feature is very practical when you create Queues for each user because if a user hasn’t interacted with a Queue for the past month, it automatically gets clean it up. It’s also a great way to drive costs down. You shouldn’t have to pay for storage that you don’t need. These Queues are limited to a maximum of 80gb. Once you’ve reached this limit your application will start receiving exceptions. 

  • Azure Diagnostics is the API that enables you to collect diagnostic data from applications running in Azure. Azure Diagnostics must be enabled for cloud service roles in order for verbose monitoring to be turned on. For more information.

  • Windows Azure diagnostics provides a facility to store diagnostics data. Some diagnostics data is stored in a table, while some are stored in a blob. For collecting diagnostics data, we must initialize the Windows Azure diagnostic monitor. The Windows Azure diagnostic monitor runs in Windows Azure and in the computer’s emulator and collects diagnostic data for a role instance.

  • Following diagnostics data is stored in table storage:

    Data Source Table name in Azure Storage Detail
    Windows Azure Logs WADLogsTable These are the application logs dumped from the application.
    Windows Azure Diagnostics Infrastructure Logs WADDiagnosticInfrastructureLogsTable These are the logs about running of diagnostics service.
    Windows Event logs WADWindowsEventLogsTable These are the logs generated on the instance where logs are running.
    Performance counters WADPerformanceCountersTable These are the performance matrices like memory utilization, processor utilization, response time, etc.

    Following diagnostics data is stored in blob storage:

    Data Source Container name in azure storage Detail
    IIS Logs wad-its-logfiles These are the IIS logs generated by role instances.
    Failed Request Logs wad-iis-failedreqlogfiles These are the IIS failed requests logs generated by role instances.
    Crash Dumps wad-crash-dumps These are the logs generated on the application crash.

  • The main reason for using queues is to provide loose connectivity among various components. For example, we have two components of an application to exchange data. Here one of them is on-premise and one exists in the cloud. Here if we use a web service to exchange data we have the following issues:

    Both components should be online simultaneously; if one partner is down, then the communication will not work.
    It’s difficult to scale up if more work is present.
    In Azure Queues, you have a queue as a mediator that connects the two components, so when the receiver is down, the sender can still insert messages into the queue, once a receiver comes online it can receive a message from that queue. And for scale-up, we just need to add more receivers and your queue is processed in parallel.

  • The queue is one type of Azure Storage, where you can store your data as storage. Blobs are stored in a container, Entity in table and Message in Queue.

    Following are the key concepts in the queue.

    FIFO implementation
    Messages are added to the end of the Queue and processed from the front
    Queues provide a good way of Front end and Back end decoupling
    In the real world example, the user can queue a job through the web role (front end) and the job can be processed by a worker role (back end). This gives an opportunity to decouple the web role and worker role.

    worker role

    Place a new label control on the aspx page and add the following code in the page load event.
    protected void Page_Load(object sender, EventArgs e)

    StorageCredentialsAccountAndKey accountAndKey = newStorageCredentialsAccountAndKey(“account”, “key”);
    CloudStorageAccount account = new CloudStorageAccount(accountAndKey, true);
    CloudQueueClient client = account.CreateCloudQueueClient();
    CloudQueue queue = client.GetQueueReference(“workitems”);
    CloudQueueMessage message = new CloudQueueMessage(“Test Work Item”);
    // Populate the messages
    message = queue.GetMessage();
    if (message != null) Label1.Text = “Message in Queue: ” + message.AsString;

  • Azure Search is a cloud search-as-a-service solution that delegates server and infrastructure management to Microsoft, leaving you with a ready-to-use service that you can populate with your data and then use to add search to your web or mobile application. Azure Search allows you to easily add a robust search experience to your applications using a simple REST API or .NET SDK without managing search infrastructure or becoming an expert in search.

  • Windows Azure Portal: To run an application, a developer accesses the Windows Azure portal through her Web browser, signing in with a Windows Live ID. She then chooses whether to create a hosting account for running applications, a storage account for storing data, or both.

    Once the developer has a hosting account, the developer can use a Windows Azure portal to submit applications to Windows Azure.

    When the user sends a request to an application hosted on Azure (that can be passed by protocols like HTTP, HTTPS or TCP), the request will be received from the load balancer. The load balancer balances the load across all the instances of the role (Web, Worker, and VM).

    Azure Fabric:

    The Azure fabric is the main core concept over here. It provides a service called the Azure Fabric Controller. It is called as OS for the Azure. Because it handles/manages:

    All roles (computing) and resources.
    Deployment and activating services.
    Health monitoring for all services.
    Allocating, releasing of resources.
    Provisioning VM, terminating, etc.
    Updating patches for the installed OS on VM automatically.
    So there would be better to have two instances of roles and also no need to worry about software updates for the user.
    Azure Fabric

  • Virtual machine scale sets are Azure compute resource that you can use to deploy and manage a set of identical VMs. With all the VMs configured the same, scale sets are designed to support true autoscale, and no pre-provisioning of VMs is required. So it’s easier to build large-scale services that target big compute, big data, and containerized workloads.

  • It is a command-line tool that generates a service package file (.cspkg) and prepares an application for deployment, either to Windows Azure or to the compute emulator.