Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Customer Data Remains Always a Customer Responsibility
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An enterprise is planning a cloud migration strategy that incorporates multiple service models, including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).
The compliance and security teams need to establish clear operational baselines and identify the tasks that will never shift to the cloud service provider.
According to the shared responsibility model, which responsibility is always retained entirely by the customer across all cloud deployment models?
Explanations
Information and customer data
Information and customer data
What Customer Data Management Is
Information and customer data governance refers to the comprehensive management, classification, protection, and lifecycle handling of digital assets stored in the cloud. Under the shared responsibility model, the customer always maintains complete ownership and ultimate accountability for their data assets.
How It Meets the Scenario Requirements
- Universal retention across models: Regardless of whether a workload is deployed using Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS), the obligation to classify, encrypt, and secure customer data never transfers to Microsoft.
- Regulatory compliance: The customer retains full authority and duty to define access policies, manage data retention schedules, and ensure regulatory alignment across all business environments.
Key Capabilities and Best Practices
- Data classification and labeling: Categorizing sensitive corporate and customer information to apply appropriate governance rules.
- Access control implementation: Configuring role-based permissions and conditional access to prevent unauthorized data exposure.
- Encryption strategy: Managing encryption keys and choosing appropriate encryption methods for data at rest and data in transit.
- Backup and lifecycle management: Setting up data lifecycle policies, retention durations, and disaster recovery workflows.
Why This Is Optimal
The shared responsibility model guarantees that cloud providers secure the underlying platform and physical facilities, but they have no visibility into the business context or sensitivity of customer files. Maintaining data governance as a dedicated customer responsibility ensures that the organization maintains strict sovereign control over its critical digital assets.
Operating system installation and patching
Operating system installation and patching
What Operating System Management Is
Operating system (OS) management involves installing, configuring, hardening, and applying routine security updates and patches to the underlying OS that runs an application or service.
Why It Doesn't Meet the Requirement
Operating system management does not remain solely with the customer across all cloud models. While the customer is responsible for configuring and patching the OS in Infrastructure as a Service (IaaS) (such as Azure Virtual Machines), the cloud provider completely assumes this responsibility in Platform as a Service (PaaS) (such as Azure App Service) and Software as a Service (SaaS) environments.
Key Characteristics and Limitations
- Service-model dependent: OS patching shifts entirely to the cloud provider when moving from IaaS to PaaS or SaaS.
- Administrative overhead: Managing the operating system requires administrative access, update schedules, and vulnerability monitoring in IaaS.
- Abstracted in managed services: In PaaS and SaaS offerings, the underlying operating system is fully abstracted and inaccessible to the customer.
This Answer Would Be Correct If
The scenario specifically asked which compute maintenance responsibility the customer manages when deploying Infrastructure as a Service (IaaS) virtual machines.
Physical datacenter access control
Physical datacenter access control
What Physical Datacenter Security Is
Physical datacenter access control includes the physical safeguards, security guards, biometric access mechanisms, surveillance cameras, and perimeter barriers that protect the buildings housing cloud server hardware.
Why It Doesn't Meet the Requirement
In public cloud computing, physical datacenter security is the sole responsibility of the cloud provider (Microsoft) across all service models (IaaS, PaaS, and SaaS). The customer has no physical access to the provider's server facilities and bears no responsibility for managing physical access controls or environmental systems.
Key Characteristics and Limitations
- Cloud provider obligation: Microsoft secures physical building access, power redundancy, and climate control across all regions.
- Zero customer overhead: Cloud consumers do not purchase real estate, employ physical security personnel, or maintain facility hardware.
- Universal across cloud models: Unlike software layers that vary by model, physical facilities are always managed by the cloud vendor.
This Answer Would Be Correct If
The scenario focused exclusively on traditional on-premises datacenters, where the customer owns the physical facility and is responsible for physical security.
Physical host hardware maintenance
Physical host hardware maintenance
What Physical Host Hardware Maintenance Is
Physical host hardware maintenance entails deploying physical rack servers, replacing failed solid-state drives or memory modules, configuring hypervisors, and managing physical network cabling within the cloud infrastructure.
Why It Doesn't Meet the Requirement
Physical host and virtualization layer maintenance is always handled entirely by Microsoft in all public cloud models (IaaS, PaaS, and SaaS). The customer never manages physical server components or hardware repair cycles in the cloud.
Key Characteristics and Limitations
- Provider-managed infrastructure: The cloud vendor monitors hardware health, handles server replacements, and updates firmware.
- Virtualization abstraction: Cloud consumers interact only with virtualized resources, platform services, or software interfaces rather than bare-metal hardware.
- High availability support: Cloud vendors maintain underlying physical host redundancy to deliver guaranteed service-level agreements (SLAs).
This Answer Would Be Correct If
The organization were operating a private on-premises datacenter where internal IT staff must purchase, mount, and repair server hardware.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Shared Responsibility Model
Describe the shared responsibility model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model Physical Security
Describe the shared responsibility model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
PaaS Shared Responsibility Model
Describe the shared responsibility model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model Customer-Only Responsibilities
Describe the shared responsibility model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model IaaS
Describe the shared responsibility model
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated