Troubleshooting practice questions

An administrator is troubleshooting why conflict detection is not running when changes are updated via a REST API integration. Which condition in the conflict detection business rule might prevent execution during API calls?

Trap 1: Conflict detection requires an interactive web browser session

Conflict detection is a server-side engine and runs via business rules regardless of interaction method.

Trap 2: REST APIs inherently disable all database business rules globally

REST APIs execute business rules unless explicitly instructed otherwise with specific headers.

Trap 3: Integration accounts lack read access to the cmdb_ci table

Lack of read access causes security errors, not silent skipping of conflict logic.

A
Conflict detection requires an interactive web browser session
Why wrong: Conflict detection is a server-side engine and runs via business rules regardless of interaction method.
B
The business rule checks if the update modifies schedule-related fields (like planned start/end or CI) and runs accordingly
Conflict detection only runs when fields impacting scheduling or CI assignment are modified to optimize performance.
C
REST APIs inherently disable all database business rules globally
Why wrong: REST APIs execute business rules unless explicitly instructed otherwise with specific headers.
D
Integration accounts lack read access to the cmdb_ci table
Why wrong: Lack of read access causes security errors, not silent skipping of conflict logic.

Question 2hardmulti select

An administrator is troubleshooting why related incidents are not receiving workaround updates when a Problem is resolved. Which THREE areas should the administrator inspect? (Choose three.)

Trap 1: The Employee Center portal theme configuration

Portal themes affect styling, not backend workaround propagation logic.

Trap 2: The hardware asset barcode scanner plugin

Barcode scanning is unrelated to problem-to-incident communication.

A
Problem Management properties governing workaround communication
Properties determine if workaround propagation is enabled globally.
B
The Employee Center portal theme configuration
Why wrong: Portal themes affect styling, not backend workaround propagation logic.
C
The hardware asset barcode scanner plugin
Why wrong: Barcode scanning is unrelated to problem-to-incident communication.
D
Business rules or script logic responsible for updating child incidents
Business rules handle the server-side pushing of workarounds to related incidents.
E
The relationship linkage in the 'Child Incidents' related list
If incidents are not properly linked as child incidents, updates will not reach them.

Question 3hardmulti select

An administrator is troubleshooting a failing Catalog Client Script. Which THREE of the following practices should be followed to ensure the script works correctly in Service Portal? (Choose three.)

Trap 1: Use synchronous GlideRecord queries inside client-side OnChange…

Synchronous queries are deprecated and blocked in Service Portal.

Trap 2: Write all client scripts using jQuery selector syntax for broad…

jQuery is discouraged and not natively standard for Service Portal catalog client scripts.

A
Avoid direct DOM manipulation (e.g., document.getElementById) and use g_form APIs instead.
Direct DOM access fails or is unsupported in Service Portal due to container isolation.
B
Use synchronous GlideRecord queries inside client-side OnChange scripts for instant validation.
Why wrong: Synchronous queries are deprecated and blocked in Service Portal.
C
Write all client scripts using jQuery selector syntax for broad browser support.
Why wrong: jQuery is discouraged and not natively standard for Service Portal catalog client scripts.
D
Set the UI type to 'Mobile / Service Portal' or 'All' to ensure portal execution.
UI type configuration governs whether the script loads in Service Portal.
E
Test scripts using g_form methods that are supported across both desktop and portal interfaces.
Using supported g_form methods ensures cross-platform compatibility.

Question 4hardmultiple choice

A user reports that a variable is not appearing on a Catalog Item form, even though the variable is active and associated with the item. Which troubleshooting step should be performed first?

Trap 1: Rebuild the Catalog Item cache

Caching issues are rare and usually systemic, not item-specific.

Trap 2: Verify the Catalog Item workflow

Workflow logic does not affect form visibility during item selection.

Trap 3: Check the Variable Set order

Order affects sequence, not visibility.

A
Rebuild the Catalog Item cache
Why wrong: Caching issues are rare and usually systemic, not item-specific.
B
Verify the Catalog Item workflow
Why wrong: Workflow logic does not affect form visibility during item selection.
C
Inspect Catalog UI Policies and Catalog Client Scripts for visibility logic
Client-side logic is the most likely culprit for unexpected hiding of variables.
D
Check the Variable Set order
Why wrong: Order affects sequence, not visibility.

Question 5hardmulti select

An administrator is troubleshooting why conflict detection is not evaluating custom CI relationship types. Which THREE components control how CI relationships are traversed during conflict detection? (Choose three.)

Trap 1: Service Catalog workflow versioning rules

Catalog versioning is unrelated to CMDB relationship traversal.

Trap 2: Incident management priority lookup tables

Priority lookup tables govern incident priority, not change relationships.

