ServiceNow CIS-ITSM Exam Prep
Certified Implementation Specialist - IT Service Management (Page 3 )

Updated On: 30-Aug-2026

A customer requests that when the Service Desk agent clicks on the information icon for the Caller's name, the quick view frame shows only the following fields: User name -Manager name -Email Address -Employee ID -How would you modify the quick view frame?

  1. Update the sys_popup view for the user table
  2. Update the sys_quick view for the caller table
  3. Update the sys_popup view for the caller table
  4. Update the sys_quick view for the user table

Answer(s): A

Explanation:

The correct answer is A. Update the sys_popup view for the user table.
Here's a detailed justification:
The "quick view" (or "hover") functionality in ServiceNow, which displays information when hovering over a reference field's information icon, is controlled by views.
When a user hovers over the Caller field (which is a reference to the User [sys_user] table), the system needs to determine which view to display. The sys_popup view is specifically designed for this purpose.
Here's why the other options are incorrect:
B: Update the sys_quick view for the caller table: There isn't a standard "sys_quick" view mechanism directly controlling hover information displays in ServiceNow. The sys_popup is the dedicated view for this.
C: Update the sys_popup view for the caller table: The Caller field references the User table, it doesn't have a table that governs the fields displayed within the popup on hover. The sys_user table defines the details of each user.
D: Update the sys_quick view for the user table: As stated before, sys_quick view is not related to hover information displays. Detailed
1. Reference Fields: The Caller field on the Incident table is a reference field. It points to a record in another table, which is the User [sys_user] table.
2. Hover Behavior: When you hover over the information icon next to a reference field, ServiceNow displays a popup window. This window shows information related to the record being referenced.
3. Views: Views in ServiceNow are named arrangements of fields on a form or list. They determine what information is displayed to the user under certain circumstances.
4. The sys_popup View: The sys_popup view is a specialized view specifically designed for popup windows in reference fields.
When ServiceNow displays the popup window for the Caller field, it looks for the sys_popup view defined on the User [sys_user] table. If it does not exist, the default view will show the full table.
5. Customization: To change the fields that appear in the quick view, you need to modify the sys_popup view on the referenced table (in this case, the User [sys_user] table). You would add the desired fields (User name, Manager name, Email Address, Employee ID) to this view.
Steps to Modify:
1. Navigate to System UI > Views . 2. Search for "sys_popup". 3. Select 'sys_user' for Table. 4. Add/remove fields from the form layout to show/hide fields.
Example: To show User Name, Email Address, Manager name, and Employee ID, you would add those fields to the sys_popup view on the User [sys_user] table. Authoritative Links:
ServiceNow Docs - Views: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/form-administration/concept/c_Views.html ServiceNow Community - Views: https://community.servicenow.com/community? id=community_article&sys_id=d16ff9a8dbb6d0103daa1ea8c49619b3
By modifying the sys_popup view, the customer's request will be satisfied: only the specified fields will be displayed when hovering over the Caller's information icon.



Your customer has built a mature knowledge base, with articles targeted to internal audiences -which are technical. Other articles are written for end users, with simple instructions. From the Incident form, the agents would like to be able to identify which articles are visible to the callers What feature would you use, to satisfy this requirement?

  1. Internal/External Highlighting
  2. Search as User
  3. Show User Viewable
  4. User Only View

Answer(s): B

Explanation:

The correct answer is B. Search as User . Here's why:
The requirement is for agents to identify, from the Incident form, which knowledge articles are visible to the caller (the end-user). The most direct and efficient way to achieve this is by using the "Search as User" functionality. This feature allows an agent to impersonate the caller and perform a knowledge search as if they were the end-user. This means the search results will be filtered based on the caller's roles, user criteria, and any other access restrictions configured on the knowledge base. The agent will then see only the articles the caller would see.
"Internal/External Highlighting" (A) could involve visually distinguishing articles based on their audience, but this is usually a pre-existing article property, and doesn't dynamically adapt to the specific caller's permissions. It doesn't filter the search results based on the end user's access rights.
"Show User Viewable" (C) is too vague.
While a generic "viewable" flag could exist, it doesn't guarantee the same level of granular access control that "Search as User" provides. It would likely need substantial customization, which is less efficient than using the out-of-the-box functionality.
"User Only View" (D) is unclear and isn't a standard ServiceNow feature specifically designed for this purpose within the incident form's knowledge search. It sounds like it might filter to show only user-created content (if it existed), which is completely unrelated to the requirement.
Therefore, "Search as User" is the most suitable because it provides the capability to accurately simulate the end-user's knowledge search experience directly from the Incident form. This functionality leverages the platform's built-in access control mechanisms related to Knowledge Management.
Further research:
ServiceNow Documentation on Impersonating a User: https://docs.servicenow.com/bundle/utopia-platform-administration/page/administer/navigation_and_ui/task/t_ImpersonateAUser.html ServiceNow Knowledge Management Documentation: https://docs.servicenow.com/bundle/utopia-servicenow-platform/page/product/knowledge-management/concept/knowledge-management.html



