Staff reach a payroll application in a browser. The vendor patches the application and its operating system. The company does not deploy its own code. Which cloud model is this?
Select an answer to reveal the explanation.
Short Explanation
You are eating a meal someone else cooked, in their kitchen. That finished application is software as a service. If you were maintaining the stoves, or bringing your own recipe, it would be a different service, and a hypervisor in your own closet is not this vendor's website.
Full Explanation
Software as a service delivers a complete application. The customer uses it, often in a browser, and the vendor patches the application and the system under it. The company deploys no code, which matches that split. Infrastructure as a service provides machines, and the customer patches the guest operating system. That is more work than this company keeps. Platform as a service lets the customer deploy its own application onto the vendor's runtime. This company is not deploying payroll code. A type 1 hypervisor on the company's own server is on-premises virtualization, not the vendor-run payroll site in the browser. Exam caveat: a vendor's marketing name does not decide the model. Who patches the application does. Operational check: list who applies payroll updates. If the vendor does and the staff only sign in, keep the design classified as software as a service. Ask who installs the next payroll update. If the answer is the vendor and staff only sign in, the model stays software as a service.