A build is the solution of an output. In Azure projects, you get the record with a .cspkg extension, that is, a Cloud Service Package is utilized for the deployment of your cloud administration.

Build Servers: In general terms, a build server is a machine where you put your deployment packages.

To utilize Team Foundation Build, you should have no less than one build machine. This machine can be a physical machine or a virtual machine.

Build Controllers: Manufacture Controllers are the component in the build system that accepts the build requests from any task inside the group project. Each build controller is dedicated to a solitary team project collection. So, there is a balanced relationship between a team project and a build controller.

Build Agents: Build Agents are components in the build system that accomplishes more processor-concentrated work.

Azure App Service is a completely managed Platform-as-a-Service (PaaS) offering for proficient developers that conveys a rich arrangement of abilities to the web, mobile, and integration scenarios. Mobile apps in Azure App Service offer a very adaptable, universally accessible mobile application development platform for Enterprise Developers and System Integrators that conveys a rich set of capacities to mobile engineers.

Profiling is only a procedure for measuring the performance analysis of an application. It is normally done to guarantee that the application is sufficiently steady and can maintain overwhelming traffic.

Visual Studio gives us different tools to do it by gathering the performance information from the application that likewise helps in troubleshooting issues.

Once the profiling wizard is run, it sets up the execution session and collects the data of the sample.

The profiling reports help in:

• Deciding the longest running strategies inside the application
• Measuring the execution time of every strategy in the call stack
• Assessing memory allocation

A cmdlet is a lightweight command that is utilized as a part of the Microsoft PowerShell environment. The cmdlets are summoned by the Windows PowerShell to automate the scripts which are in the command line. Windows PowerShell runtime additionally invokes them automatically through Windows PowerShell APIs.

Windows Azure Scheduler enables you to invoke activities, for example, calling HTTP/S endpoints or presenting a message on a storage queue on any schedule.

With Scheduler, you make jobs in the cloud that dependably call services both inside and outside of Windows Azure and execute those jobs on-demand, on a routinely repeating schedule, or assign them for a future date.

To make an Azure HDInsight Cluster, open the Azure portal > click on New > select Data Services > click on HDInsight.

Hadoop is the default and native execution of Apache Hadoop.

HBase is an Apache open-source NoSQL database based on Hadoop that gives random access and solid consistency for a lot of unstructured data.

Apache Storm is a distributed, fault-tolerant, open-source computation system that enables you to process data in real-time.

Content Analytics API is a part of content examination web administrations worked with Azure Machine Learning. The API can be utilized to analyze unstructured content for tasks such as sentiment analysis and key-phrase extraction.

The API restores a numeric score between 0 and 1. Scores near 1 show positive sentiment, while scores near 0 demonstrate negative sentiment.

The upside of this API is that another new model need not be planned and prepared; the user just needs to bring the data and call the service to get the sentiment results.

Migration Assistant tool will examine our IIS installation and recognize the sites that can be migrated to the cloud, featuring any components which can’t be migrated or are unsupported on the platform.

Once broken down, this tool will likewise create sites and databases provided under the given Azure membership.

A public cloud is utilized as a service through the Internet by users, while a private cloud is deployed within specific limits like firewall settings and is totally overseen and checked by the users dealing with it in an organization.

The SLA ensures that, when you send two or more role instances for each role, access to your cloud service will be maintained not less than 99.95 percent of the time. Additionally, identification and re-correction activities will be started 99.9 percent of the time when a role instance’s procedure isn’t running.

To add an administrator to the Azure portal, it has to be given the owner role. It will be able to manage only those resources in the subscription that are assigned to it. To add an administrator, follow these steps:

1. Sign in to the Azure portal
2. Go to the Hub menu and then to Subscriptionand select the subscription that the administrator will need access to
3. Select Access control (IAM)in the subscription blade, and then click on Add
4. Go to Select a role, and click on Owner
5. Here, provide the email address of the user to be assigned as the owner
6. Click on the user, and then click on Select

