DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
Exhibit
Refer to the exhibit.
{
"identity": {
"type": "UserAssigned",
"userAssignedIdentities": {
"/subscriptions/.../resourceGroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/mi-etl": {}
}
},
"properties": {
"linkedServices": [
{
"name": "ls_storage",
"type": "AzureStorage",
"typeProperties": {
"connectionString": "DefaultEndpointsProtocol=https;AccountName=mystorage;AccountKey=mykey"
}
}
]
}
}Refer to the exhibit. You are reviewing a Data Factory JSON definition. The factory has a user-assigned managed identity configured. However, the linked service to Azure Storage uses an account key. What security improvement should you recommend?
⚠ Common exam trap
DP-203 often tests whether candidates recognize that storing a key in Key Vault is not the same as eliminating the key — the exam rewards the more secure managed identity pattern over 'hide the secret' workarounds.
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
✓
Modify the linked service to use the managed identity for authentication
Since the Data Factory already has a user-assigned managed identity, the most secure improvement is to reconfigure the Azure Storage linked service to authenticate via that managed identity instead of an account key. Managed identities eliminate the need to store and rotate secrets, and Azure RBAC can grant the identity the minimum required role (e.g., Storage Blob Data Contributor) on the storage account. This is Microsoft's recommended authentication pattern for ADF linked services.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add a firewall rule to limit access to the storage account
Why it's wrong here
A firewall rule restricts network origin but leaves the storage account key embedded in the linked service definition, so anyone reading the JSON obtains full account access. Firewall rules suit restricting public exposure to known IP ranges; here the requirement is removing the static secret entirely by switching the linked service to the user-assigned managed identity.
- ✓
Modify the linked service to use the managed identity for authentication
Why this is correct
Switching the linked service from account-key authentication to the user-assigned managed identity removes stored credentials, letting Microsoft Entra ID issue and rotate tokens automatically. This eliminates secret sprawl and satisfies the security improvement sought for the Storage linked service.
- ✗
Remove the managed identity and use a service principal
Why it's wrong here
Removing the managed identity discards the credential-free authentication already provisioned for the factory, and a service principal reintroduces a secret that must be stored and rotated. Service principals suit cross-tenant access or scenarios where the resource cannot receive a managed identity; here, switching the linked service to the user-assigned managed identity removes the account key entirely.
- ✗
Keep the account key but store it in Azure Key Vault
Why it's wrong here
Storing the account key in Key Vault still leaves a shared secret that must be rotated and can be exfiltrated, so the user-assigned managed identity remains unused. Key Vault suits centralising secrets for services lacking identity support; here Microsoft Entra ID authentication removes the credential entirely.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
This DP-203 question is part of Courseiva's 509-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.