Text preview & study summary

ServiceNow CIS-DF Mastery Gauntlet — Full 40-Question Bank

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

Unified Map shows a clean dependency path for a service, but the operations team knows one manually maintained vendor dependency is missing. Discovery has no way to observe that dependency.

What is the correct conclusion?

Answer choices

  • A. The map is limited by the relationships present in the CMDB and needs the missing dependency modeled (Correct)

  • B. The map should be refreshed from CMDB 360 so source-level data can infer the missing vendor path

  • C. The dependency should be added to the health dashboard so the map recalculates the service view

  • D. The service should be excluded from the map until discovery can populate every dependency

Explanation

ServiceNow maps render data that physically resides inside the relationship schema tables (`cmdb_rel_ci`). If discovery cannot automatically populate an operational line, that relationship framework must be modeled manually or federated via integration to make the layout complete.

Question 2

Duplicate records for the same database keep returning after the deduplication wizard merges them. The merge result is correct each time. The duplicates appear again after the same integration runs overnight.

What should be fixed next?

Answer choices

  • A. Add the database class to the CMDB Health Dashboard and track it as a principal class

  • B. Schedule a recurring duplicate remediation review before the integration window

  • C. Create a Data Manager policy that routes duplicates to the database owner

  • D. Correct the identifying attributes or source behavior that causes new duplicate inserts (Correct)

Explanation

If an overnight integration continually reintroduces duplicates post-remediation, the upstream root cause lies in identification mismatching. The incoming payloads are failing to match existing records via the Identification and Reconciliation Engine (IRE), meaning identification rules or incoming data payloads must be realigned to update rather than insert.

Question 3

An executive dashboard shows CMDB health improving sharply this month. The data team later finds the improvement happened after several problematic classes were removed from the dashboard scope, not after remediation work.

What is the real issue?

Answer choices

  • A. The dashboard should use a higher pass threshold before reporting executive progress

  • B. The KPI changed because the measured population changed, not because quality improved (Correct)

  • C. The score should be recalculated after Data Manager reviews are closed

  • D. The dashboard should prioritize relationship health instead of completeness health

Explanation

Altering dashboard filtration parameters directly shifts the population baseline. This artificial deflation of the evaluated CI denominator creates a false positive metric trend, masking underlying quality deficiencies by removing problematic classes instead of executing root-cause configuration remediation.

Question 4

Application services already exist and are approved. Discovery finds middleware and databases correctly. Incident impact is still wrong after relationship import. Review shows the import created relationships from application services to databases using the reverse dependency direction.

What is the best correction?

Answer choices

  • A. Replace the imported relationships with discovered relationships for all database dependencies.

  • B. Correct the relationship direction and preserve the approved application service endpoints. (Correct)

  • C. Create a second relationship path from databases back to application services for reporting.

  • D. Rebuild the application services from discovery output and retire the approved records.

Explanation

Inverting dependency paths breaks downstream outage calculations. To fix this while preserving production context, you must adjust your integration mapping to write downstream relationship links in the correct direction.

Question 5

A first release has partial discovery, cloud inventory, manually maintained application lists, inconsistent ownership data, and no agreed application/service ownership model. Leadership wants a dashboard showing service health by business area.

Which actions belong in the release plan?

Answer choices

  • A. Establish ownership and target CSDM objects before sources create application and service records. (Correct)

  • B. Load all available records into broad CI classes first so leadership sees wider coverage.

  • C. Map each source to the correct CI class or CSDM object before recurring ingestion begins. (Correct)

  • D. Publish service-health dashboards from CI coverage while relationship ownership is still being finalized.

  • E. Use a custom reporting table as the temporary source of truth until discovery coverage improves.

Explanation

To avoid data corruption in early deployments, you must map your sources to targeted CSDM boundaries (C), define your cross-layer dependency guidelines (F), and clarify your ownership structures (A) prior to rolling out automated ingestion.