Question

Difficulty: EasyResource Locks

An organization needs to prevent the accidental deletion of a production database account in Azure. However, administrators must still be able to modify the database configuration settings and scale its throughput as needed. Which resource lock should be applied to meet these requirements?

  1. A
    A ReadOnly lock
  2. A CanNotDelete lockAnswer
  3. C
    A Reader role assignment using Azure role-based access control (Azure RBAC)
  4. D
    An Azure Policy deny assignment

Answer

A CanNotDelete lock
A CanNotDelete lock blocks the deletion of a resource, but allows users to read and modify its configuration. This satisfies the requirement to protect the database from deletion while allowing administrators to modify settings and scale throughput.

Step-by-Step Solution

1
Analyze the requirements to determine the allowed and blocked actions.
Deletion must be blocked, but modifications and updates (such as scaling throughput) must be permitted.
This helps determine the specific lock behavior needed.
2
Evaluate the difference between Azure resource lock types.
A ReadOnly lock blocks both modifications and deletion, whereas a CanNotDelete lock only blocks deletion and allows modifications.
This ensures the selected lock type does not disrupt normal administrative tasks.
3
Select the lock type that permits updates but denies deletion.
A CanNotDelete lock satisfies all constraints of the scenario.
It successfully prevents accidental deletion while leaving configuration and scaling controls active.

Key Concept

Azure Resource Locks prevent accidental deletion or modification of resources. A CanNotDelete lock allows read and update operations but blocks deletion, whereas a ReadOnly lock blocks both modifications and deletion.
Estimated Time:45s
Rate this question