ServiceNow CIS-DF Practice Test 21 - 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 21

Question 200

Cloud Discovery and a third-party connector both populate the same EC2 instance as separate CIs after integration rollout. Which TWO actions would be unsuitable or unsafe?

  1. Inspect cloud instance ID normalization, class choice, source labels, IRE log, and duplicate list.
  2. Match only on changing instance private IP and ignore stable instance IDs.
  3. Validate in a controlled test that after both feeds run, one instance CI remains and source-specific attributes are traceable.
  4. Disable identification checks and add a separate CMDB table per cloud source.
  5. Align both providers with stable cloud instance identifiers and supported IRE identification/reconciliation rules.

Explanation

Correct Answer

B:

“Match only on changing instance private IP and ignore stable instance IDs” would violate the requirement. Multiple observation tools should converge on one logical CI when their identifiers describe the same underlying resource.

D:

This violates the scenario constraints for discovery and connector source deduplication. Multiple observation tools should converge on one logical CI when their identifiers describe the same underlying resource. Instead the safe implementation is: Align both providers with stable cloud instance identifiers and supported IRE identification/reconciliation rules.

Incorrect Answers

A:

“Inspect cloud instance ID normalization, class choice, source labels, IRE log, and duplicate list” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Multiple observation tools should converge on one logical CI when their identifiers describe the same underlying resource.

C:

“Validate in a controlled test that after both feeds run, one instance CI remains and source-specific attributes are traceable” adds a relevant safeguard or verification step rather than weakening the solution. Multiple observation tools should converge on one logical CI when their identifiers describe the same underlying resource.

E:

“Align both providers with stable cloud instance identifiers and supported IRE identification/reconciliation rules” is the controlled implementation, not an unsafe workaround. Multiple observation tools should converge on one logical CI when their identifiers describe the same underlying resource. Confirm that after both feeds run, one instance CI remains and source-specific attributes are traceable.

Question 201

A cloud environment creates and terminates resources frequently, but a weekly discovery schedule leaves retired instances visible as active. Which corrective design should the implementation specialist recommend?

  1. Inspect source API scopes and connector staging payloads, then grant only the supported topology-read permissions.
  2. Mark every temporarily unreachable instance retired immediately without a verification window.
  3. Choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling.
  4. Increase the weekly dashboard refresh rate without changing CI source collection.

Explanation

Correct Answer

C:

The requested CMDB/CSDM implementation concerns event-driven versus scheduled ci updates, not just a different useful platform feature. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Validate the effect with: A created test instance appears promptly and its termination moves it into the intended lifecycle state.

Incorrect Answers

A:

This addresses service graph connector payload errors, an important but separate issue. It does not resolve the described event-driven versus scheduled ci updates failure. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. The targeted action is: Choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling.

B:

“Mark every temporarily unreachable instance retired immediately without a verification window” does not implement the control that the facts call for. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Instead, choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling.

D:

“Increase the weekly dashboard refresh rate without changing CI source collection” does not implement the control that the facts call for. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Instead, choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling.

Question 202

A cloud environment creates and terminates resources frequently, but a weekly discovery schedule leaves retired instances visible as active. The problem persists after the attempted change. What should the specialist inspect?

  1. Inspect certified connector coverage, supported source version, credential scope, and CMDB staging logs.
  2. Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices.
  3. Inspect connector customization records, extension documentation, update sets, and integration test results.
  4. Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy.

Explanation

Correct Answer

D:

Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. A created test instance appears promptly and its termination moves it into the intended lifecycle state.

Incorrect Answers

A:

“Inspect certified connector coverage, supported source version, credential scope, and CMDB staging logs” would not be the most direct first check for this failure. Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy.

B:

That inspection relates primarily to discovery creates ci without topology links rather than the failing event-driven versus scheduled ci updates process. The immediate evidence needed for this case is: Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy.

C:

That inspection relates primarily to connector upgradeability and customization rather than the failing event-driven versus scheduled ci updates process. The immediate evidence needed for this case is: Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy.

Question 203

