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

ServiceNow CIS-SP Exam - Topic 4 Question 5 Discussion

Actual exam question for ServiceNow's CIS-SP exam
Question #: 5
Topic #: 4
[All CIS-SP Questions]

What's a good globally unique candidate field that could be used to populate UserID?

Show Suggested Answer Hide Answer
Suggested Answer: B, C, D

When selecting a field to populate UserID in ServiceNow, it's crucial to choose an identifier that is globally unique to ensure that each user can be distinctly identified. The best practices for such identifiers include:

* Employee Number: Typically, an employee number is unique to an individual within an organization and does not change, making it a reliable identifier1.

* Email: An email address is inherently unique as it is tied to an individual and is used for communication, which also makes it a suitable candidate for UserID2.

* SSN (Social Security Number): While SSN is unique to each individual, it's important to note that using SSN as an identifier should be approached with caution due to privacy and security concerns. However, it is unique and could technically be used to populate UserID3.

The Last Name is not a good candidate for UserID because it is not globally unique; many individuals can share the same last name and it can change over time due to personal reasons.

For further details on creating unique identifiers and best practices, ServiceNow provides documentation and guidelines which can be referred to for implementing these practices within the ServiceNow environment.


Contribute your Thoughts:

0/2000 characters
Justine
3 months ago
Not sure about Email, people change it often.
upvoted 0 times
...
Art
4 months ago
Wait, can Last Name really be unique?
upvoted 0 times
...
Gilberto
4 months ago
SSN is risky, too sensitive!
upvoted 0 times
...
Theodora
4 months ago
I think Email is better since it's unique globally.
upvoted 0 times
...
Trinidad
4 months ago
Employee Number is a solid choice!
upvoted 0 times
...
Herminia
5 months ago
Last Name definitely doesn't work since it's not unique at all, but I can't quite remember if there was a better alternative we discussed.
upvoted 0 times
...
Pamella
5 months ago
I think SSN is too sensitive to use, but I recall it being mentioned in practice questions as a unique identifier.
upvoted 0 times
...
Berry
5 months ago
Employee Number seems like a solid candidate too, but I wonder if it’s always guaranteed to be unique across different organizations.
upvoted 0 times
...
Hildegarde
5 months ago
I remember discussing that email could be a good choice since it's unique to each user, but I'm not entirely sure if it's the best option.
upvoted 0 times
...
Tayna
5 months ago
SSN is definitely not a good choice for a UserID. That's way too personal and sensitive information to use.
upvoted 0 times
...
Lura
5 months ago
I'm not sure about Email - that could change if someone gets a new email address. Gotta go with Employee Number on this one.
upvoted 0 times
...
Roxane
5 months ago
Employee Number seems like the safest bet for a globally unique UserID. Last names can be duplicated, and SSNs are sensitive data.
upvoted 0 times
...
Miriam
5 months ago
This is a tricky one. I'll need to think carefully about the pros and cons of each option.
upvoted 0 times
...
Jennifer
5 months ago
Hmm, I'm a bit unsure about this one. I know there are different models for analyzing business value, but I'm not totally clear on the differences between them. I'll have to think this through carefully.
upvoted 0 times
...
Solange
5 months ago
This seems like a straightforward question about the best approach for a large-scale data processing project. I think the key is to find a solution that can handle the scale and complexity efficiently.
upvoted 0 times
...
Iola
5 months ago
Hmm, I'm not sure about this one. The options seem a bit tricky. I'll have to think it through carefully before selecting an answer.
upvoted 0 times
...
Darell
6 months ago
I'm pretty sure I saw somewhere that the right endpoint for creating messages is just the base URL without any message ID, but I'm not completely confident.
upvoted 0 times
...
Carlota
2 years ago
D. SSN? Really? That's way too sensitive to use as a UserID. Let's keep it simple and secure with option C, Email.
upvoted 0 times
Stephaine
2 years ago
C) Email
upvoted 0 times
...
Clarinda
2 years ago
B) Employee Number
upvoted 0 times
...
Lea
2 years ago
A) Last Name
upvoted 0 times
...
...
Aleisha
2 years ago
I see your point, Clare, but using SSN as UserID could pose security risks.
upvoted 0 times
...
Clare
2 years ago
I would go with SSN, it's a unique identifier for individuals.
upvoted 0 times
...
Linn
2 years ago
I agree with Audry, Email is globally unique and easy to remember.
upvoted 0 times
...
Audry
2 years ago
I think Email would be a good candidate field for UserID.
upvoted 0 times
...
Meghann
2 years ago
I'm leaning towards option B. Employee Number is a good choice because it's already assigned and unique to each user.
upvoted 0 times
Laura
2 years ago
I would avoid using SSN for UserID due to privacy concerns.
upvoted 0 times
...
Heidy
2 years ago
I think Email could also work well as a globally unique candidate field.
upvoted 0 times
...
Nana
2 years ago
I agree, Employee Number is a great choice for UserID.
upvoted 0 times
...
...
Judy
2 years ago
I would go with option C. Email is a great globally unique field for UserID. It's easy to remember and already in use for many applications.
upvoted 0 times
Stephaine
2 years ago
I think Employee Number could also work well as a globally unique field for UserID.
upvoted 0 times
...
Lisandra
2 years ago
I agree, using email as the UserID is a good choice.
upvoted 0 times
...
...

Save Cancel