Hard Difficulty Questions

Separate REST API calls for each CI followed by a manual relationship creation call.

Why wrong: While possible, this is inefficient and fails to leverage single-transaction IRE batch processing.

A CSV file attached to a Data Source record processed exclusively by a Transform Map.

Why wrong: Transform maps bypass IRE by default unless explicitly configured to use Robust Transform Engine (RTE) with IRE integration.

A flat array of CI records with parent and child reference ID fields embedded directly in each CI record.

Why wrong: Embedding parent/child IDs directly inside CI records does not conform to IRE payload standards.

CI Class Manager relationship rule definitions

Why wrong: Relationship rules manage parent-child connectivity, not aging thresholds.

Discovery Schedule properties

Why wrong: Discovery schedules govern scan frequency, not CMDB health aging rules.

Data Archiving rule definitions

Why wrong: Data archiving moves old records to archive tables, which is distinct from CMDB Health correctness metrics.

The CI is automatically retired from the database immediately

Why wrong: Certification tasks gather verification; they do not automatically retire CIs unless specified by custom workflow actions.

A high-priority incident is automatically created for the IT service desk

Why wrong: Certification tasks do not generate IT service desk incidents by default.

Assignment group field on all incoming Incident records automatically.

Why wrong: Incorrect. Incidents rely on assignment rules or service mappings, not as a substitute for CMDB configuration.

Managed by group field on the underlying Linux server CIs.

Why wrong: Incorrect. Infrastructure support groups do not override application-level support mapping.

Assigned group field on the parent Business Application record.

Why wrong: Incorrect. Business Application support groups are architectural, whereas operational support lives on the Application Service.

RTE automatically translates foreign languages in source data payloads.

Why wrong: RTE does not perform language translation.

RTE eliminates the need for staging tables during data imports.

Why wrong: RTE still utilizes staging data sources during import operations.

RTE bypasses all access control lists to accelerate import times.

Why wrong: RTE respects security configurations and access controls.

Static Business Application Service

Why wrong: Incorrect. This is not a standard CSDM Application Service type.

Manual Application Service

Why wrong: Incorrect. Manual services require manual CI additions.

Portfolio-linked Application Service

Why wrong: Incorrect. Portfolio links do not automate CI membership.

Standard Legacy Transform Maps without RTE

Why wrong: Standard legacy transform maps bypass IRE and are not recommended for reconciled CMDB updates.

Dependency View graphical layout settings

Why wrong: Dependency views are for visualization, not IRE processing logic.

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.

It is a critical CSDM violation; a database CI can never be associated with more than one Application Service.

Why wrong: Incorrect. Shared databases frequently support multiple application environments or services.

It means the database must be converted into a Service Offering immediately.

Why wrong: Incorrect. Databases are infrastructure CIs, not service offerings.

It indicates that Discovery has duplicated the database CI into the Business Application table.

Why wrong: Incorrect. Discovery populates infrastructure tables, not Business Application tables.

CMDB Data Governance > Audit Trail

Why wrong: There is no specific module named 'CMDB Data Governance > Audit Trail'.

Data Certification Results

Why wrong: Data Certification Results show responses to certification questions, not automated attribute modification audit trails.

System Logs > Audit (sys_audit)

Why wrong: While sys_audit tracks table changes, CMDB-specific queries and reporting are streamlined using CI Class History or specific CMDB audit features, though sys_audit is platform-level. However, CI History specifically formats CI attribute timelines.

All attributes are stored in a single flat cmdb_ci table with discriminator columns.

Why wrong: ServiceNow uses separate physical database tables for extended classes rather than a single flat table.

The platform throws an error because more than two levels of extension are prohibited in the CMDB.

Why wrong: ServiceNow supports multiple levels of table extension within the CMDB hierarchy.

Records are stored exclusively in the cmdb_ci table, and child tables only store metadata.

Why wrong: Child tables store the actual record data specific to their attributes and inherited fields.

Inside Data Certification definition forms

Why wrong: Data Certification handles manual attestation tasks, not automated CMDB Health anomaly remediation rule processing.

Through Data Policies on the cmdb_ci table

Why wrong: Data Policies enforce mandatory fields and read-only states on database transactions, not automated health score remediation.

In the CI Class Manager under the Remediation tab

Why wrong: CI Class Manager handles class definitions, identifier rules, and reconciliation, not health remediation workflows.

Automatic MID Server selection rule

Why wrong: MID servers are used for Discovery, not Data Certification campaigns.

Duplicate CIs

Why wrong: Duplicate CIs measures overlapping records representing the same physical or logical entity.

Unassigned CIs

Why wrong: Unassigned is a completeness metric, not an orphan correctness metric.

Stale CIs

Why wrong: Stale CIs measures records that have not been updated within a specified timeframe.

The IRE maps discovery sources based on IP address ranges rather than the discovery source string.

Why wrong: Discovery source matching relies on the designated 'discovery_source' field value passed in the payload.

The IRE automatically normalizes all discovery source strings to lowercase and strips special characters.

Why wrong: The IRE does not automatically alter or normalize discovery source strings; exact matching is required.

Discovery source names only affect reporting and have no impact on IRE reconciliation behavior.

Why wrong: Discovery source names are fundamental to tracking which source owns which attribute value under Data Source Precedence.

CMDB Health > Dashboard Settings

Why wrong: CMDB Health Dashboard settings control score calculations and metric thresholds, not governance policy remediation tasks.

Data Certification > Definitions

Why wrong: Data Certification definitions are used for audit campaigns, not real-time CMDB Data Governance remediation policies.

System Policy > Rules > Data Policy

Why wrong: Standard data policies enforce mandatory fields at the platform level, not CMDB health remediation tasks.

Data pipelines must be modeled as Business Capabilities in the Foundation domain.

Why wrong: Incorrect. Data pipelines are not foundation capabilities.

Business Applications must be deleted and replaced entirely by Incident records.

Why wrong: Incorrect. Incidents are operational tasks and cannot replace portfolio applications.

Application Services cannot participate in data integration mapping.

Why wrong: Application Services can and do participate in integration mapping.

Provide a screenshot of the Discovery Schedule configuration

Why wrong: Discovery schedules prove that scanning occurs, not that governance data policies are enforced.

Export the entire sys_audit table to CSV

Why wrong: Exporting raw sys_audit is inefficient and does not specifically demonstrate governance policy enforcement results.

Display the baseline CI Class Manager JSON payload definition

Why wrong: Class payloads define attribute structures, not policy enforcement compliance history.

Discovery Schedules > CMDB Health

Why wrong: Discovery schedules control network scans, not health calculation batch jobs.

CMDB Health Dashboard > Schedule Settings

Why wrong: Execution schedules for background calculation jobs are managed in Scheduled Jobs, not directly inside dashboard UI settings.

Data Governance > Job Execution

Why wrong: There is no 'Data Governance > Job Execution' module.

Data Policy Enforcement Engine

Why wrong: Data policies enforce mandatory fields and read-only states, not deduplication based on complex payload matching rules.

CMDB Health Duplicate Engine

Why wrong: CMDB Health detects duplicates after insertion; the IRE prevents them during ingestion.

Transform Map Unique Key matching

Why wrong: Transform maps can have coalesce flags, but the enterprise standard for CMDB deduplication is the IRE.