A parks department adopts email and collaboration as a complete vendor-hosted application with no infrastructure to manage. A board member labels the purchase Infrastructure as a Service. Which service model is actually in use?
Select an answer to reveal the explanation.
Short Explanation
Calling a finished mailbox suite IaaS is like calling a restaurant meal a kitchen lease. When parks just logs in and uses email with no servers to babysit, that is SaaS. IaaS would mean they still cook on rented stoves they manage themselves.
Full Explanation
Software as a Service delivers a complete, provider-hosted application that customers consume through a client interface without managing servers, operating systems, or application code. When a parks department adopts vendor-hosted email and collaboration with no infrastructure to operate, the engagement is SaaS regardless of how a board member labels the purchase. Calling the suite Infrastructure as a Service is incorrect because IaaS would expose virtual machines and guest OS administration that parks staff explicitly do not manage. Platform as a Service would mean the department still builds and deploys the mail stack onto a managed runtime, which is not how turnkey collaboration suites work. Hybrid bare metal incorrectly implies on-premises mailbox servers are mandatory for collaboration, which contradicts a fully vendor-hosted adoption. Exam caveat: mislabeling SaaS as IaaS is a common Cloud+ trap that leads auditors and finance teams to expect customer OS patching that will never exist on a SaaS mailbox. Operational check: update the parks procurement and security plan to reflect SaaS shared responsibility—identity federation, mailbox retention, DLP, and acceptable-use controls—while confirming the vendor, not parks sysadmins, patches the mail platform.