Free ServiceNow CIS-ITSM Actual Exam Questions

I agree with skipping B and D since 10 Star ratings are rare and pinning’s more for saving, not feedback. So A, C, E, and F seem like the solid picks here.

A, C, E, F seem right since they all involve actual feedback mechanisms. B’s 10 Star scale is pretty unusual, and D (Pin Article) is more for personal use, not feedback. Makes sense to exclude those two.

B. Event Processing Properties usually controls timing aspects for how often checks run, so it fits better for setting intervals than the properties or flow modules.

B/D? Event Processing often sets timing, but flows can trigger checks, so both possible.

A. The name itself suggests full control over user criteria, not just managing existing ones. The other roles seem broader or unrelated to criteria creation specifically.

A seems right here. The “catalog_criteria_admin” role logically implies full control over user criteria, including creation. D might only handle managing existing criteria without creating new ones, so A is a safer bet for both creating and managing. The others like B and E are more about the catalog as a whole, not specifically user criteria.

Eliminate B and D since Implement and Closed usually aren't stale from Authorize.

A/C? Implement usually feels like a forward move, so B seems off. D’s transitions mostly feel like final or end states, not really stale in the middle of a process. A and C both have transitions that might represent going back or restarting steps, which fits the idea of stale transitions better. Between those two, C includes canceled and new, which feel more like starting over or stopping, classic stale moves. A’s options seem more like lateral moves rather than truly stale. So C might be the better fit here.

C, it’s the only one that combines hierarchy and detailed table info.

C, since only it shows both the class hierarchy and detailed table info.

A since problem_admin usually includes all problem-related permissions.

It’s C because so_problem_delete sounds like a specific permission made just for deleting problem records, whereas admin roles might not cover that exact action.

C imo, adding a whole new Change Approval Policy makes sense if you want that extra layer only for SAP Enterprise Services, keeping it separate from normal changes without messing with existing policies.

Maybe A makes sense because adding a new Policy Input lets you specify conditions tied to SAP Enterprise Services, which then triggers the extra approval within the existing Normal Change Approval Policy. That way, you’re not creating a whole new policy or messing with the workflow, just refining the approval criteria.

I think D might actually be the better pick here. The form design usually dictates how fields are presented and arranged in the lookup form itself. While ref_ac_column controls columns, the actual appearance and which fields are shown in the select box often come from the form design. So, D feels like a solid choice based on how ServiceNow typically manages lookup forms.

I agree with choosing B here because the ref_ac_column attribute directly controls which columns are shown in lookup fields, making it the best fit over the other options. B

C/D no, those groups are unrelated to assignment by default. B fits better.

B imo, because Support group fits the problem management context best.

B and C imo, since incidents can result from changes and changes often fix incidents.

B, D – Incidents often cause changes, and some incidents auto-close with change closure.

A/D? Action Pills are definitely the draggable UI bits, but Flow Actions seem like the actual tasks you automate inside a flow. The question sounds like it’s about the component doing the work, not just the UI element.

A imo, because Flow Actions are the predefined tasks you drag and drop to automate steps. Action Pills feel more like UI elements, not the actual component name.

I’m thinking it’s definitely not C because “Waterfall” sounds more like a one-way flow, and the question implies a mutual passing between equivalent variables. The choice between B and D is tricky, but B “Share Variables” stands out since sharing usually means passing data between items, which fits better here than just mirroring or cascading. So I’d go with B.

D imo, “Mirror Variables” suggests reflecting or copying variables exactly between items, which fits the idea of passing equivalent variables from one item to another.

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.

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.

B imo, the item author seems a logical choice since it tracks who made the change. E could work too because the item name would clarify what’s updated without needing extra catalog details.

Maybe A and E. Timestamp seems like a no-brainer for uniqueness, and the item name probably helps identify the update set clearly without needing catalog details.

C/D? The knowledge queries app (C) sounds like it would specifically focus on user search queries, but the search logs app (D) might have broader tracking including other search types. Not sure which is more complete though.

It’s C since the knowledge queries app probably collects all user searches more directly.