Courseiva
← DP-900
Full test
Question 809 of 982
Describe core data concepts →hardMultiple ChoiceObjective-mapped

Quick Answer

The primary benefit is that it restricts access to authorized users only. By setting public access to 'None' on a container, you disable all anonymous read requests, meaning every blob access must be authenticated via an account key, a shared access signature, or Azure AD credentials. This configuration directly enforces the principle of least privilege, ensuring that only explicitly authorized identities can read or list blobs within that container. On the DP-900 exam, this concept tests your understanding of storage account public access and security fundamentals—a common trap is confusing container-level settings with the storage account’s overall public network access toggle. Remember that even if the storage account allows public network access, setting public access to 'None' at the container level still blocks anonymous users. A simple memory tip: "No anonymous access means authorized only"—think of it as locking the container door so only key holders can enter.

DP-900 Describe core data concepts Practice Question

This DP-900 practice question tests your understanding of describe core data concepts. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Exhibit

Refer to the exhibit.
```json
{
  "type": "Microsoft.Storage/storageAccounts/blobServices/containers",
  "apiVersion": "2021-02-01",
  "name": "[concat(variables('storageName'), '/default/data')]",
  "dependsOn": [
    "[resourceId('Microsoft.Storage/storageAccounts', variables('storageName'))]"
  ],
  "properties": {
    "publicAccess": "None"
  }
}
```

You are reviewing an ARM template for an Azure Storage account. The container named 'data' is created with public access set to 'None'. What is the primary benefit of this configuration?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "primary"

    Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.

Question 1hardmultiple choice
Full question →

Exhibit

Refer to the exhibit.
```json
{
  "type": "Microsoft.Storage/storageAccounts/blobServices/containers",
  "apiVersion": "2021-02-01",
  "name": "[concat(variables('storageName'), '/default/data')]",
  "dependsOn": [
    "[resourceId('Microsoft.Storage/storageAccounts', variables('storageName'))]"
  ],
  "properties": {
    "publicAccess": "None"
  }
}
```

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

✓

It restricts access to authorized users only.

Setting public access to 'None' on a container means that anonymous read requests are not allowed. The primary benefit is that only requests with proper authorization (e.g., using an account key, a shared access signature, or Azure AD credentials) can access the blobs within that container. This directly restricts access to authorized users only, which is the core security advantage.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • ✗

    It encrypts data at rest.

    Why it's wrong here

    Encryption is enabled at the storage account level, not container.

  • ✓

    It restricts access to authorized users only.

    Why this is correct

    Setting public access to 'None' disables anonymous access, requiring authentication.

    Clue confirmation

    The clue word "primary" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • ✗

    It enables soft delete for the container.

    Why it's wrong here

    Soft delete is configured separately.

  • ✗

    It prevents accidental deletion of blobs.

    Why it's wrong here

    Public access does not affect deletion; soft delete does.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse 'public access set to None' with broader security features like encryption or deletion protection, when in fact it only controls anonymous read access and does not affect data encryption, soft delete, or accidental deletion safeguards.

Detailed technical explanation

How to think about this question

When public access is set to 'None', the container's ACL (Access Control List) is configured to deny all anonymous requests. This means that any HTTP GET request to a blob URL without a valid authorization header (e.g., a SAS token or account key) will receive a 403 (Forbidden) response. In contrast, when public access is enabled, anonymous requests are allowed and the storage service skips authorization checks, which can expose data if the blob URL is discovered.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DP-900 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Describe core data concepts practice questions

Practise DP-900 questions linked to Describe core data concepts.

Describe an analytics workload on Azure practice questions

Practise DP-900 questions linked to Describe an analytics workload on Azure.

Identify considerations for relational data on Azure practice questions

Practise DP-900 questions linked to Identify considerations for relational data on Azure.

Describe considerations for working with non-relational data on Azure practice questions

Practise DP-900 questions linked to Describe considerations for working with non-relational data on Azure.

DP-900 fundamentals practice questions

Practise DP-900 questions linked to DP-900 fundamentals.

DP-900 scenario practice questions

Practise DP-900 questions linked to DP-900 scenario.

DP-900 troubleshooting practice questions

Practise DP-900 questions linked to DP-900 troubleshooting.

Practice this exam

Start a free DP-900 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions20 questions30 questions50 questionsTimed 30
DP-900 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this DP-900 question test?

Describe core data concepts — This question tests Describe core data concepts — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: It restricts access to authorized users only. — Setting public access to 'None' on a container means that anonymous read requests are not allowed. The primary benefit is that only requests with proper authorization (e.g., using an account key, a shared access signature, or Azure AD credentials) can access the blobs within that container. This directly restricts access to authorized users only, which is the core security advantage.

What should I do if I get this DP-900 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "primary". Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DP-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-900 exam.