PaaS for Web Apps Without Infrastructure Management

What Software as a Service (SaaS) is

Software as a Service (SaaS) delivers complete, fully functional end-user applications over the internet on a subscription basis. The cloud provider manages the entire technology stack—from physical hardware and operating systems to application code and runtime components. Common examples include Microsoft 365, Microsoft Dynamics 365, and web-based email solutions.

Why it doesn't meet the requirement

• No custom code development: SaaS delivers turnkey applications intended for end users rather than a hosting framework for deploying custom application source code and REST APIs.
• Limited development control: Developers cannot build custom backend logic or manage custom software development lifecycles inside a standard SaaS application.

Key characteristics and limitations

• End-user focus: Built for immediate consumption by end users rather than developers building bespoke software.
• Zero infrastructure management: Users have no visibility or control over underlying servers, middleware, or application codebase.
• Subscription-based pricing: Typically billed on a per-user, per-month basis.

This answer would be correct if

The organization needed to adopt an existing, ready-to-use business application (such as an email platform or CRM) without writing any custom software code.

What Infrastructure as a Service (IaaS) is

Infrastructure as a Service (IaaS) provides virtualized computing resources over the cloud, including virtual machines, storage disks, and virtual networks. The cloud provider hosts and manages the physical hardware and datacenter facilities, but the customer retains full control over the operating system, middleware, and installed applications.

Why it doesn't meet the requirement

While IaaS can host web applications and APIs, it requires administrative overhead that contradicts the scenario requirements:

• Operating system management: The customer is responsible for installing, configuring, and patching the operating system on virtual machines.
• Web server maintenance: The team would have to manually install and configure web server software such as IIS or NGINX.
• Complex scaling configurations: Implementing automated scaling in IaaS often requires configuring virtual machine scale sets and load balancers manually, introducing administrative complexity.

Key characteristics and limitations

• Maximum configuration control: Allows deep customization of operating system settings and low-level network components.
• Higher operational overhead: Requires dedicated staff for ongoing maintenance, patch management, and backup configurations.
• Self-managed software stack: The customer is responsible for runtime environments, database engines, and web server software.

This answer would be correct if

The scenario required complete administrative control over the underlying operating system, custom kernel extensions, or legacy software that cannot run on a managed cloud platform.

What on-premises infrastructure is

On-premises infrastructure (often referred to as a private datacenter environment) refers to physical hardware, virtualization hosts, networking gear, and storage devices owned, housed, and operated entirely within an organization's private facilities.

Why it doesn't meet the requirement

• Full administrative burden: The organization is completely responsible for purchasing physical hardware, configuring network switches, updating virtualization hypervisors, and managing OS patches.
• High capital expenditure (CapEx): Deploying new capacity requires upfront purchases of servers, storage arrays, and software licensing.
• Complex scaling: Scaling cannot occur natively or on-demand without provisioning additional physical servers and network equipment.

Key characteristics and limitations

• Full physical control: The organization retains direct access and control over physical hardware and data storage.
• High operational costs (OpEx): Requires dedicated IT staff for hardware maintenance, power, cooling, physical security, and disaster recovery.
• Slow deployment cycles: Procuring and provisioning new server hardware can take weeks or months.

This answer would be correct if

The organization had strict regulatory mandates requiring data and workloads to remain on proprietary, physically isolated on-premises hardware.