CIS-DF Practice Test 15 — 15 Questions

Question 1

Which tab or related list on a Configuration Item form allows a user to manually add a new relationship to another CI without using Discovery?

Accepted Answer

Relationships related list. The Relationships related list on a CI form allows users to manually add, view, and manage relationships between CIs. This is the standard way to create relationships without relying on Discovery or other automated processes. It provides a direct interface to define parent-child, depends-on, or other relationship types.

Answer

Discovery Schedules related list

Answer

CMDB Health related list

Answer

CSDM Alignment related list

Question 2

A company implements a policy where department heads must review their server assets every six months. Which module supports scheduling this periodic verification campaign?

Accepted Answer

Data Certification > Certification Schedules. Data Certification > Certification Schedules is the ServiceNow module that lets administrators define recurring certification campaigns, including the frequency (e.g., every six months), the CI scope, and the reviewers (department heads). When the schedule fires, certification tasks are generated and assigned to the designated reviewers for attestation.

Answer

Service Portfolio > Reviews

Answer

Governance, Risk, and Compliance > Periodic Audits

Answer

CMDB Health > Review Schedules

Question 3

An enterprise uses Service Graph connectors to automatically populate infrastructure CIs. They want to ensure that these dynamically discovered CIs are automatically associated with the correct Application Service without manual mapping for every server addition. Which Application Service type should be deployed?

Accepted Answer

Dynamic CI Group Application Service. A Dynamic CI Group Application Service automatically includes CIs based on a saved query or filter, so newly discovered servers matching the criteria are associated without manual mapping. This is exactly the requirement for dynamically discovered CIs from Service Graph connectors. Static and Manual Application Services require explicit CI membership, which would not scale.

Answer

Static Business Application Service

Answer

Manual Application Service

Answer

Portfolio-linked Application Service

Question 4

During a Dependency Views troubleshooting session, an engineer notices that a specific application server is missing its connected database nodes. What is the most likely cause when relationships are missing despite successful Discovery runs?

Accepted Answer

The relationship type filter in the Dependency Views UI is hiding specific relationship types.. Dependency Views applies relationship-type filters in the UI, and by default some relationship types may be excluded from the rendered map. If Discovery successfully created the application server-to-database relationships in cmdb_rel_ci but the filter hides those relationship types, the database nodes will not appear. Adjusting the filter to include the relevant relationship types restores the missing nodes.

Answer

Data archiving automatically deletes relationship records older than 30 days.

Answer

The CMDB Query Builder cache needs to be manually cleared.

Answer

The cmdb_ci table has reached its maximum row count limit for relationships.

Question 5

Your organization wants to understand the impact of a failing database server on dependent business applications. Which component of the CMDB architecture must be configured to establish this dependency link?

Accepted Answer

Configuration Item Relationship (cmdb_rel_ci). Relationships between configuration items are stored in the Configuration Item Relationship table (cmdb_rel_ci), defining how CIs depend on or connect to one another.

Answer

CI Class Manager

Answer

Identification and Reconciliation Engine (IRE)

Answer

Discovery Schedule

Question 6

A company notices that hundreds of stale server records are polluting the CMDB, negatively affecting health scores. Rather than deleting them manually, what is the best practice governance workflow to handle stale CIs?

Accepted Answer

Initiate a review campaign or automated retirement workflow via CMDB health remediation. The best-practice governance workflow for stale CIs is to initiate a review campaign or automated retirement workflow through CMDB Health remediation, which routes stale CIs to data owners for validation before retirement. This preserves auditability, respects data ownership, and prevents accidental deletion of CIs that may still be relevant. It also feeds back into the health score legitimately rather than masking the problem.

Answer

Delete all records where sys_updated_on is older than 90 days using a background script

Answer

Run Discovery against the entire IP range daily to force updates

Answer

Turn off the Stale CI metric so the score improves without action

Question 7

An administrator is troubleshooting a Scheduled Data Import that uses an IntegrationHub REST step to pull server data. The import completes, but no CIs are created or updated in the CMDB, and the import set rows show a status of 'Processed'. Where should the administrator check to see if the IRE rejected the payload?

Accepted Answer

Check the CMDB Integration Results (cmdb_integration_log) or IRE processing logs for detailed payload error messages.. The Identification and Reconciliation Engine (IRE) processes import set rows after they are marked 'Processed' by the transform. When IRE rejects a payload—due to missing required attributes, duplicate detection conflicts, or failed reconciliation rules—it does not create or update CIs, but the import set row status remains 'Processed' because the transform itself succeeded. Detailed rejection reasons, including the specific payload and rule that failed, are written to the CMDB Integration Results table (cmdb_integration_log) and IRE processing logs, not to the standard transform warnings. Therefore, option B is the correct place to investigate IRE rejections.

