Resource locks (delete, read-only) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Effect of Delete Lock on Resource Deletion

You have applied a Delete lock on an Azure Storage Account. What happens if you try to delete this storage account?

A The resource is deleted but all its data is retained for 30 days automatically.

B The deletion proceeds normally without any warnings or errors.

C The deletion is blocked and an error is returned preventing the resource from being deleted.

D The deletion is allowed but a notification email is sent to the subscription owner.

💡 Hint

Think about what a Delete lock is designed to prevent.

A Delete lock prevents the resource from being deleted. Any attempt to delete the resource will fail with an error, protecting it from accidental deletion.

❓ service_behavior

intermediate

Effect of Read-Only Lock on Resource Modification

You apply a Read-Only lock on an Azure Virtual Machine. Which of the following actions will be blocked?

A Only deleting the VM will be blocked; starting and stopping are allowed.

B Modifying the VM's configuration or deleting it will be blocked, but starting and stopping are allowed.

C No actions are blocked; the lock only prevents reading the VM's properties.

D Starting, stopping, or deleting the VM will be blocked.

💡 Hint

Consider what Read-Only lock means for resource changes.

A Read-Only lock prevents any modifications or deletions of the resource. However, operations like starting or stopping the VM, which do not change the resource's configuration, are allowed.

❓ Architecture

advanced

Best Practice for Protecting Critical Resources

You manage a production Azure environment with critical resources. Which lock strategy is best to prevent accidental deletion but still allow necessary updates?

A Apply a <strong>Delete</strong> lock on critical resources to block deletion but allow updates.

B Apply a <strong>Read-Only</strong> lock on critical resources to block all changes including updates.

C Do not apply any locks; rely on role-based access control (RBAC) only.

D Apply both <strong>Delete</strong> and <strong>Read-Only</strong> locks on all resources.

💡 Hint

Think about allowing updates but preventing deletion.

A Delete lock prevents accidental deletion but allows updates and modifications. A Read-Only lock blocks all changes, which may be too restrictive for production resources that need updates.

❓ security

advanced

Impact of Locks on Role-Based Access Control (RBAC)

If a user has Owner role on a resource but a Read-Only lock is applied, what is the effective permission for that user?

A The user can read the resource but cannot modify or delete it due to the lock.

B The user can delete the resource but cannot modify it.

C The user cannot access the resource at all because the lock overrides RBAC.

D The user can perform all Owner actions ignoring the lock.

💡 Hint

Consider how locks and RBAC permissions interact.

Resource locks apply on top of RBAC permissions. Even if a user has Owner role, a Read-Only lock prevents modifications and deletions, effectively limiting the user's actions.

🧠 Conceptual

expert

Lock Scope and Inheritance Behavior

You apply a Delete lock at the resource group level. Which statement is true about the lock's effect on resources inside that group?

A The lock applies only to resources tagged with a specific tag matching the resource group.

B The lock only applies to the resource group itself, not to individual resources inside it.

C The lock applies only to new resources created after the lock was applied.

D The lock applies to all resources within the resource group, preventing their deletion unless the lock is removed.

💡 Hint

Think about how locks propagate in Azure hierarchy.

Locks applied at a parent scope like a resource group inherit down to all child resources, preventing deletion of any resource inside until the lock is removed.