Your customer is using the baseline Create Incident Catalog Item and would like to add a few additional input fields. How should you update the catalog item?

  1. Edit in Catalog Item Designer
  2. Edit in Item Designer
  3. Edit in Catalog Builder
  4. Edit in Form Designer

Answer(s): C

Explanation:

The provided answer, C (Edit in Catalog Builder), is the most appropriate method for adding new input fields to an existing catalog item like the "Create Incident" item in ServiceNow's IT Service Management module.
Catalog Builder is designed to provide a guided, user-friendly interface for creating and maintaining service catalog items. It simplifies the process of adding variables (input fields), defining workflows, and setting up pricing. It provides a centralized and streamlined approach.
Option A (Catalog Item Designer) is not the correct option because the catalog item designer has not been released yet.
Option B (Item Designer) is for creating new catalog items or editing existing items that are not part of the standard service catalog.
Option D (Form Designer) is mainly used to customize the form layout of tables, including incident forms themselves.
While you could theoretically add fields to the Incident table through the Form Designer and expose them via the catalog item, this is a less direct and generally discouraged approach. Modifying the underlying table schema for catalog item-specific fields is not best practice. This would modify the incident form for all users, potentially impacting unrelated workflows.
Catalog Builder is the best solution because you are adding input variables to an existing catalog item and not changing the table or form layouts. You simply want to add variables to the Service Catalog item form.
In summary, when dealing with augmenting existing catalog items with additional input fields (variables), Catalog Builder offers the most efficient, intuitive, and ServiceNow-recommended method for achieving the desired outcome within the IT Service Management context.
References:
ServiceNow Documentation: Service Catalog Items: ( https://docs.servicenow.com/en-US/bundle/quebec-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogItems.html ) ServiceNow Documentation: Using the Catalog Builder: ( https://docs.servicenow.com/bundle/utah-platform-administration/page/build-cloud-based-apps/native-platform/service-catalog/concept/catalog-builder.html )


Reference:

References:
ServiceNow Documentation: Service Catalog Items: ( https://docs.servicenow.com/en-US/bundle/quebec-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogItems.html ) ServiceNow Documentation: Using the Catalog Builder: ( https://docs.servicenow.com/bundle/utah-platform-administration/page/build-cloud-based-apps/native-platform/service-catalog/concept/catalog-builder.html )



Your customer is complaining that Service Desk users keep accidentally assigning Incidents to the Network CAB, instead of Network Support You have confirmed that: The Network Support group record has the Group types: Incident and Change The Network CAB group record has the Group type: Change What could you do on the incident form, for the Assignment Group field, to resolve this issue?

  1. Add a UI action to hide the Network CAB group from the list
  2. Add a UI action to provide an error message if the Network CAB group is selected
  3. Add Dictionary Override to specify the Incident group Reference Qualifier
  4. Modify the choice list to include only the appropriate group types

Answer(s): C

Explanation:

The correct answer is C: Add a Dictionary Override to specify the Incident group Reference Qualifier. Here's why:
The problem is that both the Network Support and Network CAB groups appear in the Assignment Group field on the Incident form, leading to misassignment. The key to solving this is to filter the available Assignment
Groups specifically for Incidents.
Option A, hiding the Network CAB group with a UI Action, isn't ideal. The Network CAB group might be legitimately needed in other contexts, such as Change Management. Hiding it outright limits functionality elsewhere.
Option B, an error message upon selection, is also not user-friendly. It requires the user to make the mistake before being notified, leading to a less efficient workflow. Prevention is better than correction.
Option D, modifying the choice list, isn't the appropriate method. The list is dynamically generated based on the group table, and directly altering it would be problematic and not scalable.
A Dictionary Override, specifically on the Assignment Group field for the Incident table, allows you to modify the reference qualifier. This qualifier acts as a filter for the groups that appear in the assignment group field. By setting the reference qualifier to only include groups with the "Incident" group type, you ensure that only relevant support groups like "Network Support" are displayed when assigning incidents. This directly addresses the core issue without impacting other modules or requiring user error correction. This is the cleanest, most targeted, and most scalable solution. The dictionary override provides a table-specific setting that will only apply to incidents, leaving other tables untouched. https://developer.servicenow.com/dev.do#!/learn/courses/kingston/scripting_kingston/scripting_admin/ platform-administration/page/script/client-scripts/concept/c_ReferenceQualifiers.html



Which Agent workspace feature gives agents automatic search results that show possible solutions for records they open?

  1. Chat Bot
  2. Related Search Results
  3. Knowledge Bases
  4. Intelligent Agent
  5. Agent Assist

Answer(s): E

Explanation:

The correct answer is E, Agent Assist. Agent Assist within ServiceNow's Agent Workspace is designed to proactively provide agents with relevant information and solutions as they work on records. Its core function is to present a context-sensitive pane containing knowledge articles, catalog items, community discussions, and other relevant content based on the information in the record being viewed (e.g., incident, problem, change). This automatic search functionality eliminates the need for agents to manually search for solutions, significantly reducing resolution times and improving agent efficiency. By analyzing keywords and categories within the record, Agent Assist aims to anticipate the agent's needs and surface potential solutions directly.
Option A, Chat Bot, while helpful in self-service scenarios, doesn't automatically provide search results based on open records within the Agent Workspace in the same manner. Chatbots typically require user interaction to trigger searches.
Option B, Related Search Results, is a general term but doesn't capture the proactive and automated nature of Agent Assist within the Workspace. Agent Assist proactively pushes contextually relevant information rather than merely providing a standard search feature.
Option C, Knowledge Bases, represent the repository of information, but by themselves, they do not provide the automatic and targeted search results. Agent Assist leverages Knowledge Bases (and other sources) as part of its solution delivery.
Option D, Intelligent Agent, is a broader concept that encompasses various AI-powered capabilities.
While Agent Assist is powered by intelligence, "Intelligent Agent" is not the specific feature providing automatic search results within the Agent Workspace.
Agent Assist promotes first-call resolution, reduces training time for new agents, and enhances the overall customer experience by enabling agents to quickly access relevant information and resolve issues efficiently.
For further research, refer to ServiceNow's official documentation on Agent Assist: https://docs.servicenow.com/bundle/utah-now-intelligence/page/administer/agent-assist/concept/agent-assist-overview.html and https://www.servicenow.com/content/dam/servicenow/other-documents/service-brief/sb-agent-workspace.pdf



Which capability provides visibility to data joined between multiple tables?

  1. Database Views
  2. Metric Tables
  3. Published Reports
  4. Custom Tables
  5. Breakdown Sources

Answer(s): A

Explanation:

The correct answer is A. Database Views .
Database views in ServiceNow (and in general database management) provide a way to join data from multiple tables and present it as a single virtual table. This is crucial for creating consolidated reports and gaining a comprehensive understanding of relationships between data across different entities. They don't store data themselves; they are constructed from the underlying tables based on defined relationships (joins). This allows users to query and report on data that spans multiple tables as if it were a single entity, greatly simplifying reporting and analysis. Using a view hides the complexity of the underlying table structures and the join operations from the end-user.
Option B, Metric Tables, are used for measuring and tracking the effectiveness of IT processes over time but don't provide visibility into joined data from various tables in the same way as database views. Metric tables record measurements like resolution time and cost.
Option C, Published Reports, while displaying data from multiple tables, relies on an underlying data source, which could be a database view, and doesn't inherently provide the join mechanism itself. Reports use data from a single table or a table joined using a database view.
Option D, Custom Tables, are used to store new data, not to view joined data from existing tables. They simply store data defined by the user.
Option E, Breakdown Sources, define how data in indicator sources will be broken down for performance analytics and do not directly combine data from different tables for general reporting purposes.
Therefore, database views are specifically designed to create a single, unified view of data from multiple tables, making them the correct solution for the described capability.
Refer to ServiceNow's documentation on database views for more detailed information:
ServiceNow Docs: Database Views



What tools are available to the assignee to help resolve an Incident? (Choose two.)

  1. Knowledge Articles
  2. Workarounds
  3. CI Class Manager
  4. Incident Overview Dashboard
  5. Enterprise CMDB Dashboard

Answer(s): A,B

Explanation:

The correct answer is A. Knowledge Articles and B. Workarounds . Here's why:
Knowledge Articles: These are documented solutions to common problems or recurring issues.
When an Incident is assigned, the assignee can search for relevant knowledge articles to see if the problem has been previously resolved. Knowledge articles provide a readily available resource to quickly address known issues and standardize resolution processes. ServiceNow's Knowledge Management application directly integrates with Incident Management, facilitating this process.
Workarounds: A workaround provides a temporary solution to bypass an immediate problem, allowing the user to continue working until a permanent fix is implemented. Offering a workaround is a crucial step in incident resolution, especially when the root cause is unknown or the permanent fix requires significant time. Assignees can document and share workarounds through the incident record, improving user experience and minimizing disruption.
Why the other options are not the best choices:
C: CI Class Manager: CI Class Manager is primarily used for defining and managing the attributes of Configuration Items (CIs) within the CMDB. While a correctly configured CMDB is valuable for Incident Management (understanding dependencies etc), the CI Class Manager itself isn't a direct tool to resolve an individual incident.
D: Incident Overview Dashboard: Incident Overview Dashboards provide a high-level view of incident metrics, trends, and performance. They are valuable for managers and analysts to monitor the overall incident management process. But, they don't give direct tools or methods for solving an individual incident for the assignee working on the specific problem.
E: Enterprise CMDB Dashboard: The Enterprise CMDB Dashboard offers a broad overview of the Configuration Management Database (CMDB). Although understanding the relationships between CIs (which the CMDB dashboard helps with) can be useful in incident investigation, the dashboard itself doesn't offer tools to directly solve incidents. The assignee may indirectly use the information from the CMDB to understand dependencies or identify problematic CIs, but this is not a direct resolution tool.
In summary, knowledge articles offer previously documented solutions, and workarounds provide temporary solutions. Therefore, these are the tools most directly applicable to resolving an assigned incident.
Authoritative Links:
ServiceNow Documentation: https://docs.servicenow.com/ ServiceNow Knowledge Management: https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/product/knowledge-management/concept/knowledge-management.html ServiceNow Incident Management: https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/incident-management/concept/incident-management.html



When using Inbound Email Actions, what happens if an email is received which has no watermark or reference number?

  1. New incident created from the message
  2. New interaction is created from the message
  3. Email is rejected and auto-reply sent to sender
  4. New case is created from the message

Answer(s): A

Explanation:

Here's a detailed justification for why option A, "New incident created from the message," is the most likely outcome when an email with no watermark or reference number is processed by ServiceNow's Inbound Email Actions within the context of IT Service Management (ITSM).
ServiceNow Inbound Email Actions are configured to process incoming emails and perform specific actions based on defined conditions. The presence of a watermark or reference number is a crucial condition often used to identify an email as related to an existing record (like an incident, change request, etc.). If an email lacks these identifiers, ServiceNow's default behavior in a standard ITSM implementation is usually to create a new incident.
This behavior is driven by the need to address potentially new issues or requests raised by users. Without a watermark, the system cannot associate the email with any existing record, so it assumes it's a new request for assistance. This aligns with the core purpose of ITSM: to efficiently manage and resolve IT service requests. The alternative options of creating an interaction or a case are less common defaults for general IT-related emails; incident creation directly addresses potential IT disruptions. Rejecting the email (option C) would be undesirable as it could result in a user's issue going unaddressed.
The specific behavior depends on the configurations of your ServiceNow instance and the existing Inbound Email Actions. ServiceNow administrators can customize these actions extensively, including setting different default behaviors for emails lacking watermarks. However, creating a new incident is the most logical and generally configured default action in the absence of other identifying information within a typical ITSM setup. This ensures that potential IT problems reported via email are logged and addressed.It's crucial to review your specific ServiceNow instance's Inbound Email Actions to confirm the precise behavior.
For more information on ServiceNow Inbound Email Actions, you can refer to the official ServiceNow documentation:
ServiceNow Docs: Inbound Email Actions
ServiceNow Community: Inbound Email Troubleshooting



Viewing page 3 of 32
Viewing questions 11 - 15 out of 248 questions


Post your Comments and Discuss ServiceNow CIS-ITSM exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!