ServiceNow CIS-HAM Practice Test - Questions Answers, Page 16

Stock rules are rules that define the minimum and maximum quantities of assets that should be maintained in a stockroom1.

Automatic restocking actions are actions that trigger the creation of stock orders when the quantity of an asset falls below the minimum threshold or exceeds the maximum threshold1.

A daily scheduled job runs every day to check the stock levels of assets and execute the automatic restocking actions based on the stock rules1.

The plugin that must be activated in order to configure and use the scheduled job is theProcurementplugin2.

The Procurement plugin enables the procurement of assets and consumables through purchase orders, stock orders, and vendor management2.

The Procurement plugin also provides the Stock Order [Order] table, which stores the stock orders created by the automatic restocking actions2.

The plugin that helps alleviate inconsistencies in company names is the Normalization Data Services plugin, which is part of the ServiceNow IT Asset Management suite1.

The Normalization Data Services plugin provides a set of features and capabilities that enable you to standardize and normalize data across various tables and fields in ServiceNow, such as manufacturer names, model names, software names, and company names12.

The Normalization Data Services plugin uses a combination of rules, dictionaries, and algorithms to identify and correct data inconsistencies, such as spelling errors, abbreviations, synonyms, and duplicates12.

The Normalization Data Services plugin can help you improve the quality and accuracy of your data, reduce manual efforts and errors, and enhance reporting and analysis12.Reference:

1:Normalization Data Services - Product Documentation: San Diego - ServiceNow

2:Normalization Data Services - ServiceNow

According to theAudit your inventorydocument, a blind inventory audit is a type of audit that hides the expected asset list from the auditor, so that the auditor has to physically scan each asset in the location and compare it with the actual asset list1.

A blind inventory audit helps ensure data integrity and accuracy, as it prevents the auditor from ''cheating on the test'' by relying on the expected asset list1.

A blind inventory audit is typically initiated via the Now Agent Mobile app, which is a mobile application that enables users to perform various tasks related to hardware asset management, such as scanning assets, creating audits, and viewing audit results1.

The Now Agent Mobile app allows users to create an audit on the mobile device, select the location and type of audit, and scan the assets using the device camera or a Bluetooth scanner1.

Therefore, the correct answer is option C, Now Agent Mobile app, as it is the interface that is typically used to initiate a blind inventory audit.Reference:

Audit your inventory

What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management documents, the role that allows you to allocate a resource is the resource_manager role1.

The resource_manager role is a role that grants the user the ability to manage resources, such as hardware assets, consumables, and stockrooms, and to perform tasks related to resource allocation, reservation, transfer, and audit1.

The other roles that are not the correct answer are:

A)resource_user: This is a role that grants the user the ability to view and request resources, such as hardware assets and consumables, from the service catalog or the mobile app2.

B)it_project_user: This is a role that grants the user the ability to view and participate in IT projects, such as hardware asset refresh projects, and to track the progress, costs, and risks of the projects3.

C)business_stakeholder: This is a role that grants the user the ability to view and provide feedback on the business services and outcomes that are supported by the IT assets and resources4.Reference:

1: Resource Manager Role

2: Resource User Role

3: IT Project User Role

4: Business Stakeholder Role

According to the ServiceNow Hardware Asset Management documentation, advanced risk assessment is a process of identifying, analyzing, and evaluating the risks associated with hardware assets and configuration items (CIs) in the configuration management database (CMDB)1.Advanced risk assessment uses the Advanced Risk Assessment engine, which is built to address risk through an integrated risk framework2.The advanced risk assessment process consists of the following steps1:

Create a risk assessment scope: This step defines the scope and criteria of the data to be assessed, such as the asset class, category, or attribute. The risk assessment scope also specifies the frequency and duration of the assessment.

Create a risk assessment schedule: This step determines when and how often the assessment runs, based on the risk assessment scope. The risk assessment schedule also defines the assessment owner, who is responsible for overseeing the assessment process and approving the results.

Assign the assessment tasks: This step assigns the assessment tasks to the appropriate assessors, who are the users or groups who have the knowledge and authority to evaluate and update the data. The assessment tasks can be assigned manually or automatically, based on predefined rules or workflows.

Run the assessment: This step executes the assessment process, which involves sending notifications and reminders to the assessors, displaying the data to be assessed in a user-friendly interface, allowing the assessors to review and modify the data, and tracking the progress and status of the assessment tasks.

Review the assessment results: This step allows the assessment owner to verify and approve the results of the assessment, before applying the changes to the CMDB. The assessment owner can also view the risk scores, risk indicators, and risk heat maps of the assessed data.

