Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ServiceNow Exam CIS-SP 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:

Carlota
4 months 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
3 months ago
C) Email
upvoted 0 times
...
Clarinda
3 months ago
B) Employee Number
upvoted 0 times
...
Lea
4 months ago
A) Last Name
upvoted 0 times
...
...
Aleisha
4 months ago
I see your point, Clare, but using SSN as UserID could pose security risks.
upvoted 0 times
...
Clare
4 months ago
I would go with SSN, it's a unique identifier for individuals.
upvoted 0 times
...
Linn
4 months ago
I agree with Audry, Email is globally unique and easy to remember.
upvoted 0 times
...
Audry
4 months ago
I think Email would be a good candidate field for UserID.
upvoted 0 times
...
Meghann
5 months 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
3 months ago
I would avoid using SSN for UserID due to privacy concerns.
upvoted 0 times
...
Heidy
4 months ago
I think Email could also work well as a globally unique candidate field.
upvoted 0 times
...
Nana
4 months ago
I agree, Employee Number is a great choice for UserID.
upvoted 0 times
...
...
Judy
5 months 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
4 months ago
I think Employee Number could also work well as a globally unique field for UserID.
upvoted 0 times
...
Lisandra
4 months ago
I agree, using email as the UserID is a good choice.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77