MENU
A System Administrator wants to setup their domain hierarchy in a new instance, which practice should they follow when creating the structure?
Suggested Answer: A
Get Premium CIS-SP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
31 comments · newest first
SA
Sanjuana
11 months ago
Adding layers below TOP can complicate things too much.
BA
Barb
11 months ago
A flat domain hierarchy? That sounds risky!
JU
Julene
11 months ago
Wait, why would you want a default domain? Seems unnecessary.
KR
Kris
12 months ago
I totally agree, it helps with organization!
ER
Erinn
12 months ago
A domain hierarchy 3-5 layers deep is usually the way to go.
VA
Val
1 year ago
I definitely remember that a flat hierarchy isn't recommended, but I can't recall the specifics about the layers and their purposes.
CA
Caren
1 year ago
I feel like option C sounds familiar, but I'm uncertain about whether a default domain is necessary or not.
SA
Sanda
1 year ago
I think we practiced a question similar to this, and I recall that having a default domain can be beneficial for organization.
GE
Germaine
1 year 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.
KA
Kattie
1 year 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.
AN
Annalee
1 year 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.
HO
Howard
1 year 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.
MI
Mitsue
1 year 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.
KR
Kris
1 year 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.
ER
Ernest
2 years ago
Adding several layers below the TOP domain seems overkill to me. Keep it simple, you know?
RO
Roxanne
2 years ago
Haha, a totally flat domain hierarchy? That sounds like a recipe for disaster! Gotta have some structure, folks.
AR
Artie
2 years ago
C) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
DE
Dexter
2 years ago
B) Using Service Offerings in the domain hierarchy
GL
Gladys
2 years ago
A) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain
GI
Gilberto
2 years ago
I'm not sure about the 'contains' part. Wouldn't that make the structure more complex than necessary?
BE
Bernardo
2 years ago
That's a valid point, but I still think having a default domain like in option A is more organized.
DO
Douglass
2 years ago
I disagree, I believe option C is better because it allows for flexibility without a default domain.
LO
Louvenia
2 years ago
I agree with Billye. The default domain is also a nice feature to have in the hierarchy.
LA
Layla
2 years ago
I prefer having a default domain in the hierarchy as well.
KR
Kristeen
2 years ago
C) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
BA
Bambi
2 years ago
A) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain
BE
Bernardo
2 years ago
I think option A is the best practice for setting up the domain hierarchy.
BI
Billye
2 years 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.
DO
Dong
2 years ago
C) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
FL
Fletcher
2 years ago
Option A seems like the best choice for setting up the domain hierarchy.
MO
Moon
2 years ago
A) A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain