SNOW-CSA Database Administration and CMDB Practice Test 5 — 15 Questions

Question 1

A CMDB administrator needs to ensure that when a new Windows server CI is created by Discovery, it is automatically placed into the correct class within the CMDB class hierarchy. The administrator notices that some discovered servers are being placed in the generic 'Server' [cmdb_ci_server] class instead of the more specific 'Windows Server' [cmdb_ci_win_server] class. What is the most likely reason for this behavior?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The CI class is determined by the identification rule, which may not have a rule for Windows Server, causing it to fall back to the parent class.. The Identification and Reconciliation Engine (IRE) relies on identification rules to match and classify CIs. If a specific class like Windows Server lacks an identification rule, the IRE cannot uniquely identify it as that class and will assign it to the parent class (Server). This ensures that the CI is still created but with a less specific classification. Administrators should verify that identification rules exist for all desired CI classes to ensure accurate classification.

Answer

The CMDB class hierarchy is not properly configured; the Windows Server class does not inherit from the Server class.

Answer

The Discovery probe did not have sufficient permissions to read the Windows registry.

Answer

Discovery is configured to always create CIs in the base Server class unless a custom probe explicitly sets the class.

Question 2

A service desk manager reports that when a CI is retired in the CMDB, related open incidents still show the CI as active. The administrator needs to ensure that retiring a CI also marks it as non-operational and prevents new incidents from being linked. Which CMDB feature should be used?

Accepted Answer

CI Lifecycle and operational status fields. The CI Lifecycle and operational status fields are the correct mechanism because they define the current state of a CI record. Setting lifecycle to Retired and operational status to Non-Operational ensures the CI is treated as inactive, which prevents new incident links. Other CMDB features either manage class definitions, report on data quality, or handle record identification, none of which control CI state.

Answer

CMDB Identification and Reconciliation Engine

Answer

CMDB Health Dashboard

Answer

CMDB CI Class Manager

Question 3

A CMDB administrator is investigating why a CI record was not updated by Discovery even though the CI was discovered. The administrator suspects that the Identification and Reconciliation Engine (IRE) did not process the update. Which table stores the results of IRE processing, including any errors or skipped updates?

Accepted Answer

CMDB IRE Processing Results. The CMDB IRE Processing Results table is specifically designed to log the details of IRE operations, including any errors or reasons why a CI was not updated. By examining this table, the administrator can identify issues such as missing identification rules, duplicate CIs, or data conflicts that prevented the update. This is the correct tool for troubleshooting IRE behavior.

Answer

CMDB CI Change History

Answer

Discovery Logs

Answer

CMDB Health Dashboard

Question 4

A service desk analyst reports that they cannot see the 'Serial Number' field on the CI form for a printer. The field is present on other CI classes. What is the most likely reason?

Accepted Answer

The printer CI class has a UI policy that hides the 'Serial Number' field. A UI policy can conditionally hide fields on a form. If a UI policy on the printer CI class or a related condition is set to hide the 'Serial Number' field, the analyst would not see it. This is the most likely reason because the field is visible on other classes, ruling out ACLs and base class inheritance issues.

Answer

The 'Serial Number' field is not included in the form layout for the printer class

Answer

The user does not have read access to the 'Serial Number' field due to ACL restrictions

Answer

The 'Serial Number' field is not part of the base CI class and must be added to the printer class

Question 5

A CMDB administrator must ensure that when a new Windows server CI is created by Discovery, it is automatically placed in the correct business service and assigned to the correct support group based on its IP subnet. Which configuration should be implemented?

Accepted Answer

A CMDB data lookup rule that maps IP subnet to business service and support group. A CMDB data lookup rule is the correct solution because it can automatically populate CI fields based on a lookup table. By matching the IP subnet to predefined mappings, the rule assigns the correct business service and support group without custom scripting. Other options either categorize CIs, create relationships, or require ad hoc scripts, none of which provide a maintainable, data-driven assignment.

Answer

A CMDB CI class rule that sets the business service and support group

Answer

A Discovery schedule with a post-processing script that updates the CI

Answer

A CI relationship rule that links the CI to a business service

Question 6

