A water-quality team wants a data science notebook environment managed by the platform so analysts build models without administering servers. Which service type best describes that use case?
Select an answer to reveal the explanation.
Short Explanation
Managed notebooks are a builders' workshop with the landlord handling the building — classic PaaS energy. Analysts bring data and code; the platform keeps the servers out of their way. That is not payroll SaaS and not you-must-patch-the-hypervisor.
Full Explanation
A managed data science notebook environment where analysts build models without administering servers is Platform as a Service. PaaS gives builders tools and runtimes on a managed platform: notebooks, compute sessions, and library environments without owning the underlying OS lifecycle. Water-quality analysts stay focused on data and models while the platform operates the hosting substrate—an AZ-900-aligned example of PaaS for internal builders.
SaaS payroll fails by category; HR billing software is unrelated to notebook-based model development. Claiming IaaS only is required because notebooks always force cities to patch every hypervisor host misunderstands both IaaS customer scope and PaaS—customers do not patch Microsoft's hypervisor hosts, and managed notebook platforms exist specifically to avoid OS ownership. A management group is an organizational hierarchy for subscriptions governance, not a service type that hosts notebook kernels.
Exam caveat: managed notebooks can still process sensitive environmental or citizen-adjacent datasets; platform management of servers does not automatically satisfy data classification, access reviews, or approved-library controls.
Operational check: enforce identity-based access to the notebook workspace, restrict outbound exfiltration paths for raw water-quality datasets, and confirm compute auto-shutdown or quota settings so exploratory sessions do not silently inflate monthly spend.