A company is migrating its operations to Azure. They deploy virtual machines for a legacy reporting tool, use Azure SQL Database for their transactional database, and adopt Microsoft 365 for corporate email. The IT director wants to clarify the boundaries of the Shared Responsibility Model. Match each administrative task to the correct classification of responsibility under its respective cloud service model.
- Updating the guest operating system for the legacy reporting tool running on Azure Virtual MachinesCustomer responsibility in the Infrastructure as a Service (IaaS) model
- Securing the physical hardware and datacenter hosting the transactional database in Azure SQL DatabaseMicrosoft responsibility in the Platform as a Service (PaaS) model
- Managing user identity accounts and access permissions within Microsoft 365Customer responsibility in the Software as a Service (SaaS) model
Answer
Updating the guest operating system on Azure Virtual Machines matches Customer responsibility under IaaS. Securing the physical hardware for Azure SQL Database matches Microsoft responsibility under PaaS. Managing user accounts in Microsoft 365 matches Customer responsibility under SaaS.
The correct pairings align the administrative tasks with the correct responsibility models. Guest OS patching under IaaS belongs to the customer; physical infrastructure security under PaaS belongs to Microsoft; and identity management under SaaS remains the customer's responsibility.
Step-by-Step Solution
Key Concept
Under the Microsoft Shared Responsibility Model, responsibility for security tasks shifts between the customer and Microsoft depending on whether the service is classified as IaaS, PaaS, or SaaS. However, physical security is always Microsoft's responsibility, and accounts, identities, and data are always the customer's responsibility.
Estimated Time:1m 30s