A cloud environment creates and terminates resources frequently, but a weekly discovery schedule leaves retired instances visible as active. Which end-to-end acceptance test establishes success?

  1. A created test instance appears promptly and its termination moves it into the intended lifecycle state.
  2. Service maps and queries show the database dependency under the intended relationship category.
  3. A test cloud asset enters the appropriate class with its source identity and stable identifiers after scheduled sync.
  4. The next pilot run includes expected machine and network relationships without overbroad credentials.

Explanation

Correct Answer

A:

This tests the actual result for event-driven versus scheduled ci updates instead of merely checking whether a configuration screen can be opened. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. The test must be performed on the described CI and service scope.

Incorrect Answers

B:

The choice “Service maps and queries show the database dependency under the intended relationship category” concerns relationship type selection for dependency; it does not resolve the stated requirement. A created test instance appears promptly and its termination moves it into the intended lifecycle state.

C:

This might validate service graph connector for supported source, but does not establish the acceptance requirement for event-driven versus scheduled ci updates. Instead verify: A created test instance appears promptly and its termination moves it into the intended lifecycle state.

D:

This might validate service graph connector payload errors, but does not establish the acceptance requirement for event-driven versus scheduled ci updates. Instead verify: A created test instance appears promptly and its termination moves it into the intended lifecycle state.

Question 204

A cloud environment creates and terminates resources frequently, but a weekly discovery schedule leaves retired instances visible as active. Which explanation best supports the recommended solution?

  1. Out-of-box integration code can be overwritten during upgrades; isolated mappings reduce long-term technical debt.
  2. Supported connector patterns can provide maintained schemas and CMDB integration conventions with less custom technical debt.
  3. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics.
  4. A source termination event and an absence of data are different, so updates need intentional lifecycle mapping.

Explanation

Correct Answer

C:

Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling. The decisive evidence is that a created test instance appears promptly and its termination moves it into the intended lifecycle state.

Incorrect Answers

A:

Although relevant to connector upgradeability and customization, this does not explain the remedy for event-driven versus scheduled ci updates. The causally relevant rule is: Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics.

B:

Although relevant to service graph connector for supported source, this does not explain the remedy for event-driven versus scheduled ci updates. The causally relevant rule is: Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics.

D:

Although relevant to source deletion signal transform, this does not explain the remedy for event-driven versus scheduled ci updates. The causally relevant rule is: Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics.

Question 205

A cloud environment creates and terminates resources frequently, but a weekly discovery schedule leaves retired instances visible as active. Select TWO proposed changes that would violate the requirement.

  1. Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy.
  2. Increase the weekly dashboard refresh rate without changing CI source collection.
  3. Choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling.
  4. Mark every temporarily unreachable instance retired immediately without a verification window.
  5. Validate in a controlled test that a created test instance appears promptly and its termination moves it into the intended lifecycle state.

Explanation

Correct Answer

B:

This violates the scenario constraints for event-driven versus scheduled ci updates. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Instead the safe implementation is: Choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling.

D:

“Mark every temporarily unreachable instance retired immediately without a verification window” would violate the requirement. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics.

Incorrect Answers

A:

“Inspect connector polling interval, event subscription, deletion signals, last-seen timestamps and policy” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics.

C:

“Choose an appropriate supported event-driven connector or sufficiently frequent scheduled ingestion with lifecycle handling” is the controlled implementation, not an unsafe workaround. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Confirm that a created test instance appears promptly and its termination moves it into the intended lifecycle state.

E:

“Validate in a controlled test that a created test instance appears promptly and its termination moves it into the intended lifecycle state” adds a relevant safeguard or verification step rather than weakening the solution. Ingestion frequency affects freshness, but a refresh alone also needs correct update and retirement semantics. Confirm that a created test instance appears promptly and its termination moves it into the intended lifecycle state.

Question 206

An imported cloud asset payload uses vendor field names that do not map to CMDB class attributes, leaving key fields empty. Which ServiceNow implementation decision best addresses the requirement?

  1. Write source properties directly into arbitrary dictionary fields that happen to share similar names.
  2. Map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output.
  3. Set every unmapped field to a placeholder string and ignore source semantics.
  4. Map each offering to the appropriate CSDM service hierarchy and assign the required ownership and offering attributes.