A
Service Catalog workflow versioning rules
Why wrong: Catalog versioning is unrelated to CMDB relationship traversal.
B
CI relationship type definitions (cmdb_rel_type) specifying upstream/downstream semantics
Relationship types define how CIs are connected and interpreted.
C
Conflict detection system properties enabling relationship traversal
Properties must enable checking related CIs for conflicts to occur.
D
Incident management priority lookup tables
Why wrong: Priority lookup tables govern incident priority, not change relationships.
E
Script includes (such as ConflictFinderSNC) containing the traversal query logic
Script includes execute the recursive queries traversing related CIs.

Question 6hardmultiple choice

You are troubleshooting a scenario where an Incident SLA is not attaching to a ticket. What is the first place you should investigate?

Trap 1: Incident State

While relevant, the definition conditions are the root of attachment logic.

Trap 2: System Dictionary

Dictionary settings do not control SLA attachment logic.

Trap 3: User Preferences

User preferences do not affect server-side SLA engine processing.

A
SLA Definition Conditions
The condition builder determines the start criteria; if these don't match the ticket, the SLA won't attach.
B
Incident State
Why wrong: While relevant, the definition conditions are the root of attachment logic.
C
System Dictionary
Why wrong: Dictionary settings do not control SLA attachment logic.
D
User Preferences
Why wrong: User preferences do not affect server-side SLA engine processing.

Question 7hardmulti select

An administrator is troubleshooting a Catalog Client Script that is not executing properly on a Service Portal catalog item. Which THREE factors should be verified? (Choose three.)

Trap 1: The user has admin rights to the database

Catalog client scripts execute based on form interaction regardless of admin status, provided the item is accessible.

Trap 2: The script is written in Java rather than JavaScript

ServiceNow client scripts are strictly written in JavaScript.

A
The user has admin rights to the database
Why wrong: Catalog client scripts execute based on form interaction regardless of admin status, provided the item is accessible.
B
The 'UI Type' field is set to 'Mobile/Service Portal' or 'All'
Scripts configured exclusively for Desktop (UI Type = Desktop) will not execute in Service Portal.
C
The correct variable name is referenced in the script and applies to the catalog item
Client scripts must target valid variable names and be correctly associated with the catalog item or variable set.
D
The script is written in Java rather than JavaScript
Why wrong: ServiceNow client scripts are strictly written in JavaScript.
E
The script is marked as 'Active'
Inactive scripts do not execute.

Question 8hardmultiple choice

An administrator is troubleshooting an Order Guide where Rule Base conditions evaluate to true, but the expected child catalog item is not being added to the cart. What is a valid troubleshooting step in this scenario?

Trap 1: Check the 'No cart' attribute on the order guide record itself.

Order guides require a cart mechanism to function; disabling cart prevents ordering entirely.

Trap 2: Rewrite the rule base conditions using legacy javascript eval()…

Eval() statements are not standard or recommended for order guide rule base conditions.

Trap 3: Disable cascading variables on all child catalog items.

Disabling cascading would prevent data passing, not item generation.

A
Check the 'No cart' attribute on the order guide record itself.
Why wrong: Order guides require a cart mechanism to function; disabling cart prevents ordering entirely.
B
Verify that the child catalog item is active and that the submitting user satisfies the child item's User Criteria.
Even if the rule base evaluates to true, if the user cannot view the child item due to User Criteria or if the item is inactive, it will not be added.
C
Rewrite the rule base conditions using legacy javascript eval() statements.
Why wrong: Eval() statements are not standard or recommended for order guide rule base conditions.
D
Disable cascading variables on all child catalog items.
Why wrong: Disabling cascading would prevent data passing, not item generation.

Question 9hardmultiple choice

An administrator has configured a Catalog UI Policy with a Catalog UI Policy Action. However, the action is not taking effect when the dependent variable changes value. What is a common troubleshooting step for Catalog UI Policies?

Trap 1: Clear the browser cache and restart the instance JVM

While caching can occasionally affect scripts, checking 'Applies on Target' is the primary functional configuration requirement.

Trap 2: Convert the UI Policy into a Business Rule

Business rules do not control client-side form behavior.

Trap 3: Change the UI Policy execution order to zero

Order determines sequence but does not fix scoping or applicability issues.

A
Clear the browser cache and restart the instance JVM
Why wrong: While caching can occasionally affect scripts, checking 'Applies on Target' is the primary functional configuration requirement.
B
Convert the UI Policy into a Business Rule
Why wrong: Business rules do not control client-side form behavior.
C
Change the UI Policy execution order to zero
Why wrong: Order determines sequence but does not fix scoping or applicability issues.
D
Verify that 'Applies on Target' (such as Service Portal or Catalog Item) is correctly checked on the UI Policy definition
Catalog UI Policies must have the appropriate checkboxes enabled for where they should execute (e.g., Catalog Item, Service Portal, or both).