ISC · Information Systems and Data Management · 9 practice questions
IaaS vs. PaaS vs. SaaS: Who Patches the OS?
Customers patch the guest OS in standard IaaS; providers patch it in PaaS and SaaS. Below: compare who manages each layer and which model preserves OS control.
Try one first
Hint
For each service model (IaaS, PaaS, SaaS), ask who controls the operating system and the application layer, that party generally manages patching and configuration; identity/data responsibilities usually remain with the customer.
Answer B. Under a typical shared-responsibility model, the customer is responsible for software and configurations they run on IaaS VMs, including guest OS patching and VM-level network/security-group settings. PaaS providers manage the platform components they supply, so the provider typically patches the guest OS and DB engine for a managed database service. SaaS vendors manage the application stack (including application-code updates), while customers retain responsibility for their data and logical user/account provisioning.
Why not A: This is tempting because providers manage the physical infrastructure, but it is incorrect: with IaaS the customer controls and must patch the guest OS and configure VM-level network/security-group rules; providers manage the underlying host and hypervisor, not the customer's guest OS or its security groups.
Why not C: This answer assumes customers manage platform and application layers for PaaS and SaaS, but PaaS providers typically manage the OS and the managed DB engine, and SaaS vendors handle application updates. Assigning SaaS logical user provisioning to the provider is also incorrect because customers normally control their users and access settings.
Why not D: This may look plausible because providers manage many platform components, but it incorrectly assigns IaaS network security group configuration and SaaS user provisioning to the cloud provider. Customers typically configure VM-level security groups and manage their SaaS user accounts and identity controls.
Side by side
| IaaS | PaaS | SaaS | |
|---|---|---|---|
| Physical facilities, hosts, and hypervisor | Provider | Provider | Provider |
| Guest OS patching | Customer | Provider | Provider |
| Runtime or database engine patching | Customer | Provider for the managed platform | Provider |
| Business application code updates | Customer | Customer for its deployed application | Provider |
| Data and schema management | Customer | Customer manages data and schemas | Customer manages its application data |
| User provisioning and role assignments | Customer | Customer | Customer |
| Customer-controlled configuration | Customer configures VMs and security groups | Customer configures application or database access | Customer configures settings within the application |
| Guest OS administrator access | Yes; can install OS-level agents and kernel modules | No | No |
| Choose when the requirement is | Keep OS control and accept OS patching duties | Keep custom code control without OS or runtime patching | Use a finished application without maintaining its stack |
Key points
- Remember: Guest OS control comes with guest OS patching responsibility in standard IaaS.
- Classify by who manages each layer, not merely by the presence of virtual machines.
- A required customer-installed kernel module rules out standard PaaS and SaaS.
How the exam traps you
- Assigning IaaS guest OS patching to the provider because it patches the hypervisor. Separate the layers: provider patches the hypervisor; customer patches the guest OS.
- Treating managed database engine patching and schema changes as the same responsibility. In managed PaaS databases, the provider patches the engine; the customer manages schemas and data.
- Assuming SaaS shifts user provisioning and role assignments to the vendor. The provider maintains the application; the customer manages its users and roles.
Question 2
Hint
Focus on which party manages the operating system and middleware, not just where the servers are located.
Answer D. This arrangement is IaaS because the cloud provider is supplying the basic infrastructure components: compute (virtual servers), storage, and networking. Pine still installs and manages the operating system, middleware, application, and data, which is the classic dividing line for IaaS. The fact pattern is about renting infrastructure rather than a managed platform or complete software product.
Why not A: Tempting because the application is in the cloud, but in SaaS the provider manages the full application stack for the customer. Here Pine is responsible for installing and managing the application, so it is not SaaS.
Why not B: Colocation involves the customer placing and typically managing their own physical hardware in a third-party data center. In this scenario the provider supplies virtualized servers, storage, and networking, a cloud IaaS model rather than colocation.
Why not C: PaaS also hosts resources for applications, but the provider typically manages the operating system and middleware platform. Because Pine manages the OS and middleware, the setup fits IaaS rather than PaaS.
Question 3
Hint
Focus on which layers ACME controls. If the customer manages the OS and applications on provisioned VMs while the provider handles hardware and virtualization, which model fits?
Answer C. This is IaaS because the provider supplies and manages the underlying physical infrastructure and virtualization, while the customer provisions VMs and is responsible for the OS, middleware, runtime, and applications. The customer's responsibility for installing and patching the OS and applications and being billed per VM-hour aligns with IaaS.
Why not A: Tempting because the service is cloud-hosted, but SaaS delivers complete, ready-to-use applications managed entirely by the provider; customers do not install or maintain the OS, middleware, or application components as ACME does.
Why not B: PaaS removes OS and runtime management from the customer, providing a managed platform for deploying applications. It's incorrect here because ACME manages the OS, middleware, and databases on provisioned VMs, which a PaaS provider would handle.
Why not D: FaaS is event-driven and customers deploy discrete functions rather than provisioning and managing VMs. Because ACME is creating and maintaining VMs, the scenario does not describe FaaS/serverless.
Question 4
Hint
Focus on which option preserves the company's required OS‑level administrative control (patching and OS logs) while outsourcing physical infrastructure and delivering the needed availability with limited in‑house staff.
Answer C. Public cloud IaaS best balances the firm's constraints: it allows the company to retain OS-level administrative control (meeting the policy and audit-log access requirement) while outsourcing physical infrastructure, geographic redundancy, and managed replication/backups to the provider. Those provider capabilities can help achieve aggressive RTO/RPO targets without the capital and staffing burden of building active-active on‑premises datacenters. SaaS or fully managed hosting (as described) would cede OS control, and on‑premises active-active would impose staffing and cost demands the small IT team cannot reasonably meet.
Why not A: This preserves OS control and can be engineered to meet RTO/RPO, but it requires substantial capital investment and specialized operations staffing, resources the small internal IT team lacks, making it impractical here.
Why not B: SaaS reduces operational burden and often provides strong availability, but it hands control of the OS and underlying platform to the vendor, conflicting with the company's requirement to retain OS-level administrative control and direct access to OS logs for audits.
Why not D: Colocation with a managed host outsources physical operations, but if the provider performs OS patching/management the company surrenders the OS-level administrative control it requires; additionally, matching cloud-like multi‑zone resiliency and rapid RTO/RPO can require similar contractual and design complexity.
Question 5
Hint
Focus on which party manages the hardware layer versus the operating system and applications.
Answer C. IaaS is correct because the provider supplies and manages the underlying physical infrastructure (servers, storage, networking), while the customer retains responsibility for installing, configuring, and updating the operating systems and applications. The key dividing line is who manages the OS and higher layers: in IaaS the customer manages those layers.
Why not A: SaaS delivers a finished application fully managed by the provider, with customers using the software rather than installing or maintaining it. Because the company continues to run and maintain its own applications, the arrangement is not SaaS.
Why not B: PaaS might seem plausible because a provider hosts the environment, but PaaS providers typically manage the operating system and runtime platform so customers focus mainly on deploying applications. Since the company in the scenario still manages its OS, this is not PaaS.
Why not D: Colocation involves the customer owning and maintaining their own servers while renting space, power, and connectivity from a facility provider. Here the provider supplies and maintains the physical servers themselves, which points to IaaS rather than colocation.
Question 6
Hint
Decide which tasks occur at the provider's physical/virtualization layer versus inside the guest VM or application stack.
Answer A. In the standard IaaS model the cloud provider is responsible for the underlying physical infrastructure and virtualization layer (physical hosts, hypervisor) and for data-center physical security and environmental controls. The customer is responsible for the guest OS, applications, data, tenant network configurations, and application-level identity and access management unless it purchases provider-managed services.
Why not B: This option is tempting because the provider supplies the networking fabric, but it fails because tenant-specific network security rules and their configuration are typically the customer's responsibility in IaaS.
Why not C: This distractor tempts candidates who conflate IaaS with managed offerings (PaaS/SaaS). It is incorrect because, under standard IaaS, the customer controls the guest OS and must apply patches unless they buy the provider's optional managed-patching service.
Why not D: Candidates may be lured by the availability of provider IAM services; however, application-level auth and user-account management for customer applications running on VMs remain the customer's duty under IaaS.
Question 7
Hint
Focus on which model relinquishes hardware and hypervisor responsibilities to the provider while still allowing full OS-level (including kernel) control by the customer.
Answer D. IaaS offloads physical servers, data center facilities, and virtualization to the cloud provider while leaving the customer responsible for the operating system and higher layers. That configuration allows the firm to install a kernel-level authentication module and manage OS-level security and patching while avoiding on-premises server and hypervisor management.
Why not A: Tempting because hybrid deployments can preserve OS control for on-premises systems, but incorrect here because hybrid implies the firm must continue managing some physical infrastructure, contradicting its goal to stop managing physical servers and data center facilities entirely.
Why not B: Tempting because PaaS reduces infrastructure and operational burden, but incorrect because PaaS typically abstracts and manages the OS/runtime, preventing the kernel-level installations and direct OS patching the firm requires.
Why not C: Tempting because SaaS eliminates almost all infrastructure and OS responsibilities, but incorrect because SaaS provides no OS access, so the firm could not install or configure a proprietary OS- or kernel-level authentication module.
Question 8
Hint
Focus on who manages the application itself, not just who owns the servers.
Answer A. This arrangement is SaaS because the company is consuming a finished application over the internet while the vendor manages the full technology stack underneath it. The customer does not manage the servers, operating system, or application maintenance. The company's role is limited mainly to data input, configuration, and user access.
Why not B: PaaS provides a managed platform for customers to develop or deploy their own applications. In this case the customer is using a finished payroll application rather than deploying or developing software, so SaaS is the correct classification.
Why not C: IaaS involves vendor-provided servers and storage, but in IaaS the customer typically manages the operating system and applications. Here the vendor also manages the payroll application and OS, so IaaS is not the best fit.
Why not D: Private cloud describes a deployment model (dedicated infrastructure), not the service model. Nothing in the fact pattern indicates the environment is dedicated solely to this company, and the question targets the service model distinction (SaaS/PaaS/IaaS).
Question 9
Hint
First identify which controls are provider-managed versus ABC’s (user-entity) responsibilities; then plan procedures that test each party’s relevant controls rather than assuming the SOC covers everything.
Answer C. CloudCo's SOC 1 report covers the provider-managed layers (physical security, hypervisor, network), but does not cover guest OS, application configuration, or ABC's user-account provisioning. Under the shared-responsibility model, the auditor may rely on the SOC report for provider-controlled areas while designing and performing direct tests of ABC's user-entity controls that are relevant to the audit objective. Combining evaluation of the SOC report with separate testing of the client's controls provides sufficient appropriate evidence about design and operating effectiveness.
Why not A: Tempting because service organization reports provide evidence about the hosting environment, but incorrect: the SOC 1 does not address guest OS or application-level user-access/configuration controls that ABC manages. Relying solely on the SOC would leave a gap in evidence for controls that directly affect the accounting application.
Why not B: Tempting because SOC 2 addresses broader security criteria, but impractical and unnecessary: the auditor cannot require the service organization to produce a different report and the client (ABC), not CloudCo, controls the guest OS and application configuration. The appropriate response is to use the existing SOC for provider layers and test ABC's user-entity controls for application-level responsibilities.
Why not D: Tempting because substantive procedures can detect misstatements, but incorrect given the stated objective to evaluate the design and operating effectiveness of controls. Substantive tests alone would not provide evidence about whether access and change-management controls are designed and operating effectively (for example, to detect unauthorized administrative accounts or improper configuration changes).
Common questions
Who patches the operating system in IaaS, PaaS, and SaaS?
The customer patches the guest OS in standard IaaS. The provider patches the OS in PaaS and SaaS and maintains the underlying physical infrastructure and hypervisor in all three.
Which cloud service model gives the customer OS administrator access?
Standard IaaS preserves guest OS administrator access, including installing OS-level agents and kernel modules. PaaS and SaaS do not provide that control.
What is the difference between PaaS and SaaS responsibility?
In PaaS, the provider maintains the OS and platform while the customer manages its application code or database schemas. In SaaS, the provider also maintains the finished application; the customer still manages users, configuration, and data.
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on IT infrastructure
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.