A library consortium wants to publish a simple custom API for catalog lookups without babysitting servers. Which choice best fits?
Select an answer to reveal the explanation.
Short Explanation
Custom API, no desire to babysit VMs? That is a PaaS pitch. Drop the code on a managed platform and skip the OS chore list that IaaS would hand you.
Full Explanation
PaaS is appropriate when teams want to deploy application code—such as a custom API—without managing virtual machines and guest operating systems. IaaS would add OS management the consortium wants to avoid. SaaS productivity apps like Outlook do not replace a custom API hosting need, and on-premises-only hardware is not required for this scenario.