On IaaS the city installed and patched IIS itself; on Azure App Service the team deploys application code without managing that web-server OS. What does the App Service approach illustrate?
Select an answer to reveal the explanation.
Short Explanation
Building IIS by hand is IaaS homework; deploying code to App Service is PaaS letting the platform own that web-server OS layer. Same app idea, different chore list. That contrast is the whole teaching point.
Full Explanation
Azure App Service illustrates Platform as a Service: the team deploys application code without managing the web-server operating system, whereas IaaS left IIS install and patching with the city. PaaS removes that OS and web-server administration layer compared with IaaS while still allowing custom application code—the contrast is the whole teaching point. Same application intent, different chore list and responsibility boundary. SaaS that forbids any custom application code misstates both SaaS and what App Service is for; App Service hosts your app, it is not a finished HR suite. IaaS does not remove guest OS duties—claiming it always does contradicts the IaaS model this item uses as the baseline. Private cloud is not a prerequisite for running a web app on a public PaaS platform. Exam caveat: moving from IaaS IIS to App Service changes responsibility boundaries; application configuration, identity integration, and code quality remain customer-owned. Operational check: compare the old IaaS IIS patch checklist with the App Service deployment checklist and retire OS tasks that no longer apply while retaining app security and configuration reviews. Use the IaaS-versus-App-Service chore comparison in training so staff can name PaaS when OS administration disappears from the web-hosting checklist.