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-ITSM Exam - Topic 1 Question 92 Discussion

Why don't Problem records automatically move from Resolved to Closed after the fix is implemented.
A) It is designed to follow the ITIL4 standard
B) There is a scheduled job that automatically moves Resolved problems to Closed after 7 days
C) It is good practice to monitor fixes implemented, to ensure the underlying issues are resolved, before closing a problem record
D) There is no Closed state. Problem records are moved to Completed

ServiceNow CIS-ITSM Exam - Topic 1 Question 92 Discussion

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

Why don't Problem records automatically move from Resolved to Closed after the fix is implemented.

Show Suggested Answer Hide Answer
Suggested Answer: E

by Alex at Jul 10, 2024, 09:28 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Eve
9 months ago
Actually, problem records go to Completed, not Closed.
upvoted 0 times
...
Jeannetta
10 months ago
But why 7 days? Seems a bit long to me.
upvoted 0 times
...
Selene
10 months ago
Wait, there's a scheduled job for that? Didn't know!
upvoted 0 times
...
Deandrea
10 months ago
I totally agree, monitoring is key before closing.
upvoted 0 times
...
Joanna
10 months ago
It's all about ITIL4 compliance.
upvoted 0 times
...
Rachael
11 months ago
I vaguely remember that there might not be a "Closed" state for problem records, but I thought they just moved to "Resolved" instead.
upvoted 0 times
...
Felicitas
11 months ago
I feel like monitoring fixes is really important before closing records, so option C makes sense to me.
upvoted 0 times
...
Vivienne
11 months ago
I remember something about a scheduled job that moves records after a certain period, but I can't recall the exact timeframe.
upvoted 0 times
...
Winifred
11 months ago
I think it might be related to ITIL4 standards, but I'm not entirely sure if that's the main reason.
upvoted 0 times
...
Devon
11 months ago
I'm a bit confused on this one. I'm not sure if there's a specific ITIL4 requirement or if there's some kind of automated job involved. I'll have to review my notes to see if I can figure this out.
upvoted 0 times
...
Marva
11 months ago
Okay, I've got this. The answer is C - it's good practice to monitor the fixes before closing the problem record. That makes sense to ensure the underlying issue is really resolved.
upvoted 0 times
...
Sylvie
11 months ago
Hmm, this seems like a tricky one. I'll need to think through the ITIL4 standard and the problem management process to figure out the best approach.
upvoted 0 times
...
Earlean
11 months ago
I think the key here is understanding the problem management lifecycle. The Resolved state is when the fix is implemented, but you want to verify it before officially closing the record. Option C seems to be the best answer based on that.
upvoted 0 times
...
Marcelle
11 months ago
Hmm, I'm a bit confused by the different subnet options. I'll need to double-check the details to make sure I understand which subnets can be used for the new web app.
upvoted 0 times
...
Natalie
11 months ago
Hmm, I'm a bit unsure about this one. I'll need to think through the different options carefully and make sure I understand the key concepts behind interim reporting.
upvoted 0 times
...
Carry
12 months ago
Anomaly detection seems like the most proactive approach to me. I'll focus on that option.
upvoted 0 times
...
Avery
1 year ago
Ha! I was totally lost on this one. Glad the correct answer is C, makes sense to double-check before closing the problem.
upvoted 0 times
Benton
1 year ago
D) There is no Closed state. Problem records are moved to Completed
upvoted 0 times
...
Jaime
1 year ago
C) It is good practice to monitor fixes implemented, to ensure the underlying issues are resolved, before closing a problem record
upvoted 0 times
...
Julio
1 year ago
B) There is a scheduled job that automatically moves Resolved problems to Closed after 7 days
upvoted 0 times
...
Virgina
1 year ago
A) It is designed to follow the ITIL4 standard
upvoted 0 times
...
...
Mireya
1 year ago
This is a tricky one. I was torn between A and C, but C makes more sense. We need to validate the fix before closing the problem.
upvoted 0 times
...
Sanda
1 year ago
Ah, I was going with option B, but I guess that's not the case. Monitoring the fixes is a good practice to make sure the problem is really closed.
upvoted 0 times
...
Dean
1 year ago
I think option C is the correct answer. It's important to monitor the fix implementation to ensure the underlying issue is truly resolved before closing the problem record.
upvoted 0 times
Alline
1 year ago
Option A makes sense, following ITIL4 standards ensures consistency in handling problem records.
upvoted 0 times
...
Chauncey
1 year ago
I think option B is more efficient, with the scheduled job automatically moving records after 7 days.
upvoted 0 times
...
Arlyne
1 year ago
I agree, monitoring the fix is crucial to prevent recurring issues.
upvoted 0 times
...
...
Dominga
1 year ago
But isn't it also because there is a scheduled job that automatically moves Resolved problems to Closed after 7 days?
upvoted 0 times
...
Glendora
1 year ago
I agree with Ailene. It's important to ensure the underlying issues are truly resolved before closing a problem record.
upvoted 0 times
...
Ailene
1 year ago
I think the reason why Problem records don't automatically move from Resolved to Closed is because it is good practice to monitor fixes implemented.
upvoted 0 times
...

Save Cancel