Explanation

Correct Answer

B:

The requested CMDB/CSDM implementation concerns integrationhub etl transform mapping, not just a different useful platform feature. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. Validate the effect with: A test record populates stable CI attributes and preserves the intended source identifier after transform.

Incorrect Answers

A:

“Write source properties directly into arbitrary dictionary fields that happen to share similar names” does not implement the control that the facts call for. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. Instead, map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output.

C:

“Set every unmapped field to a placeholder string and ignore source semantics” would not meet the requirement. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. Instead, map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output.

D:

This addresses manual csdm classification of offering, an important but separate issue. It does not resolve the described integrationhub etl transform mapping failure. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. The targeted action is: Map source fields to the intended target class through supported IntegrationHub ETL transforms and validate IRE output.

Question 207

An imported cloud asset payload uses vendor field names that do not map to CMDB class attributes, leaving key fields empty. After an initial fix fails, which evidence should the team investigate first?

  1. Inspect source termination status, ETL mapping, lifecycle transition policy, and last-seen history.
  2. Inspect discovery credentials, MID Server reachability, pattern execution, and CI update history.
  3. Inspect import staging counts, transform error logs, key validation, and rejection reporting.
  4. Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response.

Explanation

Correct Answer

D:

Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. A test record populates stable CI attributes and preserves the intended source identifier after transform.

Incorrect Answers

A:

That inspection relates primarily to source deletion signal transform rather than the failing integrationhub etl transform mapping process. The immediate evidence needed for this case is: Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response.

B:

“Inspect discovery credentials, MID Server reachability, pattern execution, and CI update history” would not be the most direct first check for this failure. Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response.

C:

That inspection relates primarily to import rejection quarantine process rather than the failing integrationhub etl transform mapping process. The immediate evidence needed for this case is: Inspect ETL mapping rules, sample payload, class target, transformed JSON, and IRE response.

Question 208

An imported cloud asset payload uses vendor field names that do not map to CMDB class attributes, leaving key fields empty. What observed outcome most convincingly validates the correction?

  1. A test application and server appear as properly identified records with their intended relationship.
  2. A test record populates stable CI attributes and preserves the intended source identifier after transform.
  3. The batch application dependency appears correctly in queries and is subject to owner review on schedule.
  4. Two runs of the same source spreadsheet update the same intended CIs and do not grow duplicate counts.

Explanation

Correct Answer

B:

This tests the actual result for integrationhub etl transform mapping instead of merely checking whether a configuration screen can be opened. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation. The test must be performed on the described CI and service scope.

Incorrect Answers

A:

This might validate integrationhub etl relationship mapping, but does not establish the acceptance requirement for integrationhub etl transform mapping. Instead verify: A test record populates stable CI attributes and preserves the intended source identifier after transform.

C:

This might validate manual application dependency relation, but does not establish the acceptance requirement for integrationhub etl transform mapping. Instead verify: A test record populates stable CI attributes and preserves the intended source identifier after transform.

D:

This might validate import set transform and ire integration, but does not establish the acceptance requirement for integrationhub etl transform mapping. Instead verify: A test record populates stable CI attributes and preserves the intended source identifier after transform.

Question 209

An imported cloud asset payload uses vendor field names that do not map to CMDB class attributes, leaving key fields empty. Which technical principle explains the right implementation approach?

  1. Canonical manufacturer and model references allow consistent asset and configuration reporting across multiple providers.
  2. Ignoring rejected records can make a technically completed import produce an incomplete CMDB representation.
  3. Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.
  4. Time-zone errors can corrupt age-based staleness assessments even when the source observation was recent.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

Although relevant to asset model normalization before cmdb ingest, this does not explain the remedy for integrationhub etl transform mapping. The causally relevant rule is: Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

B:

Although relevant to import rejection quarantine process, this does not explain the remedy for integrationhub etl transform mapping. The causally relevant rule is: Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

D:

Although relevant to import data source timestamp normalization, this does not explain the remedy for integrationhub etl transform mapping. The causally relevant rule is: Staging and transformation translate source schema into CMDB semantics before canonical identification and reconciliation.

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.

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