Certified Implementation Specialist - Data Foundations (CMDB and CSDM) Free Sample Questions

In ServiceNow reconciliation rules, a lower order number indicates a higher priority. Since ServiceNow Discovery has order 100 and SolarWinds has order 200, Discovery is the authoritative source. The CMDB record (golden record) will reflect the value from the highest priority source (64GB). CMDB 360 stores the raw data from all sources, so the 32GB value from SolarWinds is retained as a 'shadowed' or 'lower priority' value visible in the CMDB 360 view.

Extending the existing 'IoT Device' table allows the new class to inherit all standard attributes (like protocol and IP address) defined in the parent class, as well as base attributes from cmdb_ci. This minimizes technical debt and table maintenance. Creating a standalone table or extending the base cmdb_ci would require duplicating the IoT-specific fields.

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.

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.

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.

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.