Microsoft Certified: Azure Fundamentals (AZ-900) 2026 – 400 Free Practice Questions to Pass the Exam

The statement is false because locks in Azure are designed to prevent accidental deletion or modification of resources, and they take precedence over role-based access control (RBAC) roles. While RBAC enables you to assign permissions to users or groups to manage Azure resources, locks provide an additional layer of protection that can't be bypassed by permissions granted through RBAC.

When a resource is locked, even users with RBAC roles that typically allow for deletion or modification cannot perform those actions, ensuring that specific resources remain unchanged despite the roles assigned. This is critical for maintaining the integrity and availability of important resources within Azure.

It’s important to understand that while RBAC plays a significant role in resource management by defining what actions users can perform, locks serve a higher purpose when it comes to safeguarding resources from unwanted changes or deletions, thus emphasizing the importance of implementing both RBAC and locks strategically in Azure environments.