ServiceNow & ITIL test (Intermediate)
30 questions · 35 minutes · Free
ITIL practices, ServiceNow ITSM, scripting, workflows and the platform data model.
Take the ServiceNow & ITIL test
What it covers
- ITIL service management
- ServiceNow ITSM
- ServiceNow scripting
- ServiceNow flows and workflows
- ServiceNow tables and CMDB
Interview format
- Questions: 30 questions — 18 multiple choice, 9 multi-answer, 3 predict-the-output
- Time: 35 minutes, timed from the first question
- Difficulty: Intermediate
- Skill area: Enterprise apps
- Price: Free
Sample questions
5 sample questions from the ServiceNow & ITIL test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.
Which method is preferred for setting field visibility, mandatory fields, and read-only settings on a form in ServiceNow, and why?
- Business rules
- Data policies
- Client scripts
- UI policies
Answer: D. UI policies
UI policies are preferred over client scripts for setting field visibility, mandatory fields, and read-only settings because they are easier to maintain, do not require scripting knowledge, and are less error-prone. Client scripts are more appropriate for complex logic or scenarios where dynamic behavior is needed, but they are harder to manage and can lead to performance issues if not used carefully.
What happens to an SLA when a task is paused in a ServiceNow flow?
- The SLA is paused permanently once the task is paused.
- The SLA is paused and resumes when the task is unpaused.
- The SLA continues to count time even when the task is paused.
- The SLA is not affected by the pause or resume of the task.
Answer: B. The SLA is paused and resumes when the task is unpaused.
In ServiceNow, when a task is paused, the associated SLA is also paused. The SLA resumes counting time once the task is unpaused. This behavior ensures that SLAs are not counted during periods when the task is not actively being worked on, providing accurate tracking of time against SLA targets.
In a ServiceNow ITSM project, a user reports an issue with an application that is causing intermittent downtime. The user is not currently impacted, but the issue is expected to recur. How should the incident lifecycle be applied in this scenario?
- The incident should be logged as a problem, and no further action is required since the user is not impacted.
- The incident should be logged as a service request, as the user is not impacted.
- The incident should be logged as an incident, investigated to identify the root cause, and then a problem record should be created if a known error is found.
- The incident should be resolved immediately without logging it, as the user is not impacted.
Answer: C. The incident should be logged as an incident, investigated to identify the root cause, and then a problem record should be created if a known error is found.
According to the ServiceNow ITSM incident lifecycle, an incident should first be logged, then investigated to determine the root cause. If a known error is identified, a problem record should be created to address the underlying issue. The other options are incorrect because they either skip critical steps in the incident lifecycle or misrepresent the correct process.
A ServiceNow practitioner notices that incidents are being closed directly without going through the 'Resolved' state, resulting in the system not following the proper incident lifecycle. What is the correct state to transition an incident to before it automatically closes after a configurable period?
- On Hold
- Resolved
- Closed
- Canceled
Answer: B. Resolved
In ServiceNow ITSM, the incident lifecycle includes states such as New, In Progress, On Hold, Resolved, Closed, and Canceled. When an incident is resolved, it automatically closes after a configurable period (default 7 days). The 'Resolved' state is the correct state to transition an incident to before it closes automatically. Other options are incorrect because 'Closed' is the final state, 'On Hold' is used when the incident is paused, and 'Canceled' is used when the incident is no longer valid.
Which of the following statements accurately describes the ITIL 4 service reporting frameworks?
- ITIL 4 service reporting frameworks are only applicable for internal processes and do not consider performance or complexity.
- ITIL 4 service reporting frameworks are not aligned with the Service Value System (SVS) and instead rely on the ITIL 3 service lifecycle.
- ITIL 4 service reporting frameworks are based on the Service Value System (SVS) and the service value chain, emphasizing the use of metrics to measure performance, complexity, and internal processes.
- ITIL 4 service reporting frameworks focus on the use of legacy ITIL 3 metrics and processes for service reporting.
Answer: C. ITIL 4 service reporting frameworks are based on the Service Value System (SVS) and the service value chain, emphasizing the use of metrics to measure performance, complexity, and internal processes.
The ITIL 4 service reporting frameworks are indeed based on the Service Value System (SVS) and the service value chain. They emphasize metrics to evaluate performance, complexity, and internal processes, ensuring alignment with the guiding principles of ITIL 4. The other options are either incorrect or unrelated to the ITIL 4 service reporting frameworks.
Frequently asked questions
- How many questions are in the ServiceNow & ITIL test?
- 30 questions (18 multiple choice, 9 multi-answer, 3 predict-the-output), with 35 minutes to answer them.
- What does the ServiceNow & ITIL test cover?
- ITIL service management, ServiceNow ITSM, ServiceNow scripting, ServiceNow flows and workflows, ServiceNow tables and CMDB.
- Is the ServiceNow & ITIL test free?
- Yes. It is free to take with a readyforhires account.
- What level is the ServiceNow & ITIL test?
- Intermediate, in Enterprise apps.