Free ServiceNow CIS-ITSM Actual Exam Questions - Question 13 Discussion

Question No. 13
When configuring stages in Flow Designer, what are some of the options that can be done? (Choose
two.)
Select all that apply, then reveal solution.
US
AA
Adeel A.
2026-02-16

It’s A and D for me. Changing labels is basic customization, and setting estimated durations helps with tracking progress. SLAs usually apply at a higher process level, not individual stages.

0
SY
Sohail Y.
2026-02-16

C and D. Setting SLAs (C) makes sense to track stage goals, and estimated durations (D) help manage timelines better. Renaming states (B) feels off since that's more about record status, not stage setup.

0
ZD
Zain D.
2026-02-16

Probably A and B since renaming states feels more stage-related than setting SLAs or durations.

0
SV
Sami V.
2026-02-15

Changing stage labels and names is definitely an option, so A feels right. Also, setting estimated durations for stages (D) seems useful for planning, making me go with A and D here.

0
DV
David V.
2026-02-13

Honestly, I’m not convinced B is right because renaming states for requested items feels like something tied to the item record itself, not specifically a Flow Designer stage config. A definitely fits since you can customize stage names and labels. About D, setting estimated durations sounds like a task-level setting or maybe part of scheduling, not really a stage property. So I’d pick A and probably C, assuming the version supports SLA per stage. If not C, then just A stands out as a definite choice.

0
DV
David V.
2026-02-11

A/C? Changing stage names is a given, so A is solid. As for C, I remember seeing an option to tie SLAs to specific stages to improve monitoring, especially in newer releases. D sounds plausible but feels more like a task-level setting rather than stage-specific. B definitely seems out since states relate to records, not stages themselves. So my pick would be A and C.

0
DV
David V.
2026-01-27

Maybe A and C. Changing stage names for clarity is definitely allowed, so A makes sense. For C, while SLAs are usually set at a higher level, I think newer versions might let you define SLAs specific to stages to better track performance. D sounds plausible but I’m not sure if estimated durations are set per stage or just overall flow metrics. B feels less likely since states are more tied to records themselves, not the stages in the flow.

0
DV
David V.
2026-01-26

A/D feels right since you can definitely rename stages and set estimated durations for better tracking. B seems off because states usually link to records, not stages directly, and C sounds more like a whole flow SLA.

0
DV
David V.
2026-01-20

It’s A and D, since you can rename labels and set estimated times per stage.

0
DV
David V.
2026-01-19

A/B? I know you can definitely change stage labels and names to make things clearer, so A feels solid. As for B, states for requested item records are often customizable, so renaming them might be allowed too. I’m skeptical about C since SLAs usually cover the whole process, not just one stage. D sounds plausible but setting estimated durations might be more about overall flow or tasks rather than individual stages. So A and B seem like the safer bets here.

0
AK
Ali K.
2026-01-15

A and D seem right, but what about C?

0