Answer

Check the System Log (syslog) for standard warning messages tagged with 'TransformMap'.

Answer

Review the Email Notifications table for failed ingestion alerts.

Answer

Inspect the Discovery Status dashboard.

Question 8

When customizing Dependency Views icons and indicators, an administrator wants to display a visual alert symbol directly on a CI node when its associated hardware warranty is expiring within 30 days. How is this achieved within the platform?

Accepted Answer

Configuring CI status indicators or map decorators mapped to a custom script or condition. To display a visual alert symbol on a CI node in Dependency Views, you configure CI status indicators or map decorators. These can be mapped to a custom script or condition that evaluates the warranty expiration and displays the alert.

Answer

Enabling Performance Analytics indicator widgets inside the form view

Answer

Creating a business rule on the cmdb_ci table that injects HTML into the map canvas

Answer

Modifying the CMDB Class Manager icon library directly in the sys_ui_icon table

Question 9

Which THREE of the following are common pitfalls or anti-patterns when implementing CSDM?

Accepted Answer

Attempting to implement advanced financial Run-phase metrics before completing Crawl foundational data.. Option A is correct because CSDM maturity follows a Crawl–Walk–Run progression, and trying to implement advanced financial Run-phase metrics before the foundational Crawl data (base CMDB, Business Applications, Application Services, and their relationships) is complete is a classic anti-pattern that produces unreliable reporting. Option B is correct because operational incidents should be logged against Application Services (the running instances that actually experience outages), not directly against Business Applications, which are logical containers; logging against Business Applications breaks the intended CSDM layering and skews availability/incident metrics. Option C is correct because Business Applications and Application Services are distinct CSDM domains with different purposes — Business Applications represent the logical business capability, while Application Services represent the technical service instances — and treating them as interchangeable causes duplicate records and broken relationships. Option D is not a pitfall but the correct CSDM practice: Application Services are linked to infrastructure CIs via 'Depends on / Used by' relationships, so it is not an anti-pattern. Option E is also not a pitfall: using ServiceNow Discovery to automatically populate infrastructure CIs is a recommended, supported practice that reduces manual data entry and improves CMDB accuracy.

Answer

Linking Application Services to underlying server CIs using 'Depends on / Used by'.

Answer

Using ServiceNow Discovery to automatically populate infrastructure CIs.

Question 10

An administrator is reviewing class hierarchy design principles in the CMDB. Which TWO statements describe the purpose of extending existing CI classes rather than creating independent base tables? (Choose two.)

Accepted Answer

Inherited classes ensure proper compatibility with CMDB Health, IRE, and Dependency Views.. Option A is correct because extending an existing CI class keeps the new class within the CMDB class hierarchy, so platform features such as CMDB Health, Identification and Reconciliation Engine (IRE), and Dependency Views continue to recognize and process the CIs correctly. Option B is correct because child classes inherit the parent class's attributes, fields, and behaviors, so administrators only add the extra attributes specific to the new CI type instead of redefining everything. Option C is incorrect because independent base tables are not automatically integrated with out-of-the-box Service Graph Connectors; those connectors target the standard CMDB class hierarchy. Option D is incorrect because extending a base table does not bypass ACLs; access control is still enforced on the class and its records. Option E is incorrect because independent tables still require identification rules (or equivalent logic) to uniquely identify and reconcile CIs.

Answer

Independent base tables provide better integration with out-of-the-box Service Graph Connectors automatically.

Answer

Extending base tables allows CIs to bypass mandatory access control lists (ACLs).

Answer

Creating independent tables eliminates the need for any identification rules.

Question 11

An administrator is planning a custom CMDB extension project. Which THREE factors should be evaluated when deciding whether to create a new CI class or add attributes to an existing class? (Choose three.)

Accepted Answer

Whether specialized relationships or lifecycle workflows apply specifically to these items. Option A is correct because a new CI class is justified when the items need their own specialized relationship types or lifecycle workflows that do not apply to the existing parent class, since class-specific relationships and workflows cannot be cleanly modeled as attributes. Option B is correct because if the items require unique attributes that do not apply to the parent class, adding them to the parent would pollute the parent schema and force irrelevant fields onto other CIs, so a subclass is the proper design. Option E is correct because distinct identification rules (for example, different reconciliation keys or discovery source identifiers) must be defined at the class level, and items needing their own identification logic warrant a separate CI class rather than attributes on an existing one. Option C is incorrect because ITIL user license counts are a commercial/administrative concern and have no bearing on CMDB class modeling decisions. Option D is incorrect because table form background color is a cosmetic UI preference and is irrelevant to the data model design choice between a new class and added attributes.

