An enterprise Azure subscription has a `ReadOnly` lock applied at the subscription level. Within this subscription, a resource group named `RG-CoreServices` contains an Azure Cosmos DB account named `cosmos-orders` and an Azure Storage account named `stbackups`. A `CanNotDelete` lock is applied directly to `RG-CoreServices`.
An administrator with the Owner role at the subscription level needs to perform maintenance. Which two of the following actions can the administrator successfully complete without modifying or removing any resource locks? (Select two.)
- Upload a database backup file to an existing blob container in `stbackups` using a pre-existing Shared Access Signature (SAS).Answer
- BCreate a new resource group named `RG-Shared` within the subscription.
- CRetrieve the primary access keys for `cosmos-orders` using the Azure Portal or Azure CLI.
- Delete an existing log file stored as a blob in a container within `stbackups` using direct data plane access.Answer
- EAdd an IP firewall rule to the `cosmos-orders` account to allow traffic from an on-premises network.
Answer
The administrator can upload a database backup file to an existing blob container using a pre-existing Shared Access Signature (SAS), and delete an existing log file stored as a blob using direct data plane access.
The correct options are uploading a backup file and deleting a log file. Both operations are data plane tasks interacting directly with the storage container contents rather than modifying the Azure Resource Manager (ARM) configuration of the resource. Resource locks only restrict control plane operations.
Step-by-Step Solution
Key Concept
Azure Resource Locks restrict control plane operations (such as configuration changes and resource deletion) but do not block data plane operations (such as manipulating data inside a storage account or database). ReadOnly locks also block operations that retrieve keys (like listKeys) because keys grant write access.