IT maps three workloads: a custom GIS web app on a managed app platform, citywide email from a vendor suite, and a legacy plotter server that needs a specific OS on a VM. Which mapping is correct?
Select an answer to reveal the explanation.
Short Explanation
Mix and match is normal — GIS code on PaaS, mailbox suite as SaaS, picky plotter OS on IaaS. Azure is not a one-flavor-only cafeteria. Match each municipal workload to the service type that fits how much you build versus how much you consume.
Full Explanation
Cloud service types are chosen per workload. A custom GIS app on a managed application platform aligns with PaaS; vendor email is a SaaS productivity use case; a legacy plotter that needs a specific OS on a VM aligns with IaaS. Azure customers commonly combine IaaS, PaaS, and SaaS rather than forcing every system into one model.