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-FSM Exam - Topic 7 Question 19 Discussion

Actual exam question for ServiceNow's CIS-FSM exam
Question #: 19
Topic #: 7
[All CIS-FSM Questions]

How do you prevent a task which has been rejected by an agent from being dynamically assigned to the same agent in the next 24 hours?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Daron
3 months ago
D? Nah, that won't really solve the problem.
upvoted 0 times
...
Kiley
4 months ago
C seems like the best option for dynamic scheduling.
upvoted 0 times
...
Viola
4 months ago
Wait, can we really set a 24-hour rule? Sounds tricky!
upvoted 0 times
...
Lavonda
4 months ago
I think A could work too, but not as effective.
upvoted 0 times
...
Deonna
4 months ago
B is the way to go!
upvoted 0 times
...
Janine
5 months ago
I vaguely recall discussing agent task rejection preferences, but I can't remember if that directly relates to the 24-hour rule.
upvoted 0 times
...
Trinidad
5 months ago
I’m leaning towards option C because it mentions unassignment constraints, which seems relevant to preventing reassignments.
upvoted 0 times
...
Charlesetta
5 months ago
I feel like we covered something similar in practice questions. Configuring custom assignment rules could be a way to handle this, but I’m not confident.
upvoted 0 times
...
Geoffrey
5 months ago
I think option B sounds familiar, but I'm not entirely sure if it's the right one. I remember something about setting a duration for rejected tasks.
upvoted 0 times
...
Leslie
5 months ago
I feel pretty confident about this one. Based on the question, the "Configure custom assignment rules" option seems like the most straightforward solution to prevent the task from being assigned to the same agent within 24 hours. I'll go with that.
upvoted 0 times
...
Cheryl
5 months ago
Okay, let me think this through. I'm guessing the "Configure rejected technician duration system property" might be the way to go, as that seems to directly address the 24-hour requirement. But I'll double-check the other options just to be sure.
upvoted 0 times
...
Nadine
5 months ago
Ah, I see. This is about preventing the same agent from getting a rejected task again in the next 24 hours. I think the "Configure unassignment constraints for dynamic scheduling" option sounds like it could be the right approach to solve this.
upvoted 0 times
...
Suzi
5 months ago
Hmm, I'm a bit unsure about this one. I know there are different ways to handle task assignments and rejections, but I'm not sure which option would be the best fit here. I'll need to think it through carefully.
upvoted 0 times
...
Gwen
5 months ago
This seems like a straightforward configuration question. I think the key is to look for options that directly address the requirement of preventing the task from being assigned to the same agent within 24 hours.
upvoted 0 times
...
Markus
1 year ago
Is there an option to just send the task to the agent's spam folder? That way, they'll never see it coming!
upvoted 0 times
Mabelle
1 year ago
C) Configure unassignment constraints for dynamic scheduling
upvoted 0 times
...
Rochell
1 year ago
B) Configure the rejected technician duration system property
upvoted 0 times
...
Olga
1 year ago
A) Configure custom assignment rules
upvoted 0 times
...
...
Gail
1 year ago
If I choose Option D, can I also configure 'agent task rejection excuses'? I've got a few good ones up my sleeve.
upvoted 0 times
Matthew
1 year ago
C) Configure unassignment constraints for dynamic scheduling
upvoted 0 times
...
Leanna
1 year ago
B) Configure the rejected technician duration system property
upvoted 0 times
...
Freeman
1 year ago
A) Configure custom assignment rules
upvoted 0 times
...
...
Dottie
1 year ago
Option A sounds good, but I can't help but wonder if it would be as effective as the other choices. Gotta go with my gut on this one.
upvoted 0 times
Toshia
1 year ago
I'm not sure about option D, it doesn't seem as practical as the others.
upvoted 0 times
...
Amie
1 year ago
I'm leaning towards option C, it seems like it could work well.
upvoted 0 times
...
Eric
1 year ago
I agree, option B seems like a solid choice.
upvoted 0 times
...
Cristy
1 year ago
I think option B might be the way to go here.
upvoted 0 times
...
...
Annice
1 year ago
I'm not sure about that. I think the answer might be C) Configure unassignment constraints for dynamic scheduling to prevent reassignment to the same agent.
upvoted 0 times
...
Beatriz
1 year ago
Option D seems like it would give the agents more control over the task assignments. That could be useful.
upvoted 0 times
...
Caitlin
1 year ago
Hmm, I'm not sure. Maybe Option B would be a good choice to prevent the same agent from getting the task again.
upvoted 0 times
Tarra
1 year ago
Let's make sure to set that up to avoid assigning the task to the same agent again.
upvoted 0 times
...
Cathrine
1 year ago
I agree, configuring the rejected technician duration system property should do the trick.
upvoted 0 times
...
Elly
1 year ago
I think Option B is the way to go.
upvoted 0 times
...
...
Louisa
1 year ago
I think Option C is the way to go. Unassignment constraints make the most sense here.
upvoted 0 times
Lilli
1 year ago
I think Option D could be worth considering as well.
upvoted 0 times
...
Pedro
1 year ago
I'm not sure about Option B, it might not be as effective.
upvoted 0 times
...
Jillian
1 year ago
I think Option A could also work if set up correctly.
upvoted 0 times
...
Luis
1 year ago
I agree, Option C seems like the best choice.
upvoted 0 times
...
...
Tomas
1 year ago
I agree with Carry. By configuring custom assignment rules, we can prevent the task from being assigned to the same agent again.
upvoted 0 times
...
Carry
2 years ago
I think the answer is A) Configure custom assignment rules.
upvoted 0 times
...

Save Cancel