Blob containers and access levels in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Blob Container Public Access Levels

Which of the following describes the Private access level for an Azure Blob container?

A Only the container owner can read blobs and container metadata; no anonymous access is allowed.

B Anyone can read blobs within the container, but container metadata is private.

C Anyone can read both blobs and container metadata without authentication.

D Anyone can write blobs to the container without authentication.

💡 Hint

Think about who can access the blobs when the container is set to private.

Private access means only authenticated users with proper permissions can read blobs and metadata. No anonymous access is allowed.

❓ service_behavior

intermediate

Effect of Blob Container Access Level on Anonymous Read

You set an Azure Blob container's access level to Blob. What is the expected behavior for anonymous users?

A Anonymous users can write blobs but cannot read any blobs or metadata.

B Anonymous users can list blobs and read container metadata but cannot read blob content.

C Anonymous users can read blobs but cannot list blobs or read container metadata.

D Anonymous users cannot access blobs or container metadata at all.

💡 Hint

Consider what 'Blob' access level allows compared to 'Container' and 'Private'.

The 'Blob' access level allows anonymous read access to blobs only, but not to container metadata or blob listings.

❓ Configuration

advanced

Configuring a Blob Container for Public Read Access

You want to configure an Azure Blob container so that anyone can list blobs and read blob content without authentication. Which access level should you set?

A Private

B Container

C Blob

D Off

💡 Hint

Think about which access level allows listing blobs publicly.

The 'Container' access level allows anonymous users to list blobs and read blob content and container metadata.

❓ security

advanced

Security Risks of Setting Blob Container Access Level to Container

What is a potential security risk when setting an Azure Blob container's access level to Container?

A Anyone can list and read all blobs and container metadata without authentication.

B Anyone can delete blobs without authentication.

C Only authenticated users can read blobs, but metadata is public.

D Anyone can upload malicious blobs without authentication.

💡 Hint

Consider what public access means for data visibility.

Setting access to 'Container' exposes all blobs and metadata to anyone, which can lead to data leakage.

❓ Architecture

expert

Designing Blob Storage Access for a Public Website with Private Data

You are designing Azure Blob storage for a website that serves public images but also stores private user documents. How should you configure the containers?

A Set both containers to 'Private' and use anonymous access for images.

B Set one container to 'Blob' access level for images and another to 'Blob' for user documents.

C Set both containers to 'Container' access level and rely on SAS tokens for private documents.

D Set one container to 'Container' access level for images and another container to 'Private' for user documents.

💡 Hint

Think about separating public and private data with different access levels.

Using separate containers with appropriate access levels ensures public images are accessible while private documents remain secure.