The answer is the condition on `acs:RequestVersion` is preventing access because the request does not use the specified API version. This is the most likely cause when troubleshooting managed identity access denied to Azure Data Lake Storage Gen2 RBAC policy conditions, as the condition explicitly checks the API version in the request header against a required value. If the managed identity’s client or SDK sends a different version, the policy denies the read operation even though the action, resource path, and principal are all correctly configured. On the Microsoft Azure Data Engineer Associate DP-203 exam, this scenario tests your understanding of how Azure RBAC condition keys like `acs:RequestVersion` can override seemingly correct permissions, often appearing as a trick where students focus on role assignments or scope instead of the policy’s conditional logic. A common trap is assuming the managed identity lacks the role, but the real issue is a version mismatch in the request. Memory tip: think “Version Veto”—the condition vetoes access if the API version doesn’t match, regardless of the role.
DP-203 Develop data processing Practice Question
This DP-203 practice question tests your understanding of develop data processing. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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. The following is a JSON policy for an Azure Data Lake Storage Gen2 storage account:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"ManagedIdentity": "..."
},
"Action": [
"Microsoft.Storage/storageAccounts/blobServices/containers/read"
],
"Resource": "/subscriptions/.../resourceGroups/.../providers/Microsoft.Storage/storageAccounts/.../blobServices/default/containers/data/...",
"Condition": {
"Bool": {
"acs:RequestVersion": "2019-12-12"
}
}
}
]
}
Refer to the exhibit. You have a managed identity that needs to read data from the 'data' container in Azure Data Lake Storage Gen2. The policy currently denies access. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Refer to the exhibit. The following is a JSON policy for an Azure Data Lake Storage Gen2 storage account:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"ManagedIdentity": "..."
},
"Action": [
"Microsoft.Storage/storageAccounts/blobServices/containers/read"
],
"Resource": "/subscriptions/.../resourceGroups/.../providers/Microsoft.Storage/storageAccounts/.../blobServices/default/containers/data/...",
"Condition": {
"Bool": {
"acs:RequestVersion": "2019-12-12"
}
}
}
]
}
A
The condition on 'acs:RequestVersion' is preventing access because the request does not use the specified API version
The condition requires API version 2019-12-12, which may not be used.
B
The resource path is malformed; it should include the blob path
Why wrong: The resource path is valid for container-level operations.
C
The action 'Microsoft.Storage/storageAccounts/blobServices/containers/read' is incorrect; it should be 'Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read'
Why wrong: The action is for listing containers, but reading blobs requires a different action.
D
The principal is a managed identity, but the policy requires a user-assigned identity
Why wrong: Managed identity is valid regardless of type.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The condition on 'acs:RequestVersion' is preventing access because the request does not use the specified API version
The condition `acs:RequestVersion` requires the request to use a specific API version, which may not be met. Option A is wrong because the action is correct for reading containers. Option B is wrong because the resource path is correct. Option C is wrong because the principal is a managed identity.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The condition on 'acs:RequestVersion' is preventing access because the request does not use the specified API version
Why this is correct
The condition requires API version 2019-12-12, which may not be used.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Static NAT maps one inside address to one outside address.
✗
The resource path is malformed; it should include the blob path
Why it's wrong here
The resource path is valid for container-level operations.
✗
The action 'Microsoft.Storage/storageAccounts/blobServices/containers/read' is incorrect; it should be 'Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read'
Why it's wrong here
The action is for listing containers, but reading blobs requires a different action.
✗
The principal is a managed identity, but the policy requires a user-assigned identity
Why it's wrong here
Managed identity is valid regardless of type.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-203 NAT questions on configuration and troubleshooting.
Develop data processing — This question tests Develop data processing — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: The condition on 'acs:RequestVersion' is preventing access because the request does not use the specified API version — The condition `acs:RequestVersion` requires the request to use a specific API version, which may not be met. Option A is wrong because the action is correct for reading containers. Option B is wrong because the resource path is correct. Option C is wrong because the principal is a managed identity.
What should I do if I get this DP-203 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-203 NAT questions on configuration and troubleshooting.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
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.
This DP-203 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-203 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.