Your customer has a catalog item for Request VPN. They would like to adjust the cart layout for only the VPN item, so the Quantity field is not displayed. How would you meet this requirement?
Answer(s): C
The correct answer is C: On the Catalog Item, Advanced View, unselect Use cart layout, select No quantity.Here's why: The requirement is to modify the cart layout specifically for the "Request VPN" catalog item, and the objective is to hide the Quantity field. Option A is incorrect because modifying the Cart Layout directly affects all catalog items, which does not meet the item-specific requirement. Option B attempts to modify layout using columns tab on catalog item, and it does not contain quantity column. Option D refers to catalog settings which affect the whole catalog, not a particular catalog item. Option E would also attempt to modify layout using related list, and it is not the way to proceed.The "Use cart layout" setting on the catalog item determines whether to use the global cart layout settings. By unchecking this, you gain the ability to customize the cart layout for that particular item. Then, selecting "No quantity" will ensure the Quantity field is not displayed in the cart for the "Request VPN" catalog item. This approach satisfies the requirement by making the changes only to the specific catalog item, avoiding a global modification to all catalog items' cart layouts. The advanced view provides granular control over catalog item settings.
A manager wants to run a report on the Computer catalog items, to see how many requests are being made for the add on extra memory, as compared with those requiring only the base memory. How would you meet this requirement?
Answer(s): B
The correct answer is B: Build report on Requested Item table, Group by Variables for Computer > Extra memory. Here's why:Requested Item (RITM) Table: This table stores the individual items requested from a service catalog within a Request. Each item requested from the catalog is represented as a record in the RITM table. This is the appropriate level to report on individual catalog items.Variables: Catalog items often have variables that allow users to customize their request (e.g., selecting memory size). The data entered into these variables is stored with the RITM record.Grouping by Variables: To compare requests for extra memory versus base memory, you need to group the report by the "Extra memory" variable associated with the "Computer" catalog item. This will aggregate and count requests based on the selected memory option.Now let's examine why the other options are incorrect:A: SC Task Table: SC Task (Service Catalog Task) represents tasks generated as part of the fulfillment workflow for a requested item. While tasks might be related to memory configuration, reporting on the RITM itself is more direct for determining the initial request. C. Task Table: The Task table is too broad. It includes all types of tasks in ServiceNow (Incident, Change, Problem, etc.). It would be difficult to isolate the data relevant to service catalog requests for computers. D. Request Table: The Request table represents the overall request container. It doesn't contain the detail of the individual items requested. It would be inappropriate to report on the individual variable selection for the computer catalog item. The Request would include potentially multiple requested items. E. Catalog Item Table: The Catalog Item table contains information about the catalog items themselves (description, price, etc.), not about the individual requests for those items. It wouldn't contain information about the variable choices made by users when requesting the item.In summary, reporting on the Requested Item (RITM) table and grouping by the relevant variable ("Extra memory") provides the necessary aggregation and data to analyze the request patterns for different memory configurations in the computer catalog item.
ServiceNow Docs: https://docs.servicenow.com/ (Search for "Requested Item table" or "Service Catalog reporting")
Which record type would you use for an Ask a Question form that would generate an Incident?
Answer(s): A
The correct answer is A, Record Producer. Here's a detailed justification:A Record Producer is designed specifically to create records in other tables from a catalog item like request. It provides a user-friendly interface to capture necessary information and then uses that information to create a specific type of record such as an Incident, Problem, Change, or Request. This aligns perfectly with the scenario of an "Ask a Question" form generating an Incident. The Record Producer can be configured to map the answers from the form directly into the Incident fields.Order Guides are used to bundle related catalog items together to fulfill a request. They are not ideally suited for directly creating Incident records from a form. While an order guide could include an item that creates an incident, it's not the primary purpose.Linked Items refer to connections between catalog items or knowledge articles, allowing users to navigate related content. This does not create a record on its own.Catalog Items encompass a broader range of offerings available in the service catalog, including hardware, software, and services. While an Incident could technically be created from a specific type of catalog item via workflow or script, Record Producers are more efficient and tailored to the task of transforming form data into specific record types.Content Items are used for displaying information such as articles, banners, or static content within the service portal. They don't facilitate record creation.Record producers offer a simplified and streamlined approach for creating new records such as Incidents from a front-end user interface. Using a record producer ensures that necessary fields are populated and actions are triggered based on the user input. This approach also ensures that the data structure and business rules of the target table (in this case, the Incident table) are respected. This is generally regarded as a best practice when creating records programmatically or via user interaction.In contrast, using workflows connected directly to a Catalog Item to generate Incidents is generally more complex and less intuitive than leveraging Record Producers which were specifically designed for this purpose.For further information, refer to the official ServiceNow documentation:ServiceNow Product Documentation - Record Producer ServiceNow Product Documentation - Service Catalog
Which of the following objects on the Shopping Cart Widget can be displayed or hidden using Maintain Cart Layouts settings? (Choose two.)
Answer(s): A,C
The correct answer is A. Quantity and C. Price. The "Maintain Cart Layouts" functionality within ServiceNow's Service Catalog settings allows administrators to control the visibility of certain elements within the shopping cart widget, specifically tailoring the user experience. This is valuable for simplifying the cart and removing unnecessary information based on the organization's needs."Quantity" is frequently displayed on the shopping cart widget to show the number of units or instances of a catalog item that a user is requesting. The "Maintain Cart Layouts" configuration allows an admin to hide or show the quantity field if deemed unnecessary, perhaps when items are always ordered individually, reducing clutter for the end-user.The "Price" of items in the shopping cart is also a key element controlled via "Maintain Cart Layouts". An organization might choose to hide prices from the user's shopping cart if approval workflows always determine the final cost. The configuration is crucial to managing what is being displayed.Conversely, "Requested By" (B) and "Shipping Address" (D) are managed differently. The "Requested By" field is generally tied to the user's identity through the session and is not something dynamically shown or hidden through the Cart Layouts. The "Shipping Address" is normally determined through configuration elsewhere in the system, for instance, set to be the end user's default location.Therefore, because "Maintain Cart Layouts" is meant for managing elements like "Quantity" and "Price" for each item, these options allow the administrators to configure the shopping cart widget to be simplified and reduce the amount of information displayed.For further information, refer to the official ServiceNow documentation on Service Catalog configurations and Cart Layouts:ServiceNow Product Documentation: (Requires ServiceNow login) - Search for "Maintain Cart Layouts".
Your customer wants a catalog to contain two items: 1. A request with 1 approval and 2 fulfillment tasks 2. A link to a knowledge article What type of item would you use to satisfy the requirement for the Construction request?
The correct answer is A. Catalog Item . Here's why:A Catalog Item is the most appropriate choice for fulfilling the requirement of creating a service request process involving approvals and fulfillment tasks. Catalog Items are designed to represent goods or services that users can request through the service catalog. They can be configured with workflows that define the approval process and generate associated tasks.Here's a breakdown of why the other options are less suitable:B: Content Item: Content Items are used primarily for displaying information, such as links to knowledge articles or external websites. While one requirement involves linking to a knowledge article, a Content Item doesn't provide a mechanism for triggering a request, approval process, or task creation. They are for delivering information, not for managing a service request lifecycle.C: Record Producer: Record Producers are used to create records in a table, such as incident, change, or problem records. They are typically used to capture information from users in a simplified form and then create the corresponding record. While a Record Producer could be used, it's less flexible and less suited for handling the complexities of approvals and multiple fulfillment tasks.D: Order Guide: Order Guides are used to bundle multiple Catalog Items together. While the customer wants two different items, the Catalog Item can't be fulfilled through an Order Guide.In summary, a Catalog Item gives the administrator the capacity to setup workflows with approvals and fulfillment activities. Furthermore, the customer has two requests. One is fulfilled through approvals and fulfillment tasks. Another to link to a knowledge article.
ServiceNow Documentation on Catalog Items: https://docs.servicenow.com/en-US/bundle/sandiego-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogItems.html
When building multiple catalog items, which components would you evaluate for consolidation and re-use? (Choose two.)
Answer(s): A,D
The correct answer highlights two key components for consolidation when building multiple catalog items in ServiceNow ITSM: Sets of Variables and Flows and Subflows.Let's justify each choice:Sets of Variables: Catalog Items often require similar data input. Instead of defining the same variables repeatedly for each item, grouping commonly used variables into "Variable Sets" promotes reusability. This standardization simplifies maintenance, ensures data consistency, and reduces development effort. Changing a variable in a single set automatically updates all catalog items that use it, which is more efficient than updating each catalog item individually.Flows and Subflows: IT service processes often involve repeatable workflows, such as approvals, task assignments, and notifications. Building these processes as reusable Flows (or smaller modular Subflows) inFlow Designer avoids duplication. Catalog Items can then trigger these standardized flows. If there is a change in a flow, it can be done in one place which reduces change impact and ensures consistent processes across all requests and incidents.Why the other options are less suitable for consolidation at the same level:Entitlements: Entitlements control who can access a catalog item. While access control is important, consolidating entitlements is less about streamlining content creation and more about managing user access rights.Icons: While using consistent icons is important for aesthetics and user experience, the primary focus for catalog item consolidation should be on the underlying data and process definitions that govern the service request.In summary, focusing on reusing Variable Sets and Flows/Subflows directly streamlines the building and maintenance of catalog items by minimizing redundant configurations and process definitions.Supporting Links:ServiceNow Documentation - Variable Sets: https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/service-catalog-management/concept/c_VariableSets.htmlServiceNow Documentation - Flow Designer: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/flow-designer/concept/flow-designer.html
Which record type would you use for a Computer request?
The correct answer is B, Catalog Item. Here's why:Catalog Items are the fundamental building blocks for creating requests within the Service Catalog in ServiceNow. They represent specific goods or services that users can request, such as computers, software, or network access. The ServiceNow Service Catalog acts as a self-service portal that provides a user-friendly interface for ordering services.A Computer request is a specific, tangible item (hardware) that a user needs. Therefore, a Catalog Item is the most appropriate record type to define the details of this request, including the computer type, specifications, optional accessories, and associated workflows for approval and fulfillment.Record Producers, on the other hand, are designed for creating records in specific tables (like Incident or Problem) from the Service Catalog. They are used for reporting incidents or requesting assistance rather than ordering physical items. While a Record Producer could theoretically be used, it’s less suited for requests involving workflows, pricing, and fulfillment tied to a specific item.Order Guides bundle multiple Catalog Items together into a single request. They are useful when a user needs a combination of services, for example, onboarding a new employee who needs a computer, software, and network access. An Order Guide leverages Catalog Items; it doesn't replace them.Content Items are used for informational purposes within the Service Catalog, such as FAQs, guides, and announcements. They do not initiate requests for services or goods.Therefore, for a straightforward request for a Computer, a Catalog Item provides the necessary framework to define the item, manage the request process, and track fulfillment, making it the correct choice.Further research on Catalog Items can be found on the ServiceNow documentation site:Service Catalog Create a catalog item
What are the different ways a user can locate items in a service catalog? (Choose two.)
Answer(s): A,B
The correct answer identifies two primary methods for users to find items within a ServiceNow service catalog: using the search functionality and navigating through defined categories.Option A, "Use the search on catalog or portal," is correct because ServiceNow provides a search feature that allows users to enter keywords related to the desired service or item. This search functionality scans item names, descriptions, and potentially other metadata to return relevant results. This is a common and efficient way to locate specific items when the user knows what they're looking for, mirroring search functionality on e-commerce sites or internal knowledge bases.Option B, "Navigate through the categories," is also correct. Service catalogs are structured using categories and subcategories, logically organizing services. Users can browse these categories to find items related to a particular area, such as hardware, software, or IT support. This hierarchical structure enables users to discover services they might not have known existed and aligns with best practices for information architecture and user experience.Option C, "Use the Top Request or Popular Items widget," is incorrect. While helpful for identifying commonly requested items, this widget primarily showcases popular or frequently requested services, rather than providing a comprehensive search or navigational tool to locate all available items. It's a recommendation feature, not a discovery mechanism.Option D, "Use the application navigator," is incorrect. The application navigator is for navigating within the ServiceNow platform itself (accessing different modules like Incident, Change, Problem), not for finding items within the service catalog, which resides within the Service Portal or Catalog itself.In summary, search functionality and category navigation are the core mechanisms for users to actively locate items within a service catalog. Other features, like popular items or top requests, are supplementary aids for item discovery but not primary means of item location.Further research on ServiceNow Service Catalog features can be found at:ServiceNow Product Documentation: https://docs.servicenow.com/
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.