Free CIS-DF sample questions

Correct answer: The IRE updates the 'Serial Number' attribute on the existing CI because, without specific reconciliation rules, the system defaults to allowing updates from any source.

If no reconciliation rules are configured for a specific attribute or class, the default behavior of the IRE is to allow the update. Reconciliation rules are restrictive; they are used to prevent unauthorized sources from updating attributes. In the absence of rules, the 'last writer wins' logic applies essentially, allowing the payload to update the CI.

Correct answer: CI Class Manager > Health > Completeness

The CI Class Manager is the central interface for configuring CMDB health settings per class. Under the Health section for a specific class (like Linux Server), the administrator can define which fields are Required vs. Recommended and assign specific weightings to the Completeness metric. This allows granular control over how the score is calculated.

Correct answer: Integration Hub ETL using a standard Import Set

Integration Hub ETL (Extract, Transform, Load) provides a guided, low-code interface that specifically utilizes the IRE for processing data. It allows mapping source data to CMDB classes while enforcing identification and reconciliation rules. Standard Transform Maps can use IRE (via CMDBTransformUtil), but Integration Hub ETL is the modern, recommended best practice for ensuring IRE compliance and providing visibility into the transformation logic.

Correct answer: Application Service [cmdb_ci_service_auto]

In the CSDM framework, the 'Application Service' class represents the logical representation of a deployed application stack (e.g., 'CRM - Production', 'CRM - Dev'). It bridges the 'Business Application' (Design domain) with the underlying infrastructure CIs (Build/Manage domain). Application Services are operational CIs used for Incident Management and Change Management.

Correct answers: Delete Policy; Retire Policy

The 'Delete' policy is used to permanently remove CIs from the table. This handles the second requirement of deleting the record after it has remained in the 'Archived' state for the specified duration.

In ServiceNow Data Manager, the 'Retire' policy is used to update the operational status of a CI (e.g., to 'Archived' or 'Retired') based on criteria like 'Last Discovered' date. This handles the first step of moving the CI to the 'Archived' state.

Correct answer: RTE (Robust Transform Engine) Entity Lookup Operation

Integration Hub ETL utilizes the Robust Transform Engine (RTE). To convert codes to values, an RTE Entity Lookup (or sometimes a Cleanse operation with a lookup table) is used. It references a lookup table where the mapping between the integer codes (Source) and string descriptions (Target) is defined, ensuring data is normalized before it reaches the CMDB.

Correct answer: Identifier Entry 'Search on table' setting

Wait, the correct answer for case sensitivity issues is often related to the database collation or specific normalization rules, but within IRE, you typically address this by ensuring the Identifier logic is robust. However, ServiceNow IRE has a property or configuration for case sensitivity in lookups. Actually, the most direct 'feature' for this specific cleaning during identification is **Cleanup/Cleansing** logic usually handled in the RTE or Input Translation. But if looking for an IRE-specific config: The **Identifier** rule itself doesn't inherently normalize case unless scripted. *Self-Correction*: The question asks about *preventing* duplicates via IRE configuration. The best fit is ensuring the attribute used for identification is normalized *before* identification (RTE) OR using a **Canonical** value. However, assuming standard IRE features, one might use **Subscription** or **Related** items. Let's reconsider the options. A common solution is ensuring the identifier lookup is case-insensitive or using a script in the identifier. Since that's not an option, let's look at **Identifier Entry**. If we can't change source data, we need the system to treat 'SW' and 'sw' as the same. This is often a platform behavior. *Better Answer Selection*: IRE allows **Independent** identifiers. The real answer is likely related to **normalization** outside IRE or a script. Let's pivot the question to a clearer IRE feature: **Required** attributes or **Criterion Attributes**. *Revised Question Logic*: The most accurate ServiceNow feature to handle this is using **RTE (Robust Transform Engine)** operations to 'Lowercase' the input before identification. However, the question specifies 'IRE configuration'. Let's select a different scenario for Question 9 to ensure technical accuracy. **New Scenario**: Preventing duplicates when a CI moves classes (e.g., Server to Linux Server). **Question 9 (Revised)**: A Discovery process identifies a CI that currently exists in the 'Computer' class but should now be classified as a 'Linux Server' based on new operating system data. What IRE feature automatically handles this movement to the correct class without creating a duplicate record?

Correct answer: Automatic Reclassification (Upgrade)

The IRE supports automatic reclassification (often called 'Class Upgrade'). When a payload matches an existing CI in a parent class (Computer) but the payload specifies a more specific child class (Linux Server) and includes the necessary attributes, the IRE automatically 'upgrades' the CI class to Linux Server, preserving the sys_id and history, rather than creating a duplicate.

Correct answer: Create a new CMDB Health Rule for the Staleness metric specifically for the 'Critical Service' class (or filtered group) with a 30-day threshold.

CMDB Health metrics (like Staleness) are defined by Health Rules. You can define multiple rules for the same metric type targeting different classes or conditions. By creating a specific rule for Critical Service CIs with a 30-day threshold, it will override or coexist with the global 60-day rule, applying the stricter standard to the critical items.

Correct answer: Map Settings / Filter Levels

The Unified Map provides a 'Map Settings' or filter panel where users can adjust the number of levels (hops) to display and filter by specific connection types or CI classes. This allows the operator to expand the view to include lateral dependencies like backup power supplies that might be 2 or 3 hops away or connected via specific relationship types.