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 3 Question 10 Discussion

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

A System Administrator wants to setup their domain hierarchy in a new instance, which practice should they follow when creating the structure?

Show Suggested Answer Hide Answer
Suggested Answer: A

Best practices for setting up a domain hierarchy in ServiceNow recommend creating a structure that is not too shallow or too deep. A hierarchy that is 3-5 layers deep is considered optimal as it allows for the use of 'contains' relationships where necessary12. This structure should include a default domain, which typically serves as the catch-all layer for any data that does not belong to a more specific domain3. The default domain is often the TOP domain or a domain just below it. This setup facilitates better organization and management of data and processes across different domains within the instance45.


Contribute your Thoughts:

0/2000 characters
Sanjuana
3 months ago
Adding layers below TOP can complicate things too much.
upvoted 0 times
...
Barb
4 months ago
A flat domain hierarchy? That sounds risky!
upvoted 0 times
...
Julene
4 months ago
Wait, why would you want a default domain? Seems unnecessary.
upvoted 0 times
...
Kris
4 months ago
I totally agree, it helps with organization!
upvoted 0 times
...
Erinn
4 months ago
A domain hierarchy 3-5 layers deep is usually the way to go.
upvoted 0 times
...
Val
5 months ago
I definitely remember that a flat hierarchy isn't recommended, but I can't recall the specifics about the layers and their purposes.
upvoted 0 times
...
Caren
5 months ago
I feel like option C sounds familiar, but I'm uncertain about whether a default domain is necessary or not.
upvoted 0 times
...
Sanda
5 months ago
I think we practiced a question similar to this, and I recall that having a default domain can be beneficial for organization.
upvoted 0 times
...
Germaine
5 months ago
I remember discussing the importance of having a domain hierarchy that's not too flat, but I'm not sure if 3-5 layers is the right depth.
upvoted 0 times
...
Kattie
5 months ago
Whew, domain hierarchies can be tricky. I'm going to take my time on this one and really think through the implications of each choice. I don't want to rush and end up selecting the wrong answer.
upvoted 0 times
...
Annalee
5 months ago
This is a good one. I like that it's testing our understanding of domain hierarchy best practices. I'm going to carefully consider each option and try to eliminate the ones that don't align with the stated requirements.
upvoted 0 times
...
Howard
5 months ago
Okay, I think I've got a handle on this. Based on the requirements, I'm leaning towards option A. The 3-5 layer hierarchy with a default domain seems like the best fit. I'll double-check the other choices, but that's my initial strategy.
upvoted 0 times
...
Mitsue
5 months ago
Hmm, I'm a little unsure about this one. The wording is a bit tricky, and I want to make sure I understand the implications of each answer choice. I may need to re-read the question a couple of times to really grasp what they're looking for.
upvoted 0 times
...
Kris
5 months ago
This looks like a pretty straightforward domain hierarchy question. I'd start by reviewing the key requirements - 3-5 layers, use of "contains" if needed, and whether a default domain is required. That should help me narrow down the options.
upvoted 0 times
...
Ernest
1 year ago
Adding several layers below the TOP domain seems overkill to me. Keep it simple, you know?
upvoted 0 times
...
Roxanne
1 year ago
Haha, a totally flat domain hierarchy? That sounds like a recipe for disaster! Gotta have some structure, folks.
upvoted 0 times
Artie
1 year ago
C) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
upvoted 0 times
...
Dexter
1 year ago
B) Using Service Offerings in the domain hierarchy
upvoted 0 times
...
Gladys
1 year ago
A) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain
upvoted 0 times
...
...
Gilberto
1 year ago
I'm not sure about the 'contains' part. Wouldn't that make the structure more complex than necessary?
upvoted 0 times
...
Bernardo
1 year ago
That's a valid point, but I still think having a default domain like in option A is more organized.
upvoted 0 times
...
Douglass
1 year ago
I disagree, I believe option C is better because it allows for flexibility without a default domain.
upvoted 0 times
...
Louvenia
1 year ago
I agree with Billye. The default domain is also a nice feature to have in the hierarchy.
upvoted 0 times
Layla
1 year ago
I prefer having a default domain in the hierarchy as well.
upvoted 0 times
...
Kristeen
1 year ago
C) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
upvoted 0 times
...
Bambi
1 year ago
A) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain
upvoted 0 times
...
...
Bernardo
1 year ago
I think option A is the best practice for setting up the domain hierarchy.
upvoted 0 times
...
Billye
1 year ago
Option A seems the most logical choice for setting up a domain hierarchy. Allowing for up to 5 layers and the use of 'contains' is a good practice.
upvoted 0 times
Dong
1 year ago
C) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
upvoted 0 times
...
Fletcher
1 year ago
Option A seems like the best choice for setting up the domain hierarchy.
upvoted 0 times
...
Moon
1 year ago
A) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain
upvoted 0 times
...
...

Save Cancel