Troubleshooting practice questions

Run a quick discovery scan to automatically regenerate the manual application service relationships.

Why wrong: Incorrect. Discovery does not automatically repopulate manually maintained Application Services.

Convert the manual Application Service into a Business Application record.

Why wrong: Incorrect. Converting it to a Business Application removes its ability to track runtime dependencies.

Delete the Business Application and recreate it as a Technical Service.

Why wrong: Incorrect. This does not address the missing infrastructure relationships.

Data archiving automatically deletes relationship records older than 30 days.

Why wrong: Data archiving is an explicit scheduled job and does not target active CMDB relationships by default.

The CMDB Query Builder cache needs to be manually cleared.

Why wrong: Query Builder caches do not impact real-time Dependency Views rendering for individual CI records.

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

Why wrong: ServiceNow tables do not have artificial relationship row limits that cause specific links to drop silently.

Discovery Log analyzer widget

Why wrong: Discovery logs show high-level scan status, not granular pattern variable debugging.

CMDB Query Builder execution trace

Why wrong: Query Builder traces queries, not Service Mapping pattern execution steps.

Dependency Views inspector console

Why wrong: Dependency Views is a visualization tool, not a pattern debugging environment.

Modify the Transform Map coalesce script to loop through the array.

Why wrong: Legacy transform maps do not natively handle complex JSON arrays without extensive custom scripting.

Create a Business Rule to split the JSON array into individual rows on the import staging table.

Why wrong: While custom code can do this, it bypasses native IRE hierarchical payload capabilities.

Add 'network_interfaces' as a comma-separated string column in the base cmdb_ci table dictionary.

Why wrong: Storing arrays as comma-separated strings violates database normalization and breaks relationship mapping.

Client-side form layout (UI policies)

Why wrong: UI policies control form field behavior, not graph visualization topology.

The local browser cache size of the end user

Why wrong: Browser cache does not dictate logical CI relationship rendering.

Discovery schedule polling intervals

Why wrong: Polling intervals control scan timing, not map rendering logic.

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

Why wrong: IRE errors do not always log under TransformMap syslog entries, especially when using robust transformers or direct script APIs.

Review the Email Notifications table for failed ingestion alerts.

Why wrong: ServiceNow does not send email notifications by default for silent IRE rejections unless custom alerts are configured.

Inspect the Discovery Status dashboard.

Why wrong: Discovery Status dashboards only track native Discovery schedules, not custom IntegrationHub REST imports.

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

Why wrong: SLAs track task resolution times and do not affect backend data ingestion pipelines.

The UI Macro table for broken form decorators.

Why wrong: UI macros control form rendering elements and have no impact on backend RTE data processing.

Modify the transform map script to delete duplicate records after insertion.

Why wrong: Cleaning up duplicates after creation does not solve the root cause of ingestion duplication.

Write a Business Rule on cmdb_rel_ci to merge records with matching names.

Why wrong: Business rules on relationships cannot resolve CI identity conflicts handled by the IRE.

Disable the Identification and Reconciliation Engine for external feeds.

Why wrong: Disabling the IRE is a severe anti-pattern that leads to widespread CMDB data corruption.

Create a Business Rule to merge duplicate records after discovery runs.

Why wrong: Post-creation merging leads to race conditions and data integrity issues; identification should be handled upstream by the IRE.

Change the discovery schedule interval to prevent overlapping scans.

Why wrong: Scan intervals do not resolve conflicting unique key attributes within discovery payloads.

Disable the MAC address attribute from the cmdb_ci table entirely.

Why wrong: Disabling MAC address globally would break identification for the vast majority of standard network equipment.

Disabling the cmdb_rel_ci table index generation

Why wrong: Disabling table indexes degrades query performance and system stability.

Manual SQL direct database updates on the cmdb_rel_ci table

Why wrong: Direct SQL updates bypass business rules and auditing, representing a severe risk.

Data Dictionary cascade delete settings on the sys_dictionary table

Why wrong: Cascade delete on sys_dictionary would delete table structures, not individual CI relationships.

CMDB Health dashboard completeness scorecards

Why wrong: The CMDB Health dashboard is a reporting tool and does not actively modify or delete relationships during discovery runs.

Discovery Schedule exclude rules

Why wrong: Exclude rules prevent scanning entirely, they do not prune existing relationships.

Discovery Log Analyzer

Why wrong: While Discovery logs show execution steps, they do not provide an interactive payload simulation interface like the IRE test tool.

Transform Map Simulator

Why wrong: The Transform Map Simulator is for legacy import sets, not IRE-based payloads.

Service Mapping Workbench

Why wrong: Service Mapping Workbench is used specifically for building and troubleshooting service maps, not general CI payload testing.

The target table does not have any UI Policies defined on its form view.

Why wrong: UI policies govern form behavior in the browser and have no impact on backend IRE payload processing.

The import set table row count exceeds 1,000 records per batch.

Why wrong: Batch size limits do not directly trigger IRE payload errors; batching is handled natively by import streaming.

Restart all MID Servers across the enterprise network.

Why wrong: Restarting MID servers is irrelevant for RTE import payloads that are processed locally within the instance via REST or file loads.

Modify the instance web server memory allocation via system properties.

Why wrong: Instance memory properties do not resolve payload identification syntax errors.

Modify Access Control Lists to hide duplicate CIs from users.

Why wrong: Hiding records via ACLs does not solve data duplication and violates CMDB data hygiene principles.

Increase the timeout limit on all REST Message records.

Why wrong: REST timeouts affect network connection duration, not CI deduplication logic.

Delete all Discovery schedules and recreate them from scratch.

Why wrong: Deleting discovery schedules does not resolve underlying identification rule or payload matching issues.

Whether the target CI table has active client scripts blocking the relationship field.

Why wrong: Client scripts do not execute during backend API or IRE payload processing.

Whether the Discovery status schedule is set to 'Quick Discovery'.

Why wrong: Quick discovery mode simply restricts port scanning depth, not relationship ingestion logic for custom integrations.

Disable relationship validation in CMDB properties.

Why wrong: Disabling relationship validation is not supported and compromises CMDB relationship integrity.

Create a Transform Map to map relationship types.

Why wrong: Transform maps are for import staging tables, not direct IRE relationship payload validation.

Modify the cmdb_rel_ci table dictionary to allow free-text relationship types.

Why wrong: Relationship types are governed by reference records in cmdb_rel_type, not free-text dictionary fields.

The CMDB Query Builder cache expired during the scan.

Why wrong: Query Builder caches do not affect Service Mapping discovery traversal.

The cmdb_rel_ci table has exceeded maximum indexing thresholds.

Why wrong: Table indexing limits do not cause Service Mapping traversal stoppages.

The CMDB Health Correctness rule flagged the load balancer as a duplicate.

Why wrong: Duplicate flagging does not halt Service Mapping traversal mid-map.