CIS-ITSM Certified Implementation Specialist - IT Service Management Questions and Answers

Detailed Explanation:

The portfolio_admin role in ServiceNow has the necessary permissions to create service portfolios and manage taxonomy nodes. This role provides the highest level of access for managing the structure and content of service portfolios, enabling the user to organize services and offerings in a way that aligns with business goals.

Documentation reference: Service Portfolio Management Roles.

What tools are available to the assignee to help resolve an incident?

Choose 2 answers

A. Resolutions from similar incidents

B. Known Errors

C. CI Class Manager

D. Enterprise CMDB Dashboard

E. Incident Overview Dashboard

From which table, is the Incident table extended?

A. Work [sn_work]

B. Ticket [ticket]

C. Task [sn_task]

D. Task [task]

Answer: D

Change Request [change_request]

Problem [problem]

Incident [incident]

Request [sc_request]

Request Item [sc_req_item]

Service Catalog Task [sc_task]

all extended from task

In ServiceNow ' s Problem Management application, state transitions and their associated logic are governed by Script Includes. Following ServiceNow ' s architectural best practices, the logic is split into two parts:

ProblemStateUtilsSNC: This contains the read-only, " out-of-the-box " (OOTB) logic provided by ServiceNow.

ProblemStateUtils (B): This script include extends the SNC version and is intended for customer customizations.

If an administrator needs to add a custom pre-requisite (such as ensuring a specific field is filled or a related record is closed) before a problem can move out of the Fix in Progress state, they must modify the ProblemStateUtils script. This ensures that their changes are preserved during platform upgrades.

ServiceNow Service Portfolio Management primarily manages Business Services and Application Services. A Business Service refers to services that support business processes or provide value to the customer, while Application Services are services provided by software applications. These services are tracked and managed to ensure they align with organizational objectives. Mobile Service and Technical Service are more specialized or less commonly grouped within the Service Portfolio scope.

Refer to Service Portfolio Management for further understanding.

In ServiceNow IT Service Management (ITSM) , the Service Catalog is a central repository of goods and services available to users. While a catalog is organized by Categories (A), categories themselves are containers, not items. Execution Plans (C) are legacy mechanisms used to define processes, and Requested Items (D) are the specific instances of an order after it has been placed (stored in the sc_req_item table).

A Record Producer (B) is a specific type of catalog item that allows users to create task-based records, such as Incidents or Change Requests, directly from the Service Catalog. Unlike standard catalog items that result in a Request ( sc_request ), a Record Producer uses a simplified interface to gather information and map it to fields on a target table, making it a fundamental component of the Service Catalog ecosystem.

Detailed Explanation:

The Editors field in ServiceNow Service Catalog creation specifies who has permissions to create, modify, and publish items within the catalog. Editors have the rights to manage the content and structure of the catalog, ensuring that only authorized users can perform these actions.

For details, refer to the Service Catalog Management documentation.

In Change Management , specifically when using the Change Model framework (introduced in the Rome release to provide more flexibility than legacy workflows), state transitions are governed by specific conditions. For a Change Request to move from the Authorized state (where it has been vetted by the CAB or technical leads) to the Scheduled state (where it is ready for implementation), the system must verify that the necessary approvals have been granted. Therefore, the " Requires " field is set to Task is Approved to ensure that the transition only occurs once the approval engine returns a positive result.

Step by Step Comprehensive Detailed Explanation: In the context of ServiceNow IT Service Management, specifically within the service portfolio taxonomy, a ‘leaf node’ can be associated with a service. The service portfolio taxonomy is a hierarchical structure that organizes the services offered by an organization. At the top of this hierarchy are broad categories or ‘nodes,’ which are then broken down into more specific ‘leaf nodes.’ These leaf nodes represent individual services or offerings that are the most granular level within the taxonomy. Associating a service with a leaf node allows for detailed tracking and management of that particular service within the larger portfolio.

Content Items may be used for multiple purposes:

- Link to a Knowledge Base Article (policy articles, articles providing additional information about items)

- Link to catalog content (cross-references amongst catalogs)

- Link for a Module (redirect user to the same target location specified in a navigation module)

- External Content (link to public website or internal portal)

According to the product documentation of ServiceNow1, the definition of what is provided, or not provided, for a service is defined in the service scope. The service scope is a document that describes the features, functions, and boundaries of a service, as well as the roles and responsibilities of the service provider and the customer1. Therefore, the correct answer is B. Service scope.

In the standard ServiceNow security model for ITSM, the ability to delete records is highly restricted to prevent data loss and maintain the audit trail. While the itil role allows users to create and update incidents, and the incident_manager role allows for the oversight of the incident process, neither has the out-of-the-box permission to delete Incident records. The itil_admin role is specifically designed to grant elevated permissions—including the deletion of incidents—without requiring the full system admin role. This ensures a " least privilege " approach while still allowing administrative cleanup of the Incident table.

To satisfy the requirement of identifying which knowledge base articles are visible to the callers from the Incident form, the feature ‘Show User Viewable’ would be used. This feature allows agents to see which articles can be viewed by the user associated with the incident. It helps in distinguishing between articles that are meant for internal audiences (technical) and those written for end users with simpler instructions. When an agent is on the Incident form, they can use this feature to filter and display only the articles that the caller can view, ensuring that the agent is aware of the information available to the caller and can guide them accordingly.

Detailed Explanation:

A Portfolio Manager in ServiceNow focuses on the Service Portfolio, which includes all the services provided by an organization. The Portfolio Manager oversees how the Service Offering and the Service within this portfolio perform, ensuring that they align with business objectives. The hierarchy in question, Service Portfolio > Service > Service Offering, is crucial for understanding the overall performance and governance of services. This hierarchy provides a structured approach to managing services from a business perspective and tracking their lifecycle.

ServiceNow Documentation on Service Portfolio Management.

Automatically populate the Assignment group field based on the support group available for the respective CI. If the CI does not have a support group, then the field gets populated with the support group available for the service offering.

https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/service-catalog-management/concept/catalog-items-wishlist.html