1. The first time you start the SQL Server Management Studio, the Connect to Serverdialog box opens up automatically. You can also open it manually by going to Object Explorer > Connect > Database Engine.
2. Then, enter the following information in the Connect to Serverwindow:
   Server Type Database Engine
   Server Name Enter the name of your Azure SQL Database or Azure Managed Instance
   Authentication SQL Server Authentication
   Login Enter the server account user ID
   Password Enter the server account passwordYou can also choose to change the additional connection options by going to Options. 
3. Click on Connect after completing all the required fields
   
   If the firewall settings are not set up, a prompt appears to configure the same. Once signed in, provide the Azure account login information, and set the firewall rule. Then, click on OK.
4. To verify if your Azure Database connection is successful, expand and explore Object Explorerfor the server name, the SQL Server version, and the username.

To create a VM on Azure, you need to follow the below steps:

1. Sign in to Azure
2. Sign in to the Azure portal 
3. Search for virtual machines in the search box
4. Under Services, select Virtual machines
5. Click on Addin the Virtual machines page
6. In the Basicstab, under Project details, select the correct subscription, and choose Create new resource group
7. Type myResourceGroupfor the name
8. Under Instance details, the Virtual machine nameshould be myVM
9. Choose your Region[e.g., (US) East US]
10. Choose Windows Server 2019 Datacenterfor theImage
11. Leave the rest as default
12. Under Administrator account, enter a username and a password
13. Under Inbound port rules, click on Allow selected ports,and then select HTTP (80) and RDP (3389) for Select inbound ports
14. The rest will remain as default here
15. Finally, click on the Review + createbutton

1. Authenticate to the Azure portal
2. Click on SQL Databases
3. Click on Servers
4. Click on a server name to connect to
5. Press Configure
6. Open SQL Server Management Studio
7. Connect to Database services (usually, this happens by default)
8. Finally, click on Connect

You can export users from Azure AD by following the below-mentioned steps:

1. Install the Azure PowerShellmodule using the following cmdlet:

install-module az

2.To connect to Azure AD and Azure, run:

Connect-azaccount

3.To export, all users to a CSV file, run:

Get-AzADUser | export-csv file.csv

4.If you only need to export the first 10 users, then you can use:

Get-AzADUser -First 10 |  export-csv file.csv

5.To export all users after the first 2 users, you can use:

Get-AzADUser -Skip 2 | ft

To create a resource group in Azure: 

1. Log in to the Azure portal 
2. In the menu on the left, select Resource groups
3. In the Resource groups page, click on Add
4. Fill in the details in the fields as follows:
   • Subscription: Select your Microsoft Azure subscription
   • Resource group name: Enter a unique name
   • Resource details region: Select a location
5. Click onReview + create
6. Once validation is passed, click on Create to create your resource group

That’s it in our blog on MS Azure interview questions and answers. Hope these Azure questions help you in your Azure Interview job preparation.

The major difference is that Azure scale sets have identical VM’s, and in the case of Availability sets, there is no hard and fast rule for the VM’s to be identical. Let us see other differences here –

Azure offers three other types of storage services, apart from Blob storage, table storage, queue Storage, and file storage.

• Azure table storage: It allows the deployment of applications with semi-structured data and a key-value store, which is NoSQL-based.
  • Used when there is a requirement for applications with a flexible data schema
  • Emphasis is on enterprise-level data and strongly follows consistent models
  • Data is in terms of entities grouped under tables
• Azure queue storage: The message queue system is capable of handling large workloads through the development of flexible and durable applications.
  • Ensures that the applications are scalable and less likely to have component failures
  • The queue monitoring helps the application ensure that the requirements are met
• Azure file storage: It offers file sharing and access using server message block (SMB) protocol. The data is secured with SMB 3.0 and HTTPS.
  • Improves the performance of on-premise applications
  • Azure takes care of OS deployments and hardware management

The major difference is that Azure SQL uses a relational storage structure and Azure Table follows centralized structured data without relations. Other differences are –

Following is an example how one can create a VM using Azure CLI:

az vm create \
--resource-group myResourceGroupName \
--name myVM \
--image Win19Datacenter \
--public-ip-sku Standard \
--admin-username AzureuserNAME \
--admin-password AzurePASSWORD

Azure Scheduler helps us to invoke certain background trigger events or activities like calling HTTP/S endpoints or to present a message on the queue on any schedule.

By using this Azure Schedule, the jobs present in the cloud call services present within and outside of the Azure to execute those jobs on-demand that are routinely on a repeated regular schedule or start those jobs at a future specified date.

Yes, it can be done by defining a separate Load Balancer Role in Azure.

Yes, it is totally possible by making use of the Site Recovery Service provided by Azure. It is capable of handling fail-over and fail-back scenarios between On-Prem Servers and Azure environments.

This issue can be stopped by making use of VM Scale sets by defining proper configuration and conditions to provision a new VM whenever the load to the application increases.

• Azure VM Scale Sets lets the developer create and manage a group of VMs that are load balanced. The scale sets can be configured in such a way that the count of VMs can automatically be increased or decreased based on the application demand or based on a pre-defined schedule.
• Usage of Scale Sets ensures high availability of the applications and allows the developers to manage, update and configure large VMs centrally and also help them support the development of large-scale applications supporting big data, big workloads, and compute loads.
• Azure scale sets can support up to 1,000 VMs. If the custom VM images are created and uploaded, then the limit is 600 VMs.

Azure provides overall 4 types of storage services – Blob Service, Table Storage, Queue Storage, and File Storage Services as shown in the figure below:

• Azure Table Storage: This type of storage lets user deploy their applications with semi-structured data and a NoSQL-based key-value store.
  • This is used when there is a need for applications that follow a flexible schema of data.
  • Table Storage focuses on enterprise-level data and follows strongly consistent models.
  • The data is represented in terms of Entities grouped under tables.
• Azure Queue Storage: This storage provides a message queue system for handling large workloads by letting users develop and build flexible and modular applications.
  • This storage ensures that the application becomes less prone to failure of individual components and is scalable.
  • With the help of message queues, it provides the queue monitoring feature for helping the application to ensure the user demands are met.
• Azure File Storage: This storage type provides features of file sharing that are accessible using SMB (Server Message Block) Protocol. The data in this storage is protected by HTTPS and SMB 3.0 Protocol.
  • They are used for improving the performance and capabilities of on-premise applications.
  • The OS deployments and hardware management is taken by Azure itself.

• Possibility 1:Azure VNET based “Point to Site” service can be a correct choice for this scenario of connecting one on-premise DB to an Azure-hosted app. “Point to Site” is valid for cases where the count of resources to be connected via VPN is very limited.
• Possibility 2:In case there is a large number of resources for connection, then “Site to Site” or “Express routes” are the other options that could be considered.
  • There might be chances that using “Site to Site” might lead to network latency as VPN due to these work only via Internet (public infrastructure). In such cases, “Express Routes” are used as it provides dedicated leased line for overcoming latency issues.
• Possibility 3:In case the customer is not willing to work via VNET, then Windows Communication Foundation (WCF) service can be developed and hosted on-premise which would have CRUD operations meant only for the database hosted on-premise. This works by means of using the “Service bus relay” option for developing communication between the Azure-hosted app to the WCF service for database access.

The main difference between Azure Storage Queue and the Azure Service Bus Queue is given below:

There can be 2 possible causes:

• Client-side causes:
  • The application might have been redeployed.
  • The application might have just performed a scaling operation.
  • The client-side networking layer has been changed.
  • There might be transient errors in the client or the network between the client and the server.
  • Another possible reason could be the bandwidth threshold limits have been crossed.
• Server-side causes:
  • It might occur if the Azure Redis Cache service itself might undergo a failover from the primary to the secondary node.
  • The server instance where the cache was deployed might have undergone patching or maintenance.