Azure Interview Questions

Private clouds are those that are built solely for an individual enterprise. They enable any particular firm to have applications in the cloud while tending to concerns concerning data security and control that is frequently ailing in a public cloud environment. It is otherwise called an internal cloud or enterprise cloud and dwells on the organization’s intranet or hosted data center where the data is protected. Public cloud is utilized as a service through the Internet by the users, while a private cloud, is implemented within specific limits like firewall settings and is overseen and checked by the users dealing with it in an organization.

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. They 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.

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. Furthermore, identification and re-correction activity will be started 99.9 percent of the time when the procedure of a role instance is not running.

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

Redis is an open source, BSD licensed in-memory data structure store, which is commonly used as a database, cache and message broker. Azure Redis Cache is also based on this. 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, and sorted sets with range queries, bitmaps, hyperlog logs and geospatial indexes with radius queries.

It is different from other Azure services as unlike some of the other available services; Azure Redis Cache does not have an MSDN class library reference. This is because each client has its API that makes calls to the Redis cache instance using Redis commands. That is why there is not one centralized class reference on MSDN, and each client maintains its reference documentation.

Each data disk on the VM can be up to 1 TB. However, the number of data disks, which you can use depends on the size of the virtual machine. Azure storage accounts can also provide storage for the operating system disk and any data disks where each disk is a .vhd file stored as a page blob.

Azure Managed Disks are the new and recommended disk storage offerings for use with Azure Virtual Machines for persistent storage of data. A user can use multiple Managed Disks with each VM. Managed Disks offer two types of durable storage options: Premium and Standard Managed Disks.

For configuring with Node.Js, a user can specify the PM2 configuration file or your script file. In case of .NET Core, the user can specify their compiled DLL name. Moreover, in case of Ruby, one can specify the Ruby script that they want to initialize their app with.

Service Fabric enables the user to build applications that comprise micro services. Stateless micro-services (like protocol gateways and web proxies) don’t maintain a mutable state outside a request and its response from the service. Examples of a stateless service include Azure Cloud Services worker roles. Stateful micro-services (like user accounts, databases, devices, shopping carts, and queues) maintain a mutable, authoritative state beyond the request and its response, unlike Stateless Services. Today’s Internet-scale applications comprise a combination of stateless as well as stateful micro-services.

VNet is a representation of your network in the cloud. It logically isolates the instances launched in the cloud, from the rest of the resources of a user.

Scaling by including extra instances is frequently referred to as scaling out. Windows Azure similarly supports scaling up by employing a bigger role instead of more role instances. By adding and expelling role instances to your Windows Azure application while it is running, you can adjust the execution of the application against its running costs. An auto-scaling solution simply diminishes the amount of manual work engaged in dynamically scaling an application.

The companies, which provide the cloud services to businesses, are called Cloud Providers, and one of them is Microsoft Azure. Microsoft Azure is an expanding cloud computing service created by Microsoft for testing, building, managing, and deploying applications and services via a global network of data centers managed by Microsoft. It is basically and widely used for accessing Microsoft’s infrastructure for the cloud by businesses.

The developers, who have a hosting account, can use a Windows Azure portal to submit applications to Windows Azure. A developer can easily access the Windows Azure portal through the Web browser, by signing in with a Windows Live ID to run an application.

Roles are simply servers in layman terms. They are managed and load balanced platforms like service virtual machines, which work together to achieve a common goal. There are three roles, which are implemented in Windows Azure:

• Web Role: It gives a web solution that is completely front-end. This is similar to an ASP.NET application. When it is enabled, Azure gives IIS and required services.
• Worker Role: It gives us solutions to all background service.  It can easily run long activities as well.
• Virtual Machine Role: The virtual machines execute the roles of both, web and worker. The Virtual Machine Roles gives the consumer the ability to modify the virtual machine on which the web and worker roles are running.

Azure Queues provides the user with a solid, diligent messaging between and within the services. It also highlights quite a straightforward rest-based get/peek/put interface. The Azure Storage Queues make use of 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, one can visualize their contents directly from Visual Studio. Moreover, these queues can be purged of their contents, which is especially useful during development and QA efforts.

On the other hand, Bus Queues are part of a more far-reaching Windows Azure messaging framework, which supports queuing. As a rule, Azure Service Bus Queues can 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 is also a great way to reduce costs. However, these Queues are limited to a maximum of 80 GB. Once the user has reached this limit, his or her application will start receiving exceptions.

Virtual machine scale sets are Azure compute resources, which can be used to deploy as well as manage a set of identical VMs. When all the VMs are configured in the same way, scale sets are automatically designed to support true auto-scale, and no pre-provisioning or prearrangement of VMs is required. That is why it is easier to build large-scale services, which target big compute, big data, and containerized workloads.