Answer

The number of ITIL user licenses assigned to the platform

Answer

The preferred background color of the table form layout

Question 12

When configuring CMDB Data Governance policies, which THREE rule criteria types can be evaluated against CI records? (Choose three.)

Accepted Answer

Attribute value validation (checking pattern or lookup criteria). Option A is correct because CMDB data governance rules can evaluate CI attribute values against validation criteria such as regex patterns, allowed lookup values, or reference tables to flag non-conforming records. Option B is correct because governance policies can include relationship checks that verify required parent/child or dependency connections exist for a CI class, ensuring the CMDB graph is structurally valid. Option E is correct because completeness checks are a core governance criterion, verifying that mandatory attributes for a given CI class are populated and not null or empty. Option C is not correct because network latency ping response is an operational monitoring/availability metric, not a CMDB data governance rule criterion evaluated against CI records. Option D is not correct because synchronizing hardware warranty expiration dates with vendor APIs is an external data integration/enrichment activity, not a governance rule criteria type evaluated against CI records.

Answer

Network latency ping response check

Answer

Hardware warranty expiration date synchronization with vendor APIs

Question 13

Which THREE factors should an administrator consider when configuring CMDB Health Inclusion Rules? (Choose three.)

Accepted Answer

Operational State (e.g., excluding retired or non-operational CIs). Option A is correct because CMDB Health Inclusion Rules commonly filter CIs by Operational State, allowing administrators to exclude retired, non-operational, or otherwise inactive CIs so they are not counted in health metrics. Option C is correct because Environment is a standard inclusion criterion, letting administrators scope health calculations to production assets and exclude test or lab CIs that would otherwise skew compliance and completeness scores. Option E is correct because CI Class is a fundamental inclusion factor, enabling rules to target specific tables such as servers or databases so health metrics apply only to the relevant CI types. Option B is not correct because MID Server cluster membership relates to discovery and data collection infrastructure, not to which CIs are included in CMDB Health calculations. Option D is not correct because email notification retry intervals are an alerting or notification setting and have no bearing on CMDB Health Inclusion Rules.

Answer

MID Server cluster membership

Answer

Email notification retry intervals

Question 14

An administrator is troubleshooting an integration that uses Robust Transform Engine (RTE) to ingest software licenses. During testing, records are inserted into staging tables, but the RTE fails to push them into the CMDB via the IRE. Which THREE areas should the administrator inspect to diagnose the failure? (Choose three.)

Accepted Answer

CMDB Integration Results / IRE Execution Logs to identify specific payload rejection reasons.. Option C is correct because the CMDB Integration Results and IRE Execution Logs record the exact outcome of each IRE payload, including rejection reasons such as missing required attributes, duplicate detection, or identification failures, which is the fastest way to see why records are not being inserted into the CMDB. Option D is correct because the IRE requires valid identification rules for the target CI class; if the software license class lacks an active identification rule (or the rule is not published), the IRE cannot uniquely identify or create the CI and will reject the payload. Option E is correct because RTE relies on field mappings and data stream definitions to transform source staging fields into the IRE payload attributes; if a mandatory target attribute is unmapped or mapped incorrectly, the IRE payload will be incomplete and the insert will fail. Option A is not relevant because SLA definitions govern task/response time tracking, not IRE payload processing or CMDB insertion. Option B is not relevant because UI Macros control form rendering and decorators, which have no bearing on RTE-to-IRE data flow or CMDB record creation.

Answer

The Service Level Agreement (SLA) definition table for expired response times.

Answer

The UI Macro table for broken form decorators.

Question 15

Which TWO practices represent effective CMDB governance strategies for maintaining data quality? (Choose two.)

Accepted Answer

Assigning clear data ownership (Managed by / Support Group) for every CI class. Option D is correct because assigning clear data ownership through fields such as Managed by and Support Group for every CI class establishes accountability, ensuring that each configuration item has a responsible party who validates and maintains its accuracy, which is a foundational CMDB governance control. Option E is correct because implementing automated remediation tasks for CMDB health and data governance violations enforces data quality continuously, detecting and correcting issues like orphan CIs, stale records, or missing attributes without relying solely on manual effort. Options A, B, and C do not belong: unrestricted modification by any authenticated user destroys change control and data integrity, relying entirely on end-users to manually update server attributes produces inconsistent and unverified data, and disabling audit logging removes the traceability needed to detect and investigate unauthorized or erroneous CI changes while offering negligible performance benefit.

Answer

Allowing any authenticated user to modify production CI configurations without restriction

Answer

Relying entirely on end-users to manually update all server attributes via service portal requests

Answer

Disabling all audit logging to improve table insert performance