Which workflow is defined as: Requests approval from a manager of the knowledge base before moving the article to the retired state. The workflow is canceled and the article remains in the published state if any manager rejects the request.
Answer(s): C
The correct answer is C. Knowledge – Approval Retire . Here's a detailed justification:The scenario describes a process where retiring a knowledge article requires explicit approval from a knowledge base manager. This aligns perfectly with a workflow named "Knowledge – Approval Retire." This workflow implies a deliberate approval step before the article's state is changed to "retired." The description emphasizes that the workflow is stopped if a manager rejects the request, leaving the article in the "published" state, which further solidifies the "Approval" element's importance.Let's analyze why the other options are less suitable:A: Knowledge – Article Retire: This is too general. It doesn't necessarily imply an approval step. B. Knowledge – Retire Authorize: This is close but less descriptive than "Approval Retire." Authorization could be a preliminary check, while "Approval" directly implies a decision-making gate. D. Knowledge – Retire-Approval Required: While similar in meaning, the standard ServiceNow naming conventions often use a more concise format like "Approval Retire." E. Knowledge – Instant Retire: This is the opposite of what's described. It suggests no approval is needed.The "Knowledge – Approval Retire" workflow captures the essence of requiring explicit approval from a manager to move an article to the retired state. A typical workflow will consist of conditions that need to be met, approvals that must be provided and activities that need to be completed. The scenario describes the approval requirement as well as the condition when the approval is rejected, indicating the state of the article.For further reading on ServiceNow workflows and knowledge management, refer to these resources:ServiceNow Documentation on Workflows: https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/workflow/concept/workflow-activities.html ServiceNow Documentation on Knowledge Management: https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/product/knowledge-management/concept/knowledge-management.html
What Knowledge base feature can you use to standardize the sections and fonts on a knowledge article?
The correct answer is C. Templates are the best way to standardize the sections and fonts in knowledge articles within ServiceNow. Knowledge templates provide pre-defined structures and formatting styles that ensure consistency across all articles created using that template. They allow administrators to define the sections, fields, and even the visual appearance (fonts, colors, etc.) for new articles, making article creation more efficient and guaranteeing a uniform look and feel. Using templates, authors can easily populate the pre-defined fields and sections, eliminating the need to manually configure the article structure each time. This saves time and ensures that critical information is always presented in a standardized way.Option A, Article Designer, while a valid ServiceNow feature, focuses on the overall visual customization of the Knowledge base portal itself, rather than the internal formatting of each knowledge article. Option B, Coaching Loops, relates to improvement processes and is irrelevant to knowledge article formatting. Option D, Article Layout is not a standard ServiceNow feature. The primary mechanism for dictating the structure and appearance within the content of an article itself, using consistent formatting, is through the implementation of templates. Therefore, selecting templates to ensure consistency is the ideal approach to address the question. The uniformity achieved by templates improves the user experience by making it easier for users to find and consume information. Templates also enable the creation of specialized knowledge bases (e.g., for specific audiences or problem types), with their own distinct structure and style.Further research can be found on ServiceNow's official documentation:ServiceNow Knowledge Management: https://docs.servicenow.com/bundle/utopia-platform/page/product/knowledge-management/concept/knowledge-management.html Creating a Knowledge Article Template: https://docs.servicenow.com/bundle/utopia-platform/page/product/knowledge-management/task/t_CreateAKnowledgeArticleTemplate.html
Which of the following roles has the ability to create and manage user criteria for service catalogs?
Answer(s): A
The correct answer is A. catalog_admin .Here's why:catalog_admin: This role grants comprehensive administrative rights over service catalogs, including managing user criteria. This is a central responsibility for configuring who can access and request items within the service catalog. It's a powerful role intended for those responsible for the overall structure and management of service catalogs. catalog_manager: This role primarily focuses on the content and structure of the service catalog itself, like categories, catalog items, and workflows. While they may use user criteria in the context of catalog items, they typically don't have the explicit right to create and manage the criteria itself. itil_admin: This role oversees the broader ITIL processes within ServiceNow. While they may have access to many areas, the specific task of managing service catalog user criteria falls more directly under catalog administration. catalog_criteria_admin/catalog_criteria_manager: These are not standard roles that come out-of-the-box with ServiceNow. Creating roles with the "_admin" or "_manager" suffix does not inherently grant permissions.In ServiceNow, effective role management involves assigning roles that grant the least privilege necessary to perform a specific task. Because catalog_admin has the explicit right to create and manage the user criteria lists for catalogs, it's the most appropriate role for that specific task.Justification:ServiceNow utilizes a role-based access control (RBAC) system to manage user permissions. The catalog_admin role encapsulates the necessary permissions to govern all aspects of service catalogs,including defining and controlling who can access which catalog items through user criteria. User criteria are essential for tailoring the service catalog experience based on roles, departments, locations, or other attributes. Proper user criteria ensure that users only see relevant services, reducing clutter and improving self-service efficiency. The responsibility for creating and maintaining these criteria is a fundamental part of catalog administration.Authoritative Links:ServiceNow Docs on Roles: https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/roles/concept/c_Roles.html ServiceNow Docs on Service Catalog User Criteria: https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogUserCriteria.html
Which catalog property allows users to save partially-completed requests to complete and submit at a later time?
Answer(s): B
The provided answer "B. Enable wish list" is incorrect. The correct answer is "C. Enable cart save".Here's a detailed justification:The functionality to save partially completed service catalog requests for later completion is directly related to the service catalog's "cart" feature. The "cart" is where users collect items (service catalog requests) before submitting them. Enabling a "cart save" property specifically allows users to save the contents of their cart, including partially filled-out request forms, and return to them at a later time to finish and submit.Options A, B, and D are incorrect because they do not directly enable the saving of partially completed requests. "Edit cart layout" controls the visual presentation of the cart, not its save functionality. "Enable wish list" allows users to save catalog items for future reference or purchase, which is distinct from saving an incomplete request. "User partial save" is not a standard property name related to cart functionality in ServiceNow's ITSM module.The "glide.sc.use_cart_layouts" property, while related to the cart layout feature, is not the specific property required to enable saving partially completed requests for later. There is no official "User partial save" property in the base ServiceNow ITSM catalog configuration.The ServiceNow documentation provides details on configuring various aspects of the service catalog, including the cart functionality. Searching for "ServiceNow cart save" or "ServiceNow service catalog save incomplete request" within the ServiceNow documentation or community forums will yield specific articles describing the cart save functionality and how to enable it. While a direct link confirming a property named "Enable cart save" may not exist in the documentation (as property names can vary and depend on specific ServiceNow versions or customizations), the concept and behavior are widely discussed within the ServiceNow community and are enabled via appropriate cart configuration and system properties. The precise property will depend on the ServiceNow version. Therefore, the most accurate description for enabling the required feature is generally referred to as a "cart save" capability.In conclusion, the feature that empowers users to save incomplete service catalog requests resides within the cart's functionalities, primarily enabled by a "cart save" mechanism. The core idea of a "cart save" is what allows saving progress.
Once a Catalog Item has been requested, what mechanism determines the approvals, and tasks that are triggered in the application?
The correct answer is B. Flows . Here's a detailed justification:ServiceNow leverages its Flow Designer to automate complex workflows across the platform, including those associated with Catalog Item requests. Flows provide a visual, no-code/low-code environment for defining sequences of actions and approvals that are triggered when a Catalog Item is requested. They essentially orchestrate the request fulfillment process.When a user submits a Catalog Item request, the system examines the defined Flow associated with that item(or potentially, a Flow triggered by a broader workflow). The Flow dictates the sequence of events, starting perhaps with approval requests, and then leading to the creation of tasks like incidents, changes, or fulfillment requests. Flows can evaluate conditions to branch the workflow, ensuring specific actions are taken based on input variables or pre-defined logic.Processes (A), while related to workflows, is a broader term and doesn't directly equate to the specific automated mechanism used for Catalog Item fulfillment in ServiceNow. Procedures (C) suggest a set of instructions but lack the automation capability. Actions (D) are individual components within a Flow, not the overall orchestrator. Scripts (E) can be used within Flows, but the primary mechanism is the Flow itself. The visual nature and ease of use provided by Flows are key reasons for their prevalence in ITSM implementations within ServiceNow. Using Flows allows for better maintainability and transparency of workflows compared to relying solely on scripts.Flows can also integrate with other modules within ServiceNow, such as service level management (SLAs), further streamlining the overall ITSM process. In conclusion, Flows are the primary engine for automating the approvals and task generation associated with Catalog Item requests in ServiceNow's ITSM module.Authoritative Links:ServiceNow Documentation on Flow Designer: https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/flow_designer/concept/flow-designer.html ServiceNow Developer Site on Flow Designer: https://developer.servicenow.com/dev.do#!/learn/courses/quebec/automation_engine_fundamentals/AEF-flow-designer/AEF-flow-designer_introduction
Unless there are particular security requirements, what role is given to users that perform request fulfillment work?
The correct answer is A. itil .Here's why:The ITIL (Information Technology Infrastructure Library) role in ServiceNow is a core, foundational role granting users the ability to perform a wide variety of IT service management tasks, including request fulfillment. It provides the necessary permissions to access, update, and manage records across multiple ITSM modules.The itil role is designed to align with ITIL best practices for service management. Request fulfillment, a key component of ITIL, involves handling user requests for standard services and items. Users with the itil role can access request records, complete tasks associated with fulfilling those requests, and generally manage the request lifecycle.While sc_fulfiller (Service Catalog Fulfiller) does relate to fulfillment, it's more narrowly focused on fulfilling items ordered through the service catalog. The itil role provides broader access across the entire ITSM suite,encompassing request fulfillment beyond just the service catalog. The other roles, task_worker ,catalog_fulfiller , and fulfiller are not standard, out-of-the-box ServiceNow roles directly associated with fulfilling requests in a general ITSM context without additional customization. Unless very granular security and access control are required, assigning users the itil role provides the necessary permissions for request fulfillment work. The goal is to provide the appropriate access level to efficiently manage and resolve requests while adhering to ITIL principles.For further research, refer to the official ServiceNow documentation on roles and access control:ServiceNow Docs - Roles: https://docs.servicenow.com/bundle/quebec-platform-administration/page/administer/roles/concept/c_Roles.html ServiceNow Docs - ITIL Role: https://docs.servicenow.com/bundle/quebec-it-service-management/page/product/incident-management/concept/c_ITILRole.html (Although this link directs to Incident Management documentation, the explanation regarding the itil role still applies generally acrossITSM).
Your customer is a data center. They have a construction department that builds out spaces for new customers. The customer account representatives are responsible for initiating the construction requests. The guidelines are extensive for how to complete the construction request documentation. Your customer wants the catalog to contain two items: 1. Construction request 2. Getting Started with Construction Requests The Getting Started Item should contain a link to a Knowledge Article. What type of item would you use to satisfy the requirement for the Getting Started Item?
The correct answer is C. Content Item . Here's a detailed justification:The requirement is for an item that provides information and a link to a Knowledge Article, specifically "Getting Started with Construction Requests". A Content Item is specifically designed for this purpose within the ServiceNow catalog. Content Items allow you to display static information, embed links (including links to Knowledge Articles), and present guidance without initiating a workflow or process.Here's why the other options are less suitable:A: Knowledge Item: This isn't a standard item type in ServiceNow. It might refer to a specific implementation, but generally, Knowledge Articles are linked to catalog items, not the other way around as the primary functionality. B. Record Producer: Record Producers are used to create records in ServiceNow tables (e.g., incidents, requests). They're meant to capture user input and generate new data entries. They are inappropriate for providing informational guidance. D. Order Guide: Order Guides help users select multiple related catalog items. They guide users through a selection process for related services or products, and are not primarily intended for providing documentation. E. Catalog Item: While you could technically create a catalog item with instructions and a link, it's overkill. A full catalog item implies a requestable service, which "Getting Started" is not. It creates unnecessary complexity.A Content Item is the leanest and most appropriate way to provide users with the requested information and link to the relevant Knowledge Article within the service catalog. It provides easy access to documentation without triggering any unnecessary workflows or record creation, improving the overall user experience.Authoritative Links:ServiceNow Documentation - Content Management System (CMS): https://docs.servicenow.com/bundle/sandiego-content-management/page/build/service-portal/concept/sp-content-blocks.html (While this link focuses on Service Portal, the concept of content items and their use for displaying static information and links is analogous to the Service Catalog) ServiceNow Community Forums: Search the ServiceNow Community for "Content Item in Service Catalog" to find real-world examples and discussions.
What is an example of a good use case for an Order Guide?
The best use case for an Order Guide from the provided options is A. Order a set of Dishes. Here's why:An Order Guide in ServiceNow is designed to simplify the process of ordering multiple related items or services that are often requested together. It streamlines the process by presenting a single interface with categorized questions. Based on the answers provided by the user, relevant catalog items are automatically added to the cart.Option A, "Order a set of Dishes," fits this paradigm perfectly. A "set of dishes" could involve multiple items like plates, bowls, cups, and silverware. An Order Guide could present questions regarding the desired number of place settings, the style (casual, formal), or the material (ceramic, glass). Based on these selections, the appropriate individual catalog items for each dish type and quantity would be automatically added to the user's cart as a single request.Options B, C, and D are less suitable. "Order a Custom Automobile" is typically a complex configuration process handled through a dedicated, bespoke application or system (like a CPQ - Configure, Price, Quote system) that goes far beyond the capabilities and intended use of an Order Guide. "Order a Technical Consultation" usually involves booking a single service and doesn't necessitate guiding the user through a selection of multiple related items. “Order a Couch” while simpler, would generally consist of a single catalog item representing the couch itself, possibly with options like fabric choice. There isn’t a natural, multi-item selection process an Order Guide would significantly streamline. "Order a case of Laundry Soap" is also a single item request and does not fit the multi-item, related items nature of Order Guides.Therefore, ordering a set of dishes is the best example since it allows the user to request multiple related items (plates, bowls, cups, silverware) through a single, guided order process, which is the core function of an Order Guide. The guided questions help the user determine which individual items need to be included in the order based on their specific needs, mirroring the intended purpose of the Order Guide feature within ServiceNow.ServiceNow Documentation on Order Guides
Post your Comments and Discuss ServiceNow CIS-ITSM exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CIS-ITSM content, but please register or login to continue.