AZ-900 Describe cloud concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  You never need to patch operating systems

  Why it's wrong here

  With Infrastructure as a Service (IaaS), the cloud provider only manages the physical data center and hypervisor; the customer is still responsible for patching and updating the guest operating system and any software on VMs. In PaaS or SaaS this burden shifts largely to the provider, but for IaaS you must apply security patches, configure firewalls, and maintain OS versions. Therefore the claim that 'you never need to patch' is false in an IaaS scenario, and patching remains a key shared responsibility.

• ✓

  Resources can be provisioned in minutes rather than weeks

  Why this is correct

  One of the core benefits of cloud computing is agility: virtual machines, databases, and other services can be deployed in minutes via self-service portals or APIs like Azure Resource Manager templates, whereas on-premises procurement could take weeks or months due to hardware delivery and setup. This rapid provisioning also enables scaling out and tearing down resources to match demand, directly improving time-to-market and operational responsiveness. This is exactly the agility advantage being highlighted in the answer.

• ✗

  You own the physical hardware

  Why it's wrong here

  In the cloud, the provider owns the physical hardware—servers, storage disks, networking switches, and the data center facility itself—and is responsible for hardware maintenance and replacement. Customers consume virtualized compute and storage on a pay-as-you-go basis, avoiding capital expenditure and hardware lifecycle management. Therefore, claiming you own the physical hardware contradicts the core rental model of cloud computing, where you only control the software and virtual resources you deploy.

• ✗

  All data is automatically encrypted at rest

  Why it's wrong here

  Azure provides encryption at rest through technologies like Storage Service Encryption and Azure Disk Encryption, but it is not automatically applied to every service or data object without configuration. Some services have encryption enabled by default, but many require the customer to explicitly enable it, and certain workloads need customer-managed keys for compliance. Furthermore, automatic encryption at rest is not the agility benefit described in the correct answer; that is a security feature, not a provisioning speed advantage.