A civic hackathon uses a managed database service so teams do not patch database servers themselves. At fundamentals depth, which service type does that example represent?
Select an answer to reveal the explanation.
Short Explanation
Managed databases that spare you server patching are classic PaaS-flavored platform services. Teams code against the database; the provider shoulders more of the host care. That is not the same as Outlook-in-a-browser SaaS or DIY VMs.
Full Explanation
Managed database services are commonly taught as Platform as a Service examples: the provider handles much of the database infrastructure and patching while civic hackathon teams use the database platform for their applications. That matches “do not patch database servers themselves” at fundamentals depth and keeps the focus on service-type identification. Teams still design schemas and secure access; they do not run the database host OS as an IaaS chore. Not every database is IaaS on a customer-managed VM—managed offerings exist specifically to reduce that duty. SaaS productivity suites are a different service type; databases can absolutely be platform services and are a standard PaaS teaching example. On-premises tape libraries are not cloud PaaS and do not satisfy a hackathon’s managed database need. Exam caveat: AZ-900 stays at identify/compare depth—no requirement to write client SDKs, tune query plans, or configure advanced database telemetry as the scored skill. Operational check: confirm the hackathon database is a managed offering where host patching ownership sits with the provider, and document remaining customer duties such as firewall rules, credentials, and data design.