A financial company is migrating its operations to Azure. They deploy virtual machines for legacy accounting software, use Azure SQL Database for their transactional database, and adopt Microsoft 365 for employee collaboration. Under the Microsoft Azure Shared Responsibility Model, match each operational management task to its corresponding responsibility boundary.
- Patching and updating the guest operating system on the accounting virtual machinesCustomer responsibility in an Infrastructure as a Service (IaaS) deployment
- Configuring firewall rules and database user access controls for the Azure SQL DatabaseCustomer responsibility in a Platform as a Service (PaaS) deployment
- Securing the physical datacenters and maintaining the physical hostsMicrosoft responsibility across IaaS, PaaS, and SaaS deployments
- Classifying corporate files and managing user access rights within Microsoft 365Customer responsibility in a Software as a Service (SaaS) deployment
Cevap
The correct mapping pairs virtual machine guest operating system patching to IaaS customer responsibility; SQL database firewall and access settings to PaaS customer responsibility; physical host and datacenter security to Microsoft responsibility; and Microsoft 365 data classification and user access to SaaS customer responsibility.
Under the Azure Shared Responsibility Model, ownership transitions between the customer and Microsoft depending on the service model type. Guest operating system patching belongs to the customer in IaaS (virtual machines). Configuring network firewall rules and user permissions for Azure SQL Database belongs to the customer in PaaS. Physical security of datacenters remains with Microsoft across all models. Data classification and identity management remain a customer responsibility in SaaS (Microsoft 365).
Adım Adım Çözüm
Anahtar Kavram
Shared Responsibility Model
Tahmini Süre:1m 30s