Cloud service can convey multiple web applications in Azure, characterizing a number of parts to disseminate handling and permit adaptable scaling of your application. A cloud service comprises a minimum of one web part, as well as specialist parts, each with its own particular application documents and design. The fundamental favorable position of cloud service is the capacity to help more complex multilevel structures.
Features |
Microsoft Azure |
Amazon Web Services (AWS) |
Analytics |
Azure Stream Analytics |
Amazon Kinesis |
Backup Options |
Azure Backup |
Amazon Glacier |
Compliance |
Azure Trust Center |
AWS CLoudHSM |
Content Delivery Network (CDN) |
Azure CDN |
Amazon CloudFront |
Data Orchestration |
Azure Data Factory |
AWS Data Pipeline |
Hybrid Cloud Storage |
StorSimple |
AWS Storage Gateway |
Monitoring |
Azure Operational Insights |
Amazon CloudTrail |
NoSQL Database Options |
Azure DocumentDB |
Amazon DynamoDB |
There are three roles in Windows Azure:
· Web Role
· Worker Role
· Virtual Machine Role
Web Role: It gives a web solution that is front-end. This is like an ASP.NET application. While under facilitating, Azure gives IIS and required services.
Worker Role: It gives solutions for background service. It can run long activities.
Virtual Machine Role: The roles of both web and worker are executed on virtual machines. The Virtual Machine Roles give the client the capacity to modify the virtual machine on which the web and worker roles are running.
Windows Azure has three principal segments: Compute, Storage, and Fabric.
A. Windows Azure Compute
Windows Azure gives a code that can be managed by the hosting environment. It gives the calculation benefit through parts. Windows Azure backs three types of roles:
· Web roles utilized for web application programming and upheld by IIS7
· Worker roles utilized for foundation handling of web roles
· Virtual machine (VM) roles utilized for moving windows server applications to Windows Azure in a simple way
B. Windows Azure Storage
It gives four types of storage services:
· Queues for informing between web parts and worker roles
· Tables for storing structural data
· BLOBs (Binary Large Objects) to store contents, records, or vast information
· Windows Azure Drives (VHD) to mount a page BLOB. These can be transferred and downloaded by means of BLOBs
C. Windows Azure AppFabric
AppFabric provides five services:
· Service bus
· Access
· Caching
· Integration
· Composite
Windows Azure Diagnostics empowers you to gather diagnostic data from an application running in Windows Azure. Diagnostic data is used for capacity planning and evaluation.
Azure Queues give a solid, diligent messaging between and within the services. They also highlight a very straightforward rest-based get/put/peek interface.
Bus Queues are part of a more extensive Windows Azure messaging framework that supports queuing.
Windows Azure Table storage service stores a lot of organized information. Windows Azure tables are perfect for putting away organized, non-relational data.
Table: A table is a collection of entities. Tables don’t uphold a blueprint on elements, which implies that a solitary table can contain substances that have distinctive arrangements of properties. A record can contain numerous tables.
Entity: An entity is an arrangement of properties, like a database row. An entity can be up to 1 MB in size.
Properties: A property is a name–value pair. Every entity can incorporate up to 252 properties to store data. Every entity likewise has three system properties that determine a segment key, a row key, and a timestamp.
Scaling by including extra instances is frequently referred to as scaling out. Windows Azure likewise supports scaling up by utilizing bigger role rather than more role instances.
By adding and expelling role instances to our Windows Azure application while it is running, we can adjust the execution of the application against its running costs.
An autoscaling solution reduces the amount of manual work engaged in dynamically scaling an application.
Windows Azure runs and stores the information on Microsoft data centers.
The main features are as follows:
· Websites enable the designers to assemble the sites utilizing ASP.NET, PHP, etc., and send these websites utilizing FTP,GIT, etc.
· SQL database, formally known as Azure database, makes, broadens, and scales the application into the cloud utilizing Microsoft SQL Server.
· This is Microsoft’s Platform as a Service that supports multilevel applications and automated deployment.
Private clouds are those that are constructed solely for an individual enterprise. They enable a firm to have applications in the cloud while tending to concerns with respect to data security and control that is frequently ailing in a public cloud environment.
Private cloud 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.
It is a NoSQL datastore which acknowledges verified calls from inside and outside the Windows Azure cloud. Windows Azure tables are perfect for putting away organized, non-relational data.
Table: A table is an accumulation of elements. Tables don’t implement a pattern on elements, which implies a solitary table can contain substances that have distinctive arrangements of properties. A record can contain numerous tables.
To run an application, a designer gets to the Windows Azure Portal through his/her web program by logging in with a Windows Live ID. The user at that point chooses whether to create a host account for running applications, a storage account for storing data, or both.
Once the designer has a host account, he/she can utilize a Windows Azure Portal to submit applications to Windows Azure.
Azure Fabric is the principal core concept. It gives a service called Azure Fabric Controller. It is called the OS for Azure since it handles/oversees:
· All roles (processing) and resources
· Sending and activating services
· Monitoring the health of all services
· Releasing and allocating resources
· Provisioning VM, terminating, etc.
· Patches get updated for installed OS on VM in the most automated form
A hybrid cloud is a blend of internal and external cloud services, a mix of a private cloud joined with the utilization of public cloud services. This kind of cloud is most appropriate when you need to keep the classified information at your vicinity (private cloud) and consume alternate services from a public cloud.
Explanation: A fault domain is a logical group of underlying hardware that share 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.
Explanation: An update domain is a logical group of 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.
Explanation: A network security group (NSG) contains a list of Access Control List (ACL) rules that allow or deny network traffic to subnets, NICs, or both. NSGs can be associated with either subnets or individual NICs connected to a subnet. When an NSG is associated with a subnet, the ACL rules apply to all the VMs in that subnet. In addition, traffic to an individual NIC can be restricted by associating an NSG directly to a NIC.
Explanation: Yes. A scale set is an implicit availability set with 5 fault domains and 5 update domains. Scale sets of more than 100 VMs span multiple placement groups, which are equivalent to multiple availability sets. An availability set of VMs can exist in the same virtual network as a scale set of VMs. A common configuration is to put control node VMs (which often require unique configuration) in an availability set and put data nodes in the scale set.
Explanation: Technical problems are called break-fix issue, it is an industry term which refers to “work involved in supporting a technology when it fails in the normal course of its function, which requires intervention by a support organization to be restored to working order”.
Explanation: Azure Active Directory is an Identity and Access Management system. It is used to grant access to your employees to specific products and services in your network. For example: Salesforce.com, twitter etc. Azure AD has some in-built support for applications in its gallery which can be added directly.
Explanation: 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.
Explanation: 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, you can opt for a structured training from MJIT!
Explanation: Azure AD gives you an easy and secure way to connect to the web applications you choose. You can access these applications in the same way you access your SaaS apps in Azure AD, no need for a VPN to change your network infrastructure.
Explanation: Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable micro-services. Service Fabric also addresses the significant challenges in developing and managing cloud applications. Developers and administrators can avoid complex infrastructure problems and focus on implementing mission-critical, demanding workloads that are scalable, reliable, and manageable. Service Fabric represents the next-generation middleware platform for building and managing these enterprise-class, tier-1, cloud-scale applications.
Explanation: VNet is a representation of your own network in the cloud. It logically isolates your instances launched in the cloud, from the rest of your resources.
Explanation: 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.
Explanation: Managed Disks eliminates the limits associated with storage accounts. However, the number of managed disks per subscription is limited to 2000 by default.
Explanation: 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 of deleting 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. Its 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.
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, you can opt for a structured training from MJIT!
Explanation: 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.
Explanation: 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.
Explanation: No. If you want your VM to be part of an availability set, you need to create the VM within the set. There currently no way to add a VM to an availability set after it has been created.
Explanation: Usernames can be a maximum of 20 characters in length and cannot end in a period (“.”).
The following usernames are not allowed:
Explanation: Passwords must be 12 – 123 characters in length and meet 3 out of the following 4 complexity requirements:
The following passwords are not allowed:
Explanation: Each data disk can be up to 1 TB. The number of data disks which you can use depends on the size of the virtual machine.
Azure Managed Disks are the new and recommended disk storage offerings for use with Azure Virtual Machines for persistent storage of data. You can use multiple Managed Disks with each Virtual Machine. Managed Disks offer two types of durable storage options: Premium and Standard Managed Disks.
Azure storage accounts can also provide storage for the operating system disk and any data disks. Each disk is a .vhd file stored as a page blob.
# Define a credential object $cred = Get-Credential # Create a virtual machine configuration $vmConfig = New-AzureRmVMConfig -VMName myVM -VMSize Standard_DS2 | ` Set-AzureRmVMOperatingSystem -Windows -ComputerName myVM -Credential $cred | ` Set-AzureRmVMSourceImage -PublisherName MicrosoftWindowsServer -Offer WindowsServer ` -Skus 2016-Datacenter -Version latest | Add-AzureRmVMNetworkInterface -Id $nic.Id
# Create an inbound network security group rule for port 3389 $nsgRuleRDP = New-AzureRmNetworkSecurityRuleConfig -Name myNetworkSecurityGroupRuleRDP -Protocol Tcp ` -Direction Inbound -Priority 1000 -SourceAddressPrefix * -SourcePortRange * -DestinationAddressPrefix * ` -DestinationPortRange 3389 -Access Allow # Create an inbound network security group rule for port 80 $nsgRuleWeb = New-AzureRmNetworkSecurityRuleConfig -Name myNetworkSecurityGroupRuleWWW -Protocol Tcp ` -Direction Inbound -Priority 1001 -SourceAddressPrefix * -SourcePortRange * -DestinationAddressPrefix * ` -DestinationPortRange 80 -Access Allow # Create a network security group $nsg = New-AzureRmNetworkSecurityGroup -ResourceGroupName myResourceGroup -Location EastUS ` -Name myNetworkSecurityGroup -SecurityRules $nsgRuleRDP,$nsgRuleWeb
$storageName = "st" + (Get-Random) New-AzureRmStorageAccount -ResourceGroupName "myResourceGroup" -AccountName $storageName -Location "West US" -SkuName "Standard_LRS" -Kind Storage $accountKey = (Get-AzureRmStorageAccountKey -ResourceGroupName myResourceGroup -Name $storageName).Value[0] $context = New-AzureStorageContext -StorageAccountName $storageName -StorageAccountKey $accountKey New-AzureStorageContainer -Name "templates" -Context $context -Permission Container
az vm create ` --resource-group myResourceGroup ` --name myVM --image win2016datacenter ` --admin-username azureuser ` --admin-password myPassword12
Azure Interview Questions:
Get-AzureRmVM ` -ResourceGroupName myResourceGroup ` -Name myVM ` -Status | Select @{n="Status"; e={$_.Statuses[1].Code}}
Stop-AzureRmVM -ResourceGroupName myResourceGroupVM -Name "myVM" –Force
Explanation: The following are some common reason for a cache disconnect.
v The client application was redeployed.
v The client application performed a scaling operation.
v In the case of Cloud Services or Web Apps, this may be due to auto-scaling.
v The networking layer on the client side changed.
v Transient errors occurred in the client or in the network nodes between the client and the server.
v The bandwidth threshold limits were reached.
v CPU bound operations took too long to complete.
v On the standard cache offering, the Azure Redis Cache service initiated a fail-over from the primary node to the secondary node.
v Azure was patching the instance where the cache was deployed
v This can be for Redis server updates or general VM maintenance.
Explanation: 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.
Explanation: Yes, it does. For private registries, you can update the container by stopping and then re-starting your web app. Alternatively, you can also change or add a dummy application setting to force an update of your container.
Apart from this Azure Interview Questions Blog, if you want to get trained from professionals on this technology, you can opt for a structured training from edureka! Click below to know more.
Explanation: For Node.Js, you specify the PM2 configuration file or your script file. For .NET Core, specify your compiled DLL name. For Ruby, you can specify the Ruby script that you want to initialize your app with.
Explanation:
Pricing will vary based on product types. ISV software charges and Azure infrastructure costs are charged separately through your Azure subscription. Pricing models include:
BYOL Model: Bring-your-own-license. You obtain outside of the Azure Marketplace, the right to access or use the offering and are not charged Azure Marketplace fees for use of the offering in the Azure Marketplace.
Free: Free SKU. Customers are not charged Azure Marketplace fees for use of the offering.
Free Software Trial: Full-featured version of the offer that is promotionally free for a limited period of time. You will not be charged Azure Marketplace fees for use of the offering during a trial period. Upon expiration of the trial period, customers will automatically be charged based on standard rates for use of the offering.
Usage-Based: You are charged or billed based on the extent of your use of the offering. For Virtual Machines Images, you are charged an hourly Azure Marketplace fee. For Data Services, Developer services, and APIs, you are charged per unit of measurement as defined by the offering.
Monthly Fee: You are charged or billed a fixed monthly fee for a subscription to the offering (from the date of subscription start for that particular plan). The monthly fee is not prorated for mid-month cancellations or unused services.
Explanation: “Price” refers to the cost of the Azure Virtual Machine to run the software. “Software price” refers to the cost of the publisher software running on an Azure Virtual Machine. “Total price” refers to the combined total cost of the Azure Virtual Machine and the publisher software running on an Azure Virtual Machine.
Explanation: Service Fabric enables you to build applications that consist of microservices. Stateless microservices (such as protocol gateways and web proxies) do not maintain a mutable state outside a request and its response from the service. Azure Cloud Services worker roles are an example of a stateless service. Stateful microservices (such as user accounts, databases, devices, shopping carts, and queues) maintain a mutable, authoritative state beyond the request and its response. Today’s Internet-scale applications consist of a combination of stateless and stateful microservices.
Explanation: The application partitions are a part of the Active Directory system and having said so, they are directory partitions which are replicated to domain controllers. Usually, domain controllers that are included in the process of directory partitions hold a replica of that directory partition. The attributes and values of application partitions is that you can replicated them to any specific domain controller in a forest, meaning that it could lessen replication traffic. While the domain directory partitions transfer all their data to all of the domains, the application partitions can focus on only one in the domain area. This makes application partitions redundant and more available.
Explanation: Azure has some special regions that you may wish to use when buildingyour applications for compliance or legal purposes. These special regions include:
You need to ensure that virtual machines remain available while migrating to Azure. What would be the appropriate service to use?
a. Traffic Manager
b. Update Domains
c. Express Route
d. Cloud Services
Solution - c) Express Route
a. You administer a website called web game. You’re required to validate and deploy changes made to your website by your development team with minimum downtime
b. Create a new linked resource
c. Create a staging environment for the site
d. Enable remote debugging on the website
Solution - b) Create a staging environment for the site
These scenarios are important on the list of Azure Interview Questions
Your standard tier application is used across the world and uses the Azure website standard tier. It uses a large number of image files. However, this causes the application to load slowly
a. Configure Azure blob storage with a custom domain
b. Configure Azure website Autoscaling to increase instances at high loads
c. Configure Azure CDN to cache all responses from the application’s web endpoint
d. Configure Azure CDN to cache site images and content stored in Azure blob storage
Solution - d)Configure Azure CDN to cache site images and content stored in Azure blob storage
You need to make sure your Virtual Machines are able to communicate securely with each other to ensure security.
Solution - Azure Virtual Network enables Azure resources to communicate with each other, the internet, or on-premises networks securely.
Users can create their own private networks
It provides users with an isolated and highly secure environment for applications
All traffic stays within the Azure network
It allows users to design their own networks
You need to ensure that every time a user logs in, they are not asked to re-enter their passwords as part of the authentication.
a. To enable Microsoft Account authentication
b. Deploy ExpressRoute
c. Set up a VPN between premises and datacenter. Set up an AD domain controller in VM and implement integrated Windows Authentication
d. Configure Azure AD Sync to use single sign-on
Solution - d) Configure Azure AD Sync to use single sign-on
Single sign-on (SSO) is a property of access control of multiple related, but independent software systems. With this property, a user logs in once and gains access to all systems without being prompted to log in again at each of them.
Azure Interview Questions!