Handle the risk response: This step involves creating and managing risk response tasks to address the identified risks. Risk response tasks are records that track the actions taken to mitigate, transfer, avoid, or accept the risks. Risk response tasks can be created manually by the assessment owner or automatically by the system based on predefined rules or workflows.

For advanced risk assessment, risk response can be handled in the following ways:

Create multiple risk response tasks: This option allows the assessment owner to create more than one risk response task for each assessed data, depending on the complexity and severity of the risk.For example, the assessment owner can create a mitigation task to reduce the impact or likelihood of the risk, and a transfer task to shift the responsibility or ownership of the risk to another party3.

Create at least one risk response task: This option requires the assessment owner to create at least one risk response task for each assessed data, regardless of the complexity and severity of the risk.This ensures that every risk is addressed and documented in the system3.

The other options are not correct because:

Skipped entirely based on attributes defined in the RAM: This option is not a valid way to handle risk response for advanced risk assessment.The RAM (Risk Assessment Matrix) is a tool that helps to calculate the risk score and risk indicator of the assessed data, based on the impact and likelihood attributes defined in the risk assessment scope1. The RAM does not determine whether to skip the risk response or not.

Must create a mitigation response task: This option is not a mandatory way to handle risk response for advanced risk assessment. A mitigation response task is one of the possible types of risk response tasks, but not the only one.Depending on the risk appetite and strategy of the organization, the assessment owner can choose other types of risk response tasks, such as transfer, avoid, or accept3.

ServiceNow Hardware Asset Management: Advanced Risk Assessment

ServiceNow Hardware Asset Management: Risk response tasks

ServiceNow Hardware Asset Management: ServiceNow Risk Management

To exclude certain types of CIs from the CI lists on the Incident, Problem, and Change forms, you can use thePrincipal CI classcheckbox, which is available on theClass Managermodule underConfiguration1.

The Principal CI class checkbox allows you to specify which CI classes are considered as principal CIs, meaning they are the most relevant and important CIs for the business services and processes1.By default, only the CI classes that have this checkbox selected are displayed on the CI lists on the Incident, Problem, and Change forms2.

To use this feature, you need to navigate to the Class Manager module, select the CI class that you want to exclude or include, and check or uncheck the Principal CI class checkbox accordingly1.You can also use theFilteroption to search for the CI classes by name or label1.

The other options are not recommended or valid ways to exclude certain types of CIs from the CI lists.Adding a Show field to the base cmdb table would require modifying the table schema and creating a reference qualifier, which could affect the performance and integrity of the CMDB3.Creating an Access control to hide the unnecessary CIs from the itil users would require defining the conditions and roles for the access rule, which could be complex and error-prone4.Making a show/hide UI action to show only the desired CIs to the itil users would require creating a custom script and UI element, which could be incompatible with the existing UI and functionality.Reference:1:Principal configuration item classes2:Configuration item lists3:CMDB table schema4:Access control rules: [UI actions]

According to the ServiceNow Product Documentation on Document Templates1, document templates are records that define the layout and content of a document that can be generated from a table record, such as an HR case1.They can include information such as fields, variables, images, and signatures1.

According to the ServiceNow Product Documentation on Generate Documents from Templates2, when a document template is created from an HR case, the name of the person who created the document is added to the name of the attachment2.For example, if John Smith created a document from the template Employee Termination Letter, the attachment name would be Employee Termination Letter - John Smith.docx2.

The reason for this naming convention is to indicate who generated the document, which can be useful for auditing and tracking purposes2.It can also help to avoid confusion or duplication if multiple documents are generated from the same template by different users2.

The other options are not the correct explanation for why the name of the person who created the document is added to the name of the attachment.It does not indicate who should sign the document, as the signature can be added as a variable in the template1.It does not indicate the Opened for user, as the document can be generated for any HR case, not necessarily the one that the user opened2.It does not indicate who the document is about, as the document can contain information about multiple parties, such as the employee, the manager, and the HR representative2.

1: ServiceNow Product Documentation: Document Templates

2: ServiceNow Product Documentation: Generate Documents from Templates

Once a catalog item has been requested, the mechanism that determines the approvals and tasks that are triggered in the application is theflow12.

A flow is a graphical representation of a business process that consists of one or more actions, such as approvals, tasks, notifications, scripts, etc., that are executed based on certain conditions and triggers12.

A flow can be associated with a catalog item to define the fulfillment process for that item, such as who needs to approve it, what tasks need to be performed, and what notifications need to be sent12.

A flow can be created and managed using the Flow Designer, a low-code development tool that allows users to design and test flows without writing any code12.

A flow can be activated or deactivated, versioned, and published to make it available for use12.

A flow can be monitored and debugged using the Flow Execution Details and the Flow Logs12.Reference:

Flow Designer

Service Catalog Request Fulfillment