Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ServiceNow CIS-CSM Exam - Topic 5 Question 92 Discussion

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

A customer service manager would like to limit the reading and creation of knowledge articles within a specific Knowledge Base to the Customer Support group only. Which features should be used to accomplish this? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, D

by Buddy at Apr 04, 2025, 10:04 AM

Limited Time Offer

25%

Off

Get Premium CIS-CSM Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Virgie
4 months ago
Wait, can you really hide the Knowledge Base completely?
upvoted 0 times
...
Shelba
4 months ago
Totally agree, A and D make sense!
upvoted 0 times
...
Jody
5 months ago
I’m not sure about B, seems like a hassle to whitelist everyone.
upvoted 0 times
...
Georgene
5 months ago
A and C could work too, but I think D is essential!
upvoted 0 times
...
Chantell
5 months ago
A and D are the right choices for limiting access.
upvoted 0 times
...
Chuck
5 months ago
Hiding the Knowledge Base sounds like it could work, but I don't think C is what the manager wants.
upvoted 0 times
...
Marla
6 months ago
I practiced a similar question, and I feel like A is definitely one of the answers, but I can't recall the second one.
upvoted 0 times
...
Alethea
6 months ago
I think whitelisting could be a way to limit access, but I'm not sure if B is the best choice here.
upvoted 0 times
...
Marci
6 months ago
I remember something about user criteria being important for controlling access, so maybe A and D?
upvoted 0 times
...
Judy
6 months ago
A and D seem like the logical choices here. Restricting read and create permissions to the Customer Support group should do the trick. I'm feeling good about this one.
upvoted 0 times
...
Verlene
6 months ago
Okay, let's see. I'm thinking A and B would be the best options to accomplish the goal of limiting access to the Customer Support group only. I feel pretty good about that.
upvoted 0 times
...
Alisha
7 months ago
Hmm, I'm not sure about this one. I think A and B might be the right choices, but I'm not completely confident. I'll have to think it through carefully.
upvoted 0 times
...
Tijuana
7 months ago
This seems straightforward - I'd go with options A and D to limit read and create access to the Customer Support group.
upvoted 0 times
...
Justine
12 months ago
A and D, all the way. Gotta keep those articles on lockdown, or the customers might start thinking they know stuff!
upvoted 0 times
Margarita
10 months ago
Agreed, limiting access is key to maintaining the integrity of the knowledge base.
upvoted 0 times
...
Simona
10 months ago
D) Cannot Contribute user criteria
upvoted 0 times
...
Carmela
10 months ago
A) Can Read user criteria
upvoted 0 times
...
Arlette
10 months ago
Exactly, we need to control who can access and edit those articles.
upvoted 0 times
...
Micaela
10 months ago
D) Cannot Contribute user criteria
upvoted 0 times
...
Sina
10 months ago
A) Can Read user criteria
upvoted 0 times
...
...
Shanice
12 months ago
C and D, definitely. Hiding the knowledge base from the portal is a classic move. Sneaky, but effective!
upvoted 0 times
...
Chantell
12 months ago
I'm going with A and D. Sounds like the easiest way to control who can read and create articles. Don't want any leaks!
upvoted 0 times
Lilli
11 months ago
It's important to restrict access to maintain confidentiality.
upvoted 0 times
...
Julio
11 months ago
Agreed, those features will help control who can view and contribute.
upvoted 0 times
...
Nidia
11 months ago
A and D are the best options to limit access.
upvoted 0 times
...
...
Jesus
1 year ago
Hmm, B and C seem like they'd do the trick. Hide that knowledge base from everyone but the support crew!
upvoted 0 times
Ashley
10 months ago
User 4: Sounds good, let's make those changes.
upvoted 0 times
...
Brinda
10 months ago
User 3: Agreed, that way only the Customer Support group can access it.
upvoted 0 times
...
Leota
11 months ago
User 2: Yeah, we should definitely hide it from everyone else.
upvoted 0 times
...
Rozella
11 months ago
User 1: I think B and C are the way to go.
upvoted 0 times
...
Laurel
11 months ago
D) Cannot Contribute user criteria
upvoted 0 times
...
Tyisha
11 months ago
C) Hide the Knowledge Base from the Knowledge Base Portal
upvoted 0 times
...
Janna
12 months ago
B) Whitelist all other groups from the Knowledge Base
upvoted 0 times
...
Yuki
12 months ago
A) Can Read user criteria
upvoted 0 times
...
...
Vicky
1 year ago
I'm not sure about B) Whitelist all other groups. It might give access to unintended users.
upvoted 0 times
...
Hailey
1 year ago
I agree with Mammie. Also, D) Cannot Contribute user criteria should be used to restrict creation.
upvoted 0 times
...
Twana
1 year ago
I think A and D are the way to go. Gotta keep that knowledge locked down, you know?
upvoted 0 times
Julio
11 months ago
Pauline: Exactly, we need to limit who can read and contribute to the knowledge base.
upvoted 0 times
...
Ming
11 months ago
User 3: So, only the Customer Support group should have access to those articles.
upvoted 0 times
...
Pauline
11 months ago
User 2: Yeah, we definitely need to keep that knowledge secure.
upvoted 0 times
...
Twana
11 months ago
User 1: I agree, A and D seem like the best options to restrict access.
upvoted 0 times
...
Jamal
11 months ago
Definitely, it's important to limit access to certain groups to maintain the integrity of the information.
upvoted 0 times
...
Ulysses
11 months ago
That makes sense. We need to control who can access and contribute to the knowledge base.
upvoted 0 times
...
Izetta
12 months ago
D) Cannot Contribute user criteria
upvoted 0 times
...
Gilma
1 year ago
A) Can Read user criteria
upvoted 0 times
...
...
Mammie
1 year ago
I think A) Can Read user criteria should be used to limit access.
upvoted 0 times
...

Save Cancel