A company is migrating its operations to Microsoft Azure. To ensure proper administration, the IT team needs to map specific tasks to their correct ownership classification under the Azure Shared Responsibility Model. How should the team pair each administrative task with its corresponding responsibility classification?
- Patching the guest operating system for an Azure Virtual Machine (IaaS)A responsibility that remains solely with the customer
- Upgrading the database engine software for Azure SQL Database (PaaS)A responsibility shifted to Microsoft
- Configuring identity and access management for Microsoft 365 (SaaS)A customer responsibility even in a fully managed SaaS solution
Cevap
Patching the guest operating system for an Azure Virtual Machine (IaaS) matches with a responsibility that remains solely with the customer. Upgrading the database engine software for Azure SQL Database (PaaS) matches with a responsibility shifted to Microsoft. Configuring identity and access management for Microsoft 365 (SaaS) matches with a customer responsibility even in a fully managed SaaS solution.
Patching the guest operating system of an Azure Virtual Machine is a customer responsibility because IaaS leaves OS control to the user. Upgrading database engine software for Azure SQL Database is Microsoft's responsibility since PaaS abstracts platform management. Configuring identity and access management for Microsoft 365 is the customer's responsibility because user access and identities are always managed by the customer regardless of the cloud model.
Adım Adım Çözüm
Anahtar Kavram
Under the Azure Shared Responsibility Model, physical infrastructure management shifts to Microsoft, while data, endpoints, accounts, and access management always remain the responsibility of the customer. Responsibility for applications, network controls, and operating systems shifts between Microsoft and the customer depending on the service model (IaaS, PaaS, or SaaS).