CIS-DF Sample Questions & Answers

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.

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.

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.

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.

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?

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.

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.

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.

The CI Class Manager provides a specific setting called 'Principal Class' (often a checkbox or toggle in the class definition). When checked, this class is treated as a Principal Class. The CMDB Health Dashboard can then be filtered to show 'Principal Classes Only', ensuring the health score reflects only the most critical CIs.

Service Graph Connectors are designed to handle the full lifecycle of CIs. The best practice is to configure the connector's mapping logic to translate the source state (Terminated) to the appropriate ServiceNow state (Retired/Absent). This ensures that when the daily sync runs, the status is updated automatically based on the source of truth. Deletion can then be handled separately by a Data Manager policy after 6 months.

The CMDB Query Builder allows for visual construction of complex queries. You place the CI classes as nodes, define the relationship type (connection) between them, and apply property filters (like Location = New York) directly to the nodes. This query can then be saved ('Saved Query') and used as a data source for reports.