Implement a secure environment →hardMultiple ChoiceObjective-mapped

DP-300 Implement a secure environment Practice Question

Exhibit

Refer to the exhibit.

```json
{
  "properties": {
    "state": "Enabled",
    "storageEndpoint": "https://storagesample.blob.core.windows.net",
    "storageAccountAccessKey": null,
    "retentionDays": 90,
    "auditActionsAndGroups": [
      "SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP",
      "FAILED_DATABASE_AUTHENTICATION_GROUP"
    ],
    "storageAccountSubscriptionId": "00000000-0000-0000-0000-000000000000",
    "isStorageSecondaryKeyInUse": false,
    "queueDelayTime": 0
  }
}
```

Refer to the exhibit. You are troubleshooting an Azure SQL Database auditing configuration. The exhibit shows the blob auditing policy. The storage account access key is null, and the subscription ID is all zeros. What is the most likely issue?

⚠ Common exam trap

Test-takers frequently assume managed identity is automatically used when the access key is null, but in reality, managed identity must be explicitly configured and granted permissions, and the exhibit shows no such configuration.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Auditing will fail because the storage account access key is null.

The exhibit shows that the storage account access key is null, which means Azure SQL Database cannot authenticate to the storage account using the access key. Without a valid access key or a configured managed identity, blob auditing will fail because the database cannot write audit logs to the specified storage container. Option C is correct because a null access key directly prevents auditing from functioning when no alternative authentication method is configured.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Auditing will fall back to Log Analytics workspace.
Why it's wrong here
There is no fallback; if blob auditing is misconfigured, it fails silently.
✗
Auditing will work because managed identity is used.
Why it's wrong here
Managed identity is not supported for blob auditing; storage account key or subscription-based access is required.
✓
Auditing will fail because the storage account access key is null.
Why this is correct
Blob auditing requires a storage account key or a valid subscription ID with appropriate permissions; null key indicates misconfiguration.
✗
Auditing will write to the storage account using the system-assigned managed identity.
Why it's wrong here
System-assigned managed identity is not supported for blob auditing; it's only for event hub or Log Analytics.

Go deeper

DP-300 Implement a secure environment Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question