Explore topic-wise InterviewSolutions in Current Affairs.

az vm CREATE ` --resource-group myResourceGroupName ` --name myVM --image win2016datacenter ` --admin-username AzureuserNAME ` --admin-password AzurePASSWORDConclusion

Microsoft Azure has proven itself to be the fastest-growing cloud platform due to its more than 200 service offerings and benefits with pay per use pricing strategy. The revenue generated by Microsoft Azure has been growing constantly from $880 million in 2015 to a whopping $14.6 billion in 2020.

This tremendous growth in Azure has paved the path to many BUSINESSES by creating lots of opportunities in both TECH and non-tech DOMAINS thereby making it a very lucrative domain for building one’s career.

Additional Resources

Learn Azure

Practice Coding

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.

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

• 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 Table Storage and Azure SQL Service is GIVEN below:

IAAS: This stands for “Infrastructure as a Service” which provides a set of capabilities like OS, network connectivities, etc which are at the INFRASTRUCTURAL level and are delivered as pay per use policy. The infrastructure is used for hosting applications. Examples include Azure VM, VNET, etc.

PaaS: PaaS stands for “Platform as a Service” which is mostly about underlying infrastructure abstraction to the developers for enabling quicker development of the applications without the need for worry about hosting management. Examples include Azure web apps, Storage services, cloud services, etc.

SaaS: SaaS stands for “Software as a Service” and are those applications which are delivered using the service delivery model where the applications are simply consumed and used by an organization. These applications are generally mobilized by making the organization pay for their usage or through ads. Examples include applications like OFFICE 365, Gmail, SharePoint Online, and so on.

The following table shows the DIFFERENCE between the On-Prem Service, IaaS, PaaS, and SaaS services. We can observe that as we go right, the level of control the developer or the user has over the APPLICATION reduces.

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.

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.

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.

YES, it can be done by defining a SEPARATE LOAD Balancer Role in Azure.

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.