Developers deploy their own application code. The provider runs the runtime and the operating system under it, and the developers do not patch that operating system. Which cloud model is that?
Select an answer to reveal the explanation.
Short Explanation
The developers bring the recipe, and the provider keeps the kitchen and the stove. That split is the platform as a service you are buying. Renting the whole kitchen to maintain yourself, eating a finished meal, or using a rack down the hall does not match a provider-run runtime.
Full Explanation
Platform as a service lets the customer deploy application code onto a runtime and operating system the provider maintains. The developers bring code and do not patch the operating system, which is this model. Infrastructure as a service hands over machines, and the customer patches the guest operating system. These developers are not doing that patching, so it is not infrastructure as a service. Software as a service is a finished application. Developers who deploy their own code are not simply using someone else's finished app. A private rack in their office would be equipment they house themselves. The stem puts the runtime with the provider, not in a rack they patch. Exam caveat: the provider's runtime still has limits on which languages and which services it supports. Bringing code does not mean any binary will run. Operational check: deploy a test build, confirm the provider applied the operating-system patches, and confirm the developers did not have to log into a guest to do it.