Describe considerations for working with non-relational data on Azure →easyMultiple ChoiceObjective-mapped

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

Exhibit

Refer to the exhibit.

```json
{
  "containers": [
    {
      "name": "container1",
      "properties": {
        "publicAccess": "Blob"
      }
    }
  ]
}
```

You have an Azure Blob Storage container configured with the JSON snippet shown in the exhibit. What does the 'publicAccess' setting of 'Blob' allow?

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

✓

Anonymous users can read blobs if they know the blob URL

The 'Blob' level of public access allows anonymous read access to blobs only; container metadata is not accessible. 'Container' level would allow anonymous listing of blobs. 'None' disables public access. 'Storage' is not a valid value.

Answer analysis

Option-by-option breakdown

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

✗
Anonymous users can write blobs
Why it's wrong here
Anonymous public access levels in Azure Blob Storage are strictly read-only. The container's public access setting cannot grant write, update, or delete permissions to unauthenticated users; any write operation requires an authorized identity such as a shared key, a SAS token, or Microsoft Entra ID. Therefore, even with the 'Blob' or 'Container' access level, an anonymous user cannot upload or modify blobs.
✗
No anonymous access is allowed
Why it's wrong here
This statement is false when the container is configured with the 'Blob' public access level. The 'Blob' level explicitly permits anonymous read requests to individual blobs, whereas only a container set to 'Private' (or no public access) would block all anonymous requests. Since the question specifies a container with the Blob level, anonymous access to blob content is allowed, so 'no anonymous access' is incorrect.
✗
Anonymous users can list blobs in the container
Why it's wrong here
Listing blobs requires the 'Container' public access level, not the 'Blob' level. With 'Blob' level, anonymous requests can only perform Get Blob operations on URLs they already know; the anonymous client cannot execute a List Blobs call to enumerate all blob names in the container. This distinguishes 'Blob' from 'Container' access, making the claim false for the scenario described.
✓
Anonymous users can read blobs if they know the blob URL
Why this is correct
Setting the container's public access level to 'Blob' grants anonymous users read permission for individual blobs, but only if they know the exact blob URL. Because the anonymous caller cannot list containers or blobs, discovery must happen out-of-band through a shared link or a known path. This is exactly the behavior enabled by the 'Blob' access level, making the answer correct.

Quick reference

Azure Blob Storage Tier Comparison

Tier	Storage Cost	Retrieval Cost	Latency	Use Case
Hot	Highest	Lowest	Immediate	Active data, frequent reads
Cool	Lower	Higher	Immediate	Data accessed < once / month
Cold	Lower still	Higher	Immediate	Data accessed < once / quarter
Archive	Lowest	Highest + rehydration delay	Hours	Long-term compliance retention

Go deeper

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

Exhibit

Why each option matters

Option-by-option breakdown

Azure Blob Storage Tier Comparison

Related to this question