Refer to the exhibit. A KQL query is run against Azure Storage logs. The result shows a high number of 404 errors for 'GetBlob' operations. What is the most likely cause?
404 indicates resource not found.
Why this answer
A 404 (Not Found) error for 'GetBlob' operations in Azure Storage logs specifically indicates that the requested blob resource does not exist at the specified URI. This is distinct from authorization failures (which return 403) or throttling (which returns 503). The high number of 404 errors suggests the client is attempting to retrieve blobs that have been deleted, never created, or are referenced with an incorrect path.
Exam trap
The trap here is that candidates confuse 404 (Not Found) with 403 (Forbidden), assuming that a missing blob is caused by a permissions problem, but Azure strictly differentiates these status codes based on whether the resource exists versus whether access is denied.
How to eliminate wrong answers
Option A is wrong because permission issues (e.g., missing RBAC role or SAS token) result in a 403 (Forbidden) error, not 404. Option B is wrong because throttling by the storage account returns a 503 (Server Busy) or 429 (Too Many Requests) status code, not 404. Option D is wrong because an incorrect authentication method (e.g., using an invalid key or expired SAS) also leads to a 403 (Forbidden) error, as the request is authenticated but not authorized, or a 401 (Unauthorized) if the authentication header is missing or malformed.