Pass ServiceNow CIS-DF Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Explanation
Correct Answer
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.
“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
“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.
“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.
“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?
Explanation
Correct Answer
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
“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.
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.
“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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
“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.
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
“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.
“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.
“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?
Explanation
Correct Answer
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
“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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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.
Explanation
Correct Answer
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.
“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
“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.
“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.
“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
- ServiceNow CIS-DF Practice Test 20 - 10 Questions (Last Reviewed 02-Nov-2026)
- ServiceNow CIS-DF Practice Test 21 - 10 Questions (Last Reviewed 01-Nov-2026)
- ServiceNow CIS-DF Practice Test 22 - 10 Questions (Last Reviewed 31-Oct-2026)
- ServiceNow CIS-DF Practice Test 23 - 10 Questions (Last Reviewed 30-Oct-2026)
- ServiceNow CIS-DF Practice Test 24 - 10 Questions (Last Reviewed 29-Oct-2026)