Question 266 of 881
Implement Least-Privilege Storage Access Using Managed Identity on Azure App Service
A developer is implementing least-privilege storage access. The application runs on Azure App Service and must avoid stored credentials. Which design should be used?
Quick Answer
The correct design is to enable managed identity and grant least-privilege access to the target resource. This works because Azure App Service’s managed identity provides the application with an automatically managed Azure AD identity, eliminating the need for any stored credentials in code or configuration. The app obtains an Azure AD token to authenticate directly to Azure Storage, and by assigning only the specific role required—such as ‘Storage Blob Data Reader’ for read-only access—you enforce least-privilege storage access. On the AZ-204 exam, this scenario tests your understanding of identity-based authentication versus key-based or connection-string approaches; a common trap is to default to storing a connection string in app settings. Remember the mnemonic “MIA” for Managed Identity Authentication: no keys, no secrets, just tokens.
⚠ Common exam trap
Watch out — candidates often think storing a client secret in a configuration file (Option C) is acceptable if it's encrypted or in a secure location, but the question explicitly requires avoiding stored credentials, making managed identity the only correct choice.
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
✓
Enable managed identity and grant least-privilege access to the target resource
Managed identity in Azure App Service allows the application to authenticate to Azure Storage without storing any credentials in code or configuration. By enabling a system-assigned or user-assigned managed identity, the app obtains an Azure AD token automatically, which is used to access the storage resource. Granting the managed identity only the required permissions (e.g., 'Storage Blob Data Reader' for read-only access) enforces least-privilege access, eliminating the need for stored 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.
- ✗
Use a shared administrator account
Why it's wrong here
Shared accounts remove accountability and violate least privilege.
- ✗
Disable authentication for the target resource
Why it's wrong here
Removing authentication is not a secure design.
- ✗
Store a client secret in source control
Why it's wrong here
Source-controlled secrets are exposed and difficult to rotate safely.
- ✓
Enable managed identity and grant least-privilege access to the target resource
Why this is correct
Managed identity lets Azure-hosted apps authenticate without stored secrets.
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 →
Same concept, more angles
2 more ways this is tested on AZ-204
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A developer is implementing least-privilege storage access. The application runs on Azure App Service and must avoid stored credentials. Which design should be used? The design must avoid adding custom operational scripts.
medium- A.Use a shared administrator account
- B.Disable authentication for the target resource
- C.Store a client secret in source control
- ✓ D.Enable managed identity and grant least-privilege access to the target resource
Why D: Azure Managed Identity provides an automatically managed identity in Azure AD that allows the App Service to authenticate to any service supporting Azure AD authentication without storing any credentials. By granting the managed identity only the specific permissions required (least-privilege) on the target storage resource (e.g., Storage Blob Data Reader), the application avoids stored credentials and eliminates the need for custom operational scripts. This aligns with the principle of zero standing credentials and is the recommended approach for Azure App Service.
Variation 2. You need to ensure that an Azure Functions app can access a blob in Azure Storage using its system-assigned managed identity. What should you do first?
easy- A.Configure CORS on the storage account
- ✓ B.Enable the managed identity in the Function App
- C.Assign the Storage Blob Data Reader role to the managed identity at the storage account scope
- D.Generate a SAS token for the blob
Why B: To use a system-assigned managed identity, it must first be enabled on the Azure Functions app. This action creates the identity in Azure Active Directory. Once the identity is enabled, you can then assign the necessary Azure RBAC role, such as 'Storage Blob Data Reader', to this identity at the storage account scope to grant it permissions to access the blob storage. Therefore, enabling the managed identity is the foundational first step.
Last reviewed: Jun 11, 2026
This AZ-204 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 AZ-204 exam.
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.
Sign in to join the discussion.