Wednesday, April 19, 2017

Implementing 70-533 - Objective 1 App Service Apps (15-20%)

Deploy Web Apps
  1. App_Data/jobs/continuous
  2. App_Data/jobs/triggered
  3. Web jobs can be uploaded as zip files but must be < 100mb
  4. Powershell New-AzureWebSite CarsToGo -Slot Test creates a deployemnt slot named Test, use Publish-AzureWebSiteProject -Name -Slot Test to publish to an existing slot
  5. Set-AzureResource to set propoerties on Azure resources
  6. New-AzureResource allows you to create a new resource but does not allow you to update existing resources
  7. A Standard pricing tier must be used to have a deployment slot. Basic plans do not allow deployment slots
  8. Powershell can be used to create resource groups and deploy new versions
  9. Web Deploy will just let you deploy a new version of the code but not create the RG
  10. Clone App can be used to recreate an app in another App Service Plan in a different region
  11. Azure Blob storage is used by ARM template deployment
  12. AzCopy utility is used when building an ARM template in Visual Studio

Configure Web Apps
  1. Basic plans allow the hosting of up to 10 web apps with custom domains 
  2. SSL certificates need to be converted to .pfx format before uploaded to Azure 
  3. Publish-WebApplication -Configuration parameter can specify a JSON file with resource configuration 
  4. Use CPU metrics to auto scale your instance count
Configure diagnostics, monitoring, and analytics
  1. Get-AzureWebSiteLog command produces a continuous stream of log data for viewing but you can not download locally
  2. Save-AzureWebSiteLog command is used to gather Azure logs and download them locally
  3. Monitoring endpoints allow you to monitor your web app requests from test locations you specify
  4. Too Many Requests rule displays Not active means metric has not exceeded its threshold within the evaluation window
  5. Use Uptime to monitor availabitliy of a Web App
  6. Requests metric shows average requests to a Web App in a specific timeframe
Configure Web Apps for scale and resilience
  1. Standard mode can auto-scale while Basic can not
  2. Only standard mode supports auto scaling, basic and shared do not
  3. Traffic manager is used to distribute web app traffic across multiple geographic locations based on  web app load
  4. Auto scaling is used to increase the number of instances
  5. Scale by none allows the web app to scale exactly to the number of instances that you specify
  6. Priority traffic routing is used to support DR scenarios
  7. Performamce traffic routing will allow traffic to go to the closest endpoint
  8. Weighted traffic distributes traffic evenly between endpoints

No comments:

Post a Comment