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 AZ-204 Exam - Topic 3 Question 58 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 58
Topic #: 3
[All AZ-204 Questions]

You are building a web application that uses the Microsoft identity platform for user authentication. You are implementing user identification for the web application. You need to retrieve a claim to uniquely identify a user. Which claim type should you use?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Beata
4 months ago
I disagree, idp seems like a better option for user identification.
upvoted 0 times
...
Wenona
4 months ago
I’m surprised that nonce isn’t the answer here!
upvoted 0 times
...
Sheron
4 months ago
Wait, isn't aud also important for identifying users?
upvoted 0 times
...
Glendora
4 months ago
I think A is the right choice too!
upvoted 0 times
...
Zack
5 months ago
Definitely go with A, oid is the unique identifier.
upvoted 0 times
...
Monte
5 months ago
"Nonce" seems like it’s more about security tokens rather than identifying users, so I’m leaning towards "oid" as well.
upvoted 0 times
...
Weldon
5 months ago
I practiced a similar question where "idp" was mentioned, but I don't think it's the right choice for uniquely identifying users.
upvoted 0 times
...
Matthew
5 months ago
I think the claim type we need is "oid" because it stands for Object ID, which is unique for each user.
upvoted 0 times
...
Janella
5 months ago
I'm not entirely sure, but I remember something about "aud" being related to audience validation, not user identification.
upvoted 0 times
...
Shawnna
5 months ago
Okay, let's think this through. A consulting engagement is more about providing advisory services, so I'd guess the answer is likely related to evaluating the policies and procedures rather than just the accounting details.
upvoted 0 times
...
Darci
5 months ago
Okay, I think I've got this. The key steps are: 1) Enqueue the network request in a setTimeout when the search string changes, 2) If there's an existing timeout, cancel it and replace it with a new one, and 3) Store the timerId so you can reference it later. Feels like a pretty straightforward debouncing problem to me.
upvoted 0 times
...

Save Cancel