A CMDB administrator needs to create a custom CI class that inherits from the 'Server' class but adds a new field 'Backup Schedule'. The administrator also wants to ensure that this new class can be discovered by ServiceNow Discovery. What is the minimum required step?

Accepted Answer

Create the new class, extend 'Server', and create a new Discovery pattern for the class. To make a custom CI class discoverable, you must create a Discovery pattern that targets the new class. The pattern defines the probes, sensors, and mapping to populate the CI attributes, including the new 'Backup Schedule' field. Extending the 'Server' class is necessary for inheritance, but without a pattern, Discovery will not populate the class.

Answer

Create the new class and extend the 'Server' class; no additional configuration is needed for Discovery

Answer

Create the new class, extend 'Server', and add a new CI type to the Discovery schedule

Answer

Create the new class, extend 'Server', and create a new identification rule for the class

Question 7

A CMDB administrator is investigating why a newly discovered Linux server was not created in the CMDB. The Discovery log shows that the server was successfully classified and identified, but the CI record is missing. The administrator checks the Identification and Reconciliation Engine (IRE) logs and finds that the CI was matched to an existing record but was not updated. Which of the following is the most likely cause?

Accepted Answer

The IRE identification rule matched the server to an existing CI, but the reconciliation rule prevented any updates, so no new CI was created.. The IRE attempts to match incoming data to existing CIs using identification rules. If a match is found, no new CI is created; instead, reconciliation rules determine which attributes to update. If reconciliation rules prevent updates (e.g., the data source is not authoritative or is set to ignore), the existing CI remains unchanged, and the new server data is effectively discarded. This explains why the CI appears missing despite successful discovery.

Answer

The Discovery schedule did not include the Linux server's IP range, so the server was never discovered.

Answer

The reconciliation rule for the Linux Server class is set to 'Ignore' for the data source, preventing updates.

Answer

The CMDB class for Linux Server does not have an identification rule, so the IRE could not create the CI.

Question 8

A consultant is designing the CMDB for a large enterprise. The company wants to track relationships between business services, applications, and infrastructure components. Which relationship model should be used to represent that a business service depends on an application, which in turn depends on a server?

Accepted Answer

Dependency relationship (structural). A dependency relationship (structural) is the correct model because it explicitly captures the directional 'depends on' nature of the chain: a business service relies on an application, which in turn relies on a server. In ServiceNow CMDB, structural dependency relationships (e.g., 'Depends on' or 'Used by') are designed to represent these hierarchical, transitive dependencies between CIs, enabling impact analysis and root cause mapping.

Answer

Membership relationship

Answer

Ownership relationship

Answer

Connectivity relationship

Question 9

During a CMDB health review, an administrator finds that many CI records have the same serial number but different names and IP addresses. What is the most likely root cause?

Accepted Answer

The identification rule for the CI class does not include the serial number.. The identification rule determines which fields are used to uniquely identify a CI. If the serial number is not included in the identification rule, the CMDB cannot detect duplicates based on serial number, allowing multiple CIs with the same serial number but different names and IP addresses to be created. This is a common misconfiguration that leads to CI proliferation and data inconsistency.

Answer

The CMDB has a scheduled job that deletes old CIs.

Answer

The CI class has a unique constraint on the name field.

Answer

The reconciliation rule is set to 'Create' instead of 'Update'.

Question 10

An administrator inspects the IRE log and sees the exhibit. The IRE created a new CI despite finding a match on serial_number. What is the most likely reason?

Accepted Answer

The identification rule for cmdb_ci_server does NOT include serial_number.. The IRE uses identification rules to determine which attributes are used for matching CIs. If the identification rule for cmdb_ci_server does NOT include serial_number, then even though a match on serial_number exists, the IRE will not consider it a match and will create a new CI. The IRE only reconciles based on the attributes defined in the identification rule.

Answer

The identification rule for cmdb_ci_server includes serial_number.

Answer

The IRE is configured to always create new records regardless of matches.

Answer

The existing CI has a different name, so IRE considers it a different CI.

Question 11

A company is using multiple data sources (Discovery, SCCM, and manual imports) to populate the CMDB. They notice that some CI attributes are being overwritten incorrectly. Which feature should be used to define which data source is authoritative for specific attributes?

Accepted Answer

Identification and Reconciliation Engine (IRE) with reconciliation rules. The Identification and Reconciliation Engine (IRE) with reconciliation rules is the correct feature because it allows administrators to define which data source is authoritative for specific CI attributes. When multiple sources populate the CMDB, reconciliation rules determine the priority of data sources, ensuring that attributes from a higher-priority source overwrite those from lower-priority sources, preventing incorrect overwrites.

Answer

CMDB Data Source rules

Answer

Import set transform maps

Answer

Business rules with condition on source field

Question 12

An administrator discovers that a scheduled discovery job is creating duplicate CI records for the same physical server. The server has two IP addresses (one for management, one for production). What is the most likely cause?

Accepted Answer

The identification rule for the CI class does not include a unique hardware identifier like serial number.. ServiceNow's CMDB uses identification rules to determine whether a discovered CI is new or matches an existing record. For a physical server with multiple IP addresses, the identification rule must include a unique hardware identifier such as a serial number (e.g., from SMBIOS) to prevent duplicate CIs. Without that, the system may treat each IP address as a separate CI, even though they belong to the same server.

Answer

The discovery schedule is set to run too frequently.

Answer

The discovery job is configured to scan only the management IP.

Answer

The server has too many IP addresses for discovery to handle.

Question 13

What is the purpose of the CMDB Health Dashboard?

Accepted Answer

To monitor the completeness and compliance of CI data in the CMDB. The CMDB Health Dashboard is designed to monitor the completeness and compliance of Configuration Item (CI) data within the CMDB. It provides metrics and visualizations that help administrators identify data quality issues, such as missing mandatory fields, stale CIs, or violations of CMDB rules, ensuring the CMDB remains a reliable source of truth for IT operations.

Answer

To manage user roles and permissions for CMDB

Answer

To visualize relationships between CIs

Answer

To configure discovery schedules and probes

Question 14

A large financial institution uses ServiceNow CMDB to manage their IT infrastructure. They have a complex environment with multiple data sources: Discovery, SCCM, and a custom integration from their cloud provider. The CMDB contains over 100,000 CIs. Recently, the CMDB team noticed that for a specific set of Windows servers, the 'os_version' attribute is being updated to an incorrect value every night. The value comes from the SCCM integration, which is supposed to be the authoritative source for software-related attributes. However, the 'os_version' attribute should be authoritative from Discovery. The IRE is configured with reconciliation rules, but the issue persists. The team also finds that the Discovery job for these servers runs at 2:00 AM, and the SCCM integration runs at 3:00 AM. The incorrect value appears after the SCCM run. The reconciliation rules are set so that Discovery is authoritative for 'os_version', but the SCCM integration still overwrites it. What is the most likely cause and recommended action?

Accepted Answer

Review and correct the reconciliation rule to ensure Discovery is the authoritative source for 'os_version' and that the rule is active.. The reconciliation rule is the mechanism that dictates which data source is authoritative for a specific attribute. If the rule is misconfigured, inactive, or not properly scoped, the IRE will allow the SCCM integration to overwrite the 'os_version' attribute even though Discovery is intended to be authoritative. Reviewing and correcting the rule ensures that the IRE enforces the correct source priority for that attribute.

Answer

Enable the IRE 'Strict' mode to prevent any updates from non-authoritative sources.

Answer

Disable the SCCM integration for these servers and rely solely on Discovery.

Answer

Change the order of the integrations so that SCCM runs before Discovery.

Question 15

A CMDB administrator notices that duplicate CIs are being created for the same server from different discovery sources. What is the most likely cause?

Accepted Answer

The identification rules for the CI class are not correctly defined.. Duplicate CIs occur when multiple discovery sources (e.g., Service Mapping, Discovery, or cloud APIs) identify the same server but the identification rules fail to reconcile them into a single CI. Identification rules define which attributes (such as serial number, MAC address, or FQDN) uniquely identify a CI class. If these rules are missing, incomplete, or incorrectly prioritized, the system treats each discovery event as a new CI, leading to duplicates.

Answer

The 'Prevent duplicates' flag is not enabled.

Answer

The reconciliation rules are misconfigured.

Answer

The CMDB is set to read-only mode.