Courseiva

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

You need to provide temporary access to a specific blob in Azure Blob Storage for a limited time. The access should be time-limited and require no authentication from the user. Which mechanism should you use?

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

Shared access signatures (SAS)

Shared access signatures (SAS) provide time-limited, delegated access to storage resources without requiring the account key. Storage account keys provide full access and never expire. RBAC is for identity-based access, not anonymous. Access keys are long-lived secrets.

Answer analysis

Option-by-option breakdown

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

  • Storage account keys

    Why it's wrong here

    Storage account keys grant unrestricted administrative control over all data and services within the entire storage account. They do not expire and cannot be scoped to a single blob, so using them would expose far more than the targeted blob and fail the 'temporary' requirement. Any compromise of a key demands a full account key rotation, making this approach overly risky and operationally heavy for a one-off access grant.

  • Anonymous public access

    Why it's wrong here

    Anonymous public access removes authentication completely, allowing anyone on the internet to read the blob without restrictions. It can only be configured at the container level, not on a per-blob basis, and the access has no built-in expiry mechanism. To end the access you must manually change the container's public access setting, which would also affect every other blob in that container.

  • Azure RBAC roles

    Why it's wrong here

    Azure RBAC assigns permissions to Azure AD principals (users, groups, or service principals) at a specified scope, such as a container or storage account. It is identity-based, so it cannot grant access to anonymous users, and role assignments do not carry an expiration date. Even if you scope the role to a single blob's container, you would need to manually remove or change the assignment to end access, which is not a true temporary delegation.

  • Shared access signatures (SAS)

    Why this is correct

    A shared access signature (SAS) is a signed URI that grants time-bound and permission-limited access to a specific blob without revealing the account key. It lets you specify exact start/expiry times, allowed IP ranges, and supported protocols, making it ideal for controlled temporary access. Additionally, you can use a stored access policy to revoke the SAS before its expiry, offering a clean way to manage short-lived delegated access.

Quick reference

Azure Blob Storage Tier Comparison

TierStorage CostRetrieval CostLatencyUse Case
HotHighestLowestImmediateActive data, frequent reads
CoolLowerHigherImmediateData accessed < once / month
ColdLower stillHigherImmediateData accessed < once / quarter
ArchiveLowestHighest + rehydration delayHoursLong-term compliance retention

About these practice questions

One of 820 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.