Implementing 70-533 - Objective 1 App Service Apps (15-20%)
Deploy Web Apps
- App_Data/jobs/continuous
- App_Data/jobs/triggered
- Web jobs can be uploaded as zip files but must be < 100mb
- Powershell New-AzureWebSite CarsToGo -Slot Test creates a deployemnt slot named Test, use Publish-AzureWebSiteProject -Name -Slot Test to publish to an existing slot
- Set-AzureResource to set propoerties on Azure resources
- New-AzureResource allows you to create a new resource but does not allow you to update existing resources
- A Standard pricing tier must be used to have a deployment slot. Basic plans do not allow deployment slots
- Powershell can be used to create resource groups and deploy new versions
- Web Deploy will just let you deploy a new version of the code but not create the RG
- Clone App can be used to recreate an app in another App Service Plan in a different region
- Azure Blob storage is used by ARM template deployment
- AzCopy utility is used when building an ARM template in Visual Studio
Configure Web Apps
- Basic plans allow the hosting of up to 10 web apps with custom domains
- SSL certificates need to be converted to .pfx format before uploaded to Azure
- Publish-WebApplication -Configuration parameter can specify a JSON file with resource configuration
- Use CPU metrics to auto scale your instance count
Configure diagnostics, monitoring, and analytics
- Get-AzureWebSiteLog command produces a continuous stream of log data for viewing but you can not download locally
- Save-AzureWebSiteLog command is used to gather Azure logs and download them locally
- Monitoring endpoints allow you to monitor your web app requests from test locations you specify
- Too Many Requests rule displays Not active means metric has not exceeded its threshold within the evaluation window
- Use Uptime to monitor availabitliy of a Web App
- Requests metric shows average requests to a Web App in a specific timeframe
Configure Web Apps for scale and resilience
- Standard mode can auto-scale while Basic can not
- Only standard mode supports auto scaling, basic and shared do not
- Traffic manager is used to distribute web app traffic across multiple geographic locations based on web app load
- Auto scaling is used to increase the number of instances
- Scale by none allows the web app to scale exactly to the number of instances that you specify
- Priority traffic routing is used to support DR scenarios
- Performamce traffic routing will allow traffic to go to the closest endpoint
- Weighted traffic distributes traffic evenly between endpoints
No comments:
Post a Comment