The answer is physical network security. Under the shared responsibility model, the cloud provider is always responsible for the security OF the cloud, which includes all physical controls like data center perimeter protection, hardware surveillance, and network infrastructure at the provider’s edge. This is because the customer cannot physically access or manage the provider’s data centers, so encryption at rest and in transit—while a customer concern—is actually a shared responsibility where the customer manages keys and configurations, while the provider secures the underlying physical network. On the AZ-900 exam, this question tests your ability to distinguish between security OF the cloud (provider) and security IN the cloud (customer). A common trap is assuming the provider handles all encryption; remember, the provider owns the physical layer, not your data’s encryption settings. Memory tip: think “provider protects the box, customer protects what’s inside the box.”
AZ-900 Describe cloud concepts Practice Question
This AZ-900 practice question tests your understanding of describe cloud concepts. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A financial services company is evaluating a public cloud provider. They are concerned about the shared responsibility model for security. The company must ensure that their customer data is encrypted at rest and in transit. Under the shared responsibility model, which security control is the cloud provider typically responsible for?
Why wrong: Encryption at rest is generally the customer's responsibility unless using platform-managed keys where the provider may manage the keys, but the customer must configure it.
B
Patching virtual machines
Why wrong: Patching VMs is the customer's responsibility in IaaS; the provider patches the host, not the VM.
C
Physical network security
The cloud provider is responsible for the security of the physical network, including firewalls and infrastructure against physical threats.
D
Managing customer access policies
Why wrong: Access policies are managed by the customer to control who can access resources.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Physical network security
Under the shared responsibility model, the cloud provider is responsible for the security OF the cloud, which includes physical network security such as protecting the data center perimeter, network infrastructure, and hardware. This is correct because physical security controls (e.g., access badges, surveillance, and network firewalls at the provider's edge) are entirely the provider's domain and cannot be delegated to the customer.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Encrypting customer data at rest
Why it's wrong here
Encryption at rest is generally the customer's responsibility unless using platform-managed keys where the provider may manage the keys, but the customer must configure it.
✗
Patching virtual machines
Why it's wrong here
Patching VMs is the customer's responsibility in IaaS; the provider patches the host, not the VM.
✓
Physical network security
Why this is correct
The cloud provider is responsible for the security of the physical network, including firewalls and infrastructure against physical threats.
Related concept
Read the scenario before looking for a memorised answer.
✗
Managing customer access policies
Why it's wrong here
Access policies are managed by the customer to control who can access resources.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'encryption at rest' (which is a shared or customer responsibility depending on key management) with physical security, leading them to choose A, but the provider's inherent responsibility is always the physical infrastructure, not the customer's data encryption.
Detailed technical explanation
How to think about this question
In Azure, the shared responsibility model is delineated by the type of cloud service: for IaaS, the customer manages everything above the hypervisor (OS, apps, data), while the provider secures the physical host, network, and datacenter. For PaaS, the provider also manages the runtime and middleware, but customer data encryption and access policies remain customer-controlled. This distinction is codified in the Microsoft Service Trust Portal and the Azure Security Benchmark, where physical security controls like datacenter access logs and network perimeter firewalls are audited under SOC 2 and ISO 27001.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-900 question in full detail.
Describe cloud concepts — This question tests Describe cloud concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Physical network security — Under the shared responsibility model, the cloud provider is responsible for the security OF the cloud, which includes physical network security such as protecting the data center perimeter, network infrastructure, and hardware. This is correct because physical security controls (e.g., access badges, surveillance, and network firewalls at the provider's edge) are entirely the provider's domain and cannot be delegated to the customer.
What should I do if I get this AZ-900 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-900 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.