70-533 Implementing Microsoft Azure Infrastructure Solutions Exam validates technical expertise in deployment, management, and operations on the Azure platform? The Azure certification exam 70-533 includes such topics as Designing and implementing Azure App Service apps; creating and managing Azure Resource Manager Virtual Machines; designing and implementing a storage strategy; implementing an Azure Active Directory; implementing virtual networks; and designing and deploying ARM templates.
You can download the related 70-533 Implementing Microsoft Azure Infrastructure Solutions study guide for more details about the exam.
Eligible candidates for this exam have:
- Who is experienced in implementing an infrastructure solution in Microsoft Azure
- Candidates have experience implementing and monitoring cloud and hybrid solutions
- Supporting application lifecycle management
Be sure to have hands-on experience!
|Design and implement Azure App Service apps (15–20%)||
|Create and manage Azure Resource Manager Virtual Machines (20–25%)||
|Design and implement a storage strategy (20–25%)||
|Implement an Azure Active Directory (15–20%)||
|Implement virtual networks (10–15%)||
|Design and deploy ARM templates (10–15%)||
Table #1 Domains covered by the 70-533 Azure Infrastructure Solutions Exam
In this article, we are going to explain about the topic that addresses the “Deploy Web Apps” knowledge measured as highlighted in the above exam guide.
Azure App Service
Nowadays, all organization needs to create fast web and mobile apps for any platform or device. Integrate your apps with SaaS solutions, connect with on-premises applications, and automate your business processes without the complexity of building and maintaining the technology infrastructure.
Microsoft Azure offers PaaS services where you can run your apps on fully managed virtual machines (VMs), with your choice of shared VM resources or dedicated VMs.
The Azure App Service includes web and mobile capabilities, new capabilities for automating business processes and hosting cloud APIs. As a single integrated service, App Service lets you compose various components — websites, mobile app backends, RESTful APIs, and business processes — into a single solution.
Azure Web Apps
App Service Web Apps is a fully managed to compute the platform that is optimized for hosting websites and web applications. This platform-as-a-service (PaaS) offering of Microsoft Azure lets you focus on your business logic while Azure takes care of the infrastructure to run and scale your apps.
Azure Web Apps enables you to build and host web applications in the programming language of your choice without managing infrastructure. It offers auto-scaling and high availability, supports both Windows and Linux, and enables automated deployments from GitHub, Visual Studio Team Services, or any Git repository.
The computing resources may be on shared or dedicated virtual machines (VMs), depending on the pricing tier that you choose. Your application code runs in a managed VM that is isolated from other customers.
Your code can be in any language or framework that is supported by Azure App Service, such as ASP.NET, Node.js, Java, PHP, or Python. You can also run scripts that use PowerShell and other scripting languages in a web app.
Several App Types
The Azure App Service offers several app types, each of which is intended to host a specific workload:
|Web Apps||For hosting websites and web applications|
|Mobile Apps||For hosting mobile app backends|
|API Apps||For hosting RESTful APIs|
|Logic Apps||For automating business processes and integrating systems and data across clouds without writing code|
Table #2 Application Types List
Creating a Service Plan
You can create an empty App Service plan from the App Service plan browse experience or as part of app creation.
App Service plans give you the flexibility to allocate specific apps to a given set of resources and further optimize your Azure resource utilization. This way, if you want to save money on your testing environment you can share a plan across multiple apps.
An App Service plan defines:
- Region (West US, East US, etc.):
- Scale count (one, two, three instances, etc.)
- Instance size (Small, Medium, Large)
- SKU (Free, Shared, Basic, Standard, Premium)
Your App Service plan can scale from Free and Shared SKUs to Basic, Standard, and Premium SKUs giving you access to more resources and features along the way. Also, you can move apps between plans if the plans are in the same resource group and geographical region.
You can scale an Azure App Service plan:
- Changing the plan’s pricing tier
- Changing the plan’s instance size
- Changing the plan’s instance count
Deploy Web Apps
An app in Azure App Service can be associated with only one App Service plan at any given time.
Both apps and plans are contained in a resource group. A resource group serves as the life cycle boundary for every resource that’s within it. You can use it to manage all the pieces of an application together.
Because a single resource group can have multiple App Service plans, you can allocate different apps to different physical resources. You can separate resources from development, staging, and production environments, it lets you isolate resources.
When you deploy your web app, web app on Linux, mobile back end, and API app to App Service, you can deploy to a separate deployment slot instead of the default production slot when running in the Standard or Premium App Service plan mode. Deployment slots are live apps with their own hostnames. App content and configurations elements can be swapped between two deployment slots, including the production slot.
App deployment can leverage options that include continuous integration or local source control publishing, Web Deploy, and FTP. The recommended method for production app deployment is deployment slot swap. Deployment slots represent staging and integration environments associated with production apps. Deployment slots can be configured and targeted with web traffic for validation, and traffic can be swapped on demand for deployment to production with no downtime and automated warm-up. The steps of a deployment workflow can be easily automated via release management products such as Visual Studio Release Management.
Deploying your app to App Service is a matter of deploying your code, binaries, content files, and their respective directory structure, to the /site/wwwroot directory in Azure (or the /site/wwwroot/App_Data/Jobs/ directory for WebJobs). App Service supports three different deployment processes:
- Deploy by using Visual Studio
- Deploy by using an FTP client
- Deploy by Kudu (Git/Mercurial or OneDrive/Dropbox)
For automating tasks into your Web Apps you could use WebJobs.
Azure WebJobs provide an effortless way to run scripts or programs as background processes on App Service Web Apps. You can upload and run an executable file such as cmd, bat, exe (.NET), ps1, sh, php, py, js and jar. These programs run as WebJobs on a schedule (CRON) or continuously.
You can run programs or scripts in WebJobs in your Azure App Service web app in three ways: on demand, continuously, or on a schedule. There is no additional cost to use WebJobs.
By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. In the Basic or Standard mode, you can enable Always On to keep the app loaded all the time. If your app runs continuous WebJobs or runs WebJobs triggered using a CRON expression, you should enable Always On, or the web jobs may not run reliably.
Important Points to Remember
- Azure Web Apps enable you to build and host web applications
- You can deploy to a separate deployment slot instead of the default production slot when running in the Standard or Premium Azure App Service plan mode
- You can also run scripts that use PowerShell and other scripting languages in a web app
- You can move apps between plans if the plans are in the same resource group and geographical region
- You can scale a plan: changing plan’s pricing tier, instance size or instance count
- You can publish your web app code using Visual Studio or by using an FTP client
- You can run scripts in WebJobs in your Web App: on demand, continuously, or on a schedule
- There is no additional cost to use WebJobs
Are you preparing for 70-533 Implementing Microsoft Azure Infrastructure Solutions Exam ? Pass in first attempt with Whizlabs Free and Practice Tests.
- Azure App Service: Exam 70-533 - December 7, 2017
- Azure 70-533: Monitoring Web Apps Resources - December 5, 2017
- How to Prepare for Microsoft Azure 70-533 Exam - December 5, 2017
- Top Interview Questions for Azure Solution Architect - December 4, 2017
- AWS: Blue Green Deployment - November 30, 2017