A company is migrating its operations to Azure and deploying three different workloads: legacy applications on Azure Virtual Machines (IaaS), database workloads on Azure SQL Database (PaaS), and productivity tools on Microsoft 365 (SaaS). To ensure proper governance, the IT team must define operational boundaries. Match each operational task to the correct responsibility classification under the Azure Shared Responsibility Model.
- Patching the guest operating system of the virtual machine running the legacy application (IaaS)Solely the responsibility of the Customer
- Configuring network firewalls and access controls for the database workload (PaaS)Shared responsibility between the Customer and Microsoft
- Securing the physical server hardware and datacenters hosting Microsoft 365 (SaaS)Solely the responsibility of Microsoft
Answer
Patching the guest operating system in IaaS is solely the responsibility of the Customer. Configuring network firewalls in PaaS is a shared responsibility between the Customer and Microsoft. Securing physical server hardware in SaaS is solely the responsibility of Microsoft.
Under the Azure Shared Responsibility Model: 1. Guest OS patching in IaaS is solely the customer's responsibility since they control the virtual machine. 2. Network controls configuration in PaaS is a shared responsibility because the customer manages the resource-level network settings while Microsoft secures the network infrastructure. 3. Physical host and datacenter security is always solely Microsoft's responsibility across all cloud models.
Step-by-Step Solution
Key Concept
The Shared Responsibility Model defines which security and operational tasks are handled by the cloud provider (Microsoft) and which are handled by the customer, varying across IaaS, PaaS, and SaaS deployments.
Estimated Time:1m 30s