New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-420 Exam - Topic 13 Question 48 Discussion

Actual exam question for Microsoft's DP-420 exam
Question #: 48
Topic #: 13
[All DP-420 Questions]

You have an Azure Cosmos DB account named account1.

You have several apps that connect to account1 by using the account's secondary key.

You then configure the apps to authenticate by using service principals.

You need to ensure that account1 will only allow apps to connect by using an Azure AD identity.

Which account property should you modify?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Tyisha
3 months ago
Nope, it's definitely disableLocalAuth!
upvoted 0 times
...
Alonzo
3 months ago
I thought it was disableKeyBasedMetadataWriteAccess?
upvoted 0 times
...
Whitney
4 months ago
Wait, are you sure about that?
upvoted 0 times
...
Phung
4 months ago
Totally agree, that's the right move!
upvoted 0 times
...
Helaine
4 months ago
You need to modify the disableLocalAuth property.
upvoted 0 times
...
Laurel
4 months ago
I don’t recall "userAssignedIdentity" being related to this scenario. I think it’s more about authentication methods rather than identity assignment.
upvoted 0 times
...
Alberta
5 months ago
I’m a bit confused about the options. "disableKeyBasedMetadataWriteAccess" sounds familiar, but I don’t think it’s the right one for enforcing Azure AD identities.
upvoted 0 times
...
Julene
5 months ago
I remember practicing a similar question where we had to restrict access to Azure resources. I feel like "disableLocalAuth" might be the answer here.
upvoted 0 times
...
Abel
5 months ago
I think we need to disable the local authentication, but I'm not entirely sure if that's the right property.
upvoted 0 times
...
Isabella
5 months ago
This is a good one. I know I need to restrict access to the Cosmos DB account, but I'm not sure which property is the correct choice. I'll have to think it through step-by-step.
upvoted 0 times
...
Laquita
5 months ago
Okay, let's see... I need to find the property that will enforce Azure AD authentication and disable the secondary key. I'll review the options closely.
upvoted 0 times
...
Aide
5 months ago
Disabling key-based access and requiring Azure AD authentication seems like the right approach here. I'll make sure to double-check the property name.
upvoted 0 times
...
Fannie
5 months ago
Hmm, I'm not too familiar with the specific Cosmos DB account properties. I'll need to think this through carefully.
upvoted 0 times
...
Yaeko
5 months ago
This looks like a straightforward Azure Cosmos DB configuration question. I think I can handle this one.
upvoted 0 times
...
Pedro
5 months ago
This seems like a pretty straightforward data analysis task. I'll focus on identifying any significant changes in the wildlife populations, especially the noted declines in mourning dove and bobwhite quail. And I'll make sure to follow the instructions for adding the SmartArt list - that shouldn't be too difficult.
upvoted 0 times
...
Shoshana
10 months ago
I'm pretty sure the correct answer is not 'userAssignedldentatxe'. That sounds like a typo, not a real property.
upvoted 0 times
Annett
9 months ago
Yes, 'disableLocalAuth' makes more sense in this context.
upvoted 0 times
...
Frankie
9 months ago
I agree, 'userAssignedldentatxe' does sound like a typo.
upvoted 0 times
...
Alverta
9 months ago
I think the correct answer is 'disableLocalAuth'.
upvoted 0 times
...
Vanesa
9 months ago
D) allowedOrxgins
upvoted 0 times
...
Emeline
9 months ago
C) userAssignedldentatxe
upvoted 0 times
...
India
10 months ago
B) disableLocalAuth
upvoted 0 times
...
Lelia
10 months ago
A) disableKeyBasedMetadataWriteAccess
upvoted 0 times
...
...
Lillian
10 months ago
Option A sounds like a great way to disable the ability to write metadata. Perfect for those who want to keep their Cosmos DB account a secret!
upvoted 0 times
Becky
9 months ago
I don't think that option is related to restricting access to Azure AD identities.
upvoted 0 times
...
Kattie
9 months ago
D) allowedOrxgins
upvoted 0 times
...
Maile
9 months ago
Yes, using Azure AD identity for authentication is more secure.
upvoted 0 times
...
Stephaine
9 months ago
C) userAssignedldentatxe
upvoted 0 times
...
Raul
9 months ago
That sounds like a good option to restrict access to the secondary key.
upvoted 0 times
...
Dick
10 months ago
A) disableKeyBasedMetadataWriteAccess
upvoted 0 times
...
...
Juan
10 months ago
D is my pick. Allowing specific origins makes sense for security, but I hope the exam doesn't ask us to spell 'origins' correctly.
upvoted 0 times
...
Ronald
11 months ago
I'm not sure, but option C looks interesting. What is a 'userAssignedldentatxe'?
upvoted 0 times
Glenna
9 months ago
User1: That makes sense. Let's go with option C then.
upvoted 0 times
...
Corazon
9 months ago
User3: I'm not sure, but it sounds like it could be related to assigning identities to users.
upvoted 0 times
...
Roy
9 months ago
User2: What is userAssignedldentatxe?
upvoted 0 times
...
Candra
10 months ago
User1: I think you should modify the userAssignedldentatxe property.
upvoted 0 times
...
...
Percy
11 months ago
Option B is clearly the correct answer, as disabling local authentication will force the apps to use Azure AD identity for authentication.
upvoted 0 times
Claribel
10 months ago
B) disableLocalAuth
upvoted 0 times
...
Ettie
10 months ago
A) disableKeyBasedMetadataWriteAccess
upvoted 0 times
...
...
Ines
11 months ago
I'm not sure. Maybe we should also consider disabling local authentication to enhance security.
upvoted 0 times
...
Xenia
11 months ago
I agree with Eric. Modifying the userAssignedldentatxe property will ensure that only Azure AD identities can connect.
upvoted 0 times
...
Eric
11 months ago
I think we should modify the userAssignedldentatxe property.
upvoted 0 times
...

Save Cancel