ServiceNow CIS-DF Practice Test 22 - Prepaway
Practice Exams:

Pass ServiceNow CIS-DF Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

CIS-DF Premium ETE File


  • Premium File 283 Questions & Answers. Last Update: Nov 12, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

ServiceNow CIS-DF Practice Test 22

Question 210

An imported cloud asset payload uses vendor field names that do not map to CMDB class attributes, leaving key fields empty. Select TWO shortcuts that would undermine the intended data integrity or governance.

  1. Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response.
  2. Validate in a controlled test that a test record populates stable CI attributes and preserves the intended source identifier after transform.
  3. Write source properties directly into arbitrary dictionary fields that happen to share similar names.
  4. Set every unmapped field to a placeholder string and ignore source semantics.
  5. Map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output.

Explanation

Correct Answer

C:

This violates the scenario constraints for integrationhub etl transform mapping. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. Instead the safe implementation is: Map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output.

D:

“Set every unmapped field to a placeholder string and ignore source semantics” would violate the requirement. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

Incorrect Answers

A:

“Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

B:

“Validate in a controlled test that a test record populates stable CI attributes and preserves the intended source identifier after transform” adds a relevant safeguard or verification step rather than weakening the solution. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

E:

“Map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output” is the controlled implementation, not an unsafe workaround. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

Question 211

A legacy spreadsheet import inserts server records directly into cmdb_ci and creates duplicates on every monthly load. What is the most appropriate configuration or governance action?

  1. Use a random generated hostname each month so rows appear unique.
  2. Enrich the CI through an approved authoritative contract or stewardship feed without overriding discovered technical fields.
  3. Keep the direct insert transform and delete duplicates manually after every run.
  4. Route supported transformed imports through IRE with appropriate identification and reconciliation controls.

Explanation

Correct Answer

D:

The requested CMDB/CSDM implementation concerns import set transform and ire integration, not just a different useful platform feature. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Validate the effect with: Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

Incorrect Answers

A:

“Use a random generated hostname each month so rows appear unique” does not implement the control that the facts call for. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Instead, route supported transformed imports through IRE with appropriate identification and reconciliation controls.

B:

This addresses non-discoverable attribute enrichment, an important but separate issue. It does not resolve the described import set transform and ire integration failure. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. The targeted action is: Route supported transformed imports through IRE with appropriate identification and reconciliation controls.

C:

“Keep the direct insert transform and delete duplicates manually after every run” does not implement the control that the facts call for. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Instead, route supported transformed imports through IRE with appropriate identification and reconciliation controls.

Question 212

A legacy spreadsheet import inserts server records directly into cmdb_ci and creates duplicates on every monthly load. Which diagnostic evidence best isolates the actual cause?

  1. Inspect source endpoint IDs, IRE mapping, relationship type and duplicate edge count.
  2. Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries.
  3. Inspect raw units, transform scripts, target dictionary type, and sample converted attributes.
  4. Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response.

Explanation

Correct Answer

B:

Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

Incorrect Answers

A:

That inspection relates primarily to relationship duplication from integrations rather than the failing import set transform and ire integration process. The immediate evidence needed for this case is: Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries.

C:

“Inspect raw units, transform scripts, target dictionary type, and sample converted attributes” would not be the most direct first check for this failure. Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.

D:

That inspection relates primarily to integrationhub etl transform mapping rather than the failing import set transform and ire integration process. The immediate evidence needed for this case is: Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries.

Question 213

A legacy spreadsheet import inserts server records directly into cmdb_ci and creates duplicates on every monthly load. Which result demonstrates that the requirement is now satisfied?

  1. Service maps and queries show the database dependency under the intended relationship category.
  2. Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.
  3. A mixed test batch imports valid CIs and lists invalid rows with actionable source identifiers and errors.
  4. Test devices with 8 GiB and 8192 MiB normalize to the intended comparable numeric value.

Explanation

Correct Answer

B:

This tests the actual result for import set transform and ire integration instead of merely checking whether a configuration screen can be opened. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. The test must be performed on the described CI and service scope.

Incorrect Answers

A:

“Service maps and queries show the database dependency under the intended relationship category” pertains to relationship type selection for dependency, not the deciding condition here. Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.

C:

This might validate import rejection quarantine process, but does not establish the acceptance requirement for import set transform and ire integration. Instead verify: Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

D:

This might validate integration data transform type safety, but does not establish the acceptance requirement for import set transform and ire integration. Instead verify: Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

Question 214

A legacy spreadsheet import inserts server records directly into cmdb_ci and creates duplicates on every monthly load. What underlying CMDB or CSDM behavior justifies the correct decision?

  1. Canonical manufacturer and model references allow consistent asset and configuration reporting across multiple providers.
  2. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.
  3. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.
  4. Type and unit mismatches in ingestion can produce false configuration and compliance conclusions.

Explanation

Correct Answer

C:

Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Route supported transformed imports through IRE with appropriate identification and reconciliation controls. The decisive evidence is that two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

Incorrect Answers

A:

Although relevant to asset model normalization before cmdb ingest, this does not explain the remedy for import set transform and ire integration. The causally relevant rule is: Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.

B:

Although relevant to import data source timestamp normalization, this does not explain the remedy for import set transform and ire integration. The causally relevant rule is: Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.

D:

Although relevant to integration data transform type safety, this does not explain the remedy for import set transform and ire integration. The causally relevant rule is: Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.

Question 215

A legacy spreadsheet import inserts server records directly into cmdb_ci and creates duplicates on every monthly load. Which TWO actions would be unsuitable or unsafe?

  1. Use a random generated hostname each month so rows appear unique.
  2. Validate in a controlled test that two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.
  3. Route supported transformed imports through IRE with appropriate identification and reconciliation controls.
  4. Keep the direct insert transform and delete duplicates manually after every run.
  5. Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries.

Explanation

Correct Answer

A:

“Use a random generated hostname each month so rows appear unique” would violate the requirement. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior.

D:

This violates the scenario constraints for import set transform and ire integration. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Instead the safe implementation is: Route supported transformed imports through IRE with appropriate identification and reconciliation controls.

Incorrect Answers

B:

“Validate in a controlled test that two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts” adds a relevant safeguard or verification step rather than weakening the solution. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Confirm that two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

C:

“Route supported transformed imports through IRE with appropriate identification and reconciliation controls” is the controlled implementation, not an unsafe workaround. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Confirm that two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

E:

“Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Import sets stage data, but canonical CI matching needs identification rather than blind insert behavior. Confirm that two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

Question 216

A connector delivers last-seen timestamps in local time and the dashboard incorrectly treats current assets as stale. Which corrective design should the implementation specialist recommend?

  1. Disable age-based health checks rather than correcting time-zone normalization.
  2. Set every imported last-seen value to the current system time whether observed or not.
  3. Normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.
  4. Normalize units and validate numeric types in the transformation before writing the supported CMDB attribute.

Explanation

Correct Answer

C:

The requested CMDB/CSDM implementation concerns import data source timestamp normalization, not just a different useful platform feature. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. Validate the effect with: A known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.

Incorrect Answers

A:

“Disable age-based health checks rather than correcting time-zone normalization” would not meet the requirement. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. Instead, normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.

B:

“Set every imported last-seen value to the current system time whether observed or not” does not implement the control that the facts call for. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. Instead, normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.

D:

This addresses integration data transform type safety, an important but separate issue. It does not resolve the described import data source timestamp normalization failure. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. The targeted action is: Normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.

Question 217

A connector delivers last-seen timestamps in local time and the dashboard incorrectly treats current assets as stale. The problem persists after the attempted change. What should the specialist inspect?

  1. Inspect connector API response, integration execution log, authorized scopes, and relationship staging table.
  2. Inspect import set rows, transform mapping, IRE invocation, keys, and run summaries.
  3. Inspect import staging counts, transform error logs, key validation, and rejection reporting.
  4. Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic.

Explanation

Correct Answer

D:

Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. A known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.

Incorrect Answers

A:

“Inspect connector API response, integration execution log, authorized scopes, and relationship staging table” would not be the most direct first check for this failure. Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

B:

That inspection relates primarily to import set transform and ire integration rather than the failing import data source timestamp normalization process. The immediate evidence needed for this case is: Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic.

C:

That inspection relates primarily to import rejection quarantine process rather than the failing import data source timestamp normalization process. The immediate evidence needed for this case is: Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic.

Question 218

A connector delivers last-seen timestamps in local time and the dashboard incorrectly treats current assets as stale. Which end-to-end acceptance test establishes success?

  1. The service has documented owner, purpose, lifecycle and relationships to supported offering records.
  2. Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.
  3. A known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.
  4. A paginated test fetch returns all expected records and no CI is retired merely because it was on a later page.

Explanation

Correct Answer

C:

This tests the actual result for import data source timestamp normalization instead of merely checking whether a configuration screen can be opened. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. The test must be performed on the described CI and service scope.

Incorrect Answers

A:

This might validate non-discoverable business service ci ownership, but does not establish the acceptance requirement for import data source timestamp normalization. Instead verify: A known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.

B:

This might validate import set transform and ire integration, but does not establish the acceptance requirement for import data source timestamp normalization. Instead verify: A known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.

D:

This might validate api pagination of configuration inventory, but does not establish the acceptance requirement for import data source timestamp normalization. Instead verify: A known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.

Question 219

A connector delivers last-seen timestamps in local time and the dashboard incorrectly treats current assets as stale. Which explanation best supports the recommended solution?

  1. Partial source extracts must not be mistaken for a complete inventory snapshot when performing reconciliations.
  2. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.
  3. A source termination event and an absence of data are different, so updates need intentional lifecycle mapping.
  4. Compliance evidence should identify a verified source and review time, not pretend discovery occurred.

Explanation

Correct Answer

B:

Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. Normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.

Incorrect Answers

A:

Although relevant to api pagination of configuration inventory, this does not explain the remedy for import data source timestamp normalization. The causally relevant rule is: Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

C:

Although relevant to source deletion signal transform, this does not explain the remedy for import data source timestamp normalization. The causally relevant rule is: Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

D:

Although relevant to compliance evidence from non-discoverable ci, this does not explain the remedy for import data source timestamp normalization. The causally relevant rule is: Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

Question 220

A connector delivers last-seen timestamps in local time and the dashboard incorrectly treats current assets as stale. Select TWO proposed changes that would violate the requirement.

  1. Validate in a controlled test that a known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.
  2. Set every imported last-seen value to the current system time whether observed or not.
  3. Disable age-based health checks rather than correcting time-zone normalization.
  4. Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic.
  5. Normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.

Explanation

Correct Answer

B:

This violates the scenario constraints for import data source timestamp normalization. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. Instead the safe implementation is: Normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates.

C:

“Disable age-based health checks rather than correcting time-zone normalization” would violate the requirement. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

Incorrect Answers

A:

“Validate in a controlled test that a known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment” adds a relevant safeguard or verification step rather than weakening the solution. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

D:

“Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent. Confirm that a known UTC and local-time test payload yields the expected normalized last-seen and freshness assessment.

E:

“Normalize and validate source timestamps using a consistent time zone and conversion policy before CMDB updates” is the controlled implementation, not an unsafe workaround. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Practice Tests