Question 90
After deployment for scheduled flat-file import, the team sees: Repeated CSV uploads add a new rack record each month despite a stable external identifier. What explains this failure?
- Compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
- Discovery cannot reach its targets on the required probes or credentials and therefore cannot refresh host data.
- The import transform inserts target records without reliable identification or IRE processing.
- The mapping did not preserve stable identification attributes through the transform into IRE.
Explanation
Correct Answer
C:The import transform inserts target records without reliable identification or IRE processing.
Incorrect Answers
A:Compliance identifiers were not modeled on the relevant CI or related object using structured relationships. The different cause concerns the import transform inserts target records without reliable identification or IRE processing.
B:Discovery requires reachable targets and working probes or credentials; old CI records do not prove that collection is current.
D:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. The evidence points to the import transform inserts target records without reliable identification or IRE processing.
Question 91
A facilities contractor supplies a monthly CSV of network racks that cannot be automatically discovered. Which continuing operational safeguard most directly protects the intended outcome?
- Validate key mapping and reject malformed rows before promoting the recurring import schedule.
- Version and test custom ETL mappings to avoid brittle direct CMDB writes and future upgrade debt.
- Monitor schedule and MID Server/probe failures and prevent stale infrastructure inventory through documented ownership.
- Maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes.
Explanation
Correct Answer
A:Validate key mapping and reject malformed rows before promoting the recurring import schedule.
Incorrect Answers
B:Version and test custom ETL mappings to avoid brittle direct CMDB writes and future upgrade debt. It would leave validate key mapping and reject malformed rows before promoting the recurring import schedule without the specified safeguard.
C:Monitor schedule and MID Server/probe failures and prevent stale infrastructure inventory through documented ownership. It would leave validate key mapping and reject malformed rows before promoting the recurring import schedule without the specified safeguard.
D:Maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes. It would leave validate key mapping and reject malformed rows before promoting the recurring import schedule without the specified safeguard.
Question 92
A ServiceNow team is evaluating non-discoverable business context. A privacy officer maintains risk-tier labels on business application CIs that infrastructure probes cannot infer. What should it implement?
- Configure the supported connector using its guided connection and source mappings instead of building an unnecessary custom table.
- Create and steward an explicit typed relationship from the application service to the required database CI.
- Establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of technical facts.
- Ingest the file through a controlled import set and transform map that routes valid CIs through IRE.
- Design a governed IntegrationHub ETL mapping that transforms the source into appropriate CI classes and uses IRE.
Explanation
Correct Answer
C:Establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of technical facts.
Incorrect Answers
A:Configure the supported connector using its guided connection and source mappings instead of building an unnecessary custom table. That does not establish establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of.
B:Create and steward an explicit typed relationship from the application service to the required database CI. That does not establish establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of.
D:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. That does not establish establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of.
E:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. The missing change involves establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of technical facts.
Question 93
A privacy officer maintains risk-tier labels on business application CIs that infrastructure probes cannot infer. After the implementation, what evidence most directly demonstrates the intended result?
- Replay the same CSV and confirm existing CIs update without unintended duplicates or unrecognized target fields.
- Check that approved risk tier values appear on the intended business application records with steward attribution.
- Trace one control identifier from the authoritative source to its related service object and owner.
- Validate the transform preview, target class, identity mapping and IRE update results against known source records.
Explanation
Correct Answer
B:Check that approved risk tier values appear on the intended business application records with steward attribution. That distinguishes a functioning non-discoverable business context path from a configuration that was merely entered.
Incorrect Answers
A:CI deduplication depends on stable identifiers and relationships, not just visually matching names. Verification of this result involves checking that approved risk tier values appear on the intended business application records with steward attribution.
C:Reconciliation rules restrict which data sources may update each attribute of an identified CI. It does not check that approved risk tier values appear on the intended business application records with steward attribution.
D:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. It does not check that approved risk tier values appear on the intended business application records with steward attribution.
Question 94
The non-discoverable business context implementation shows an unexpected result: A discovery rescan overwrites the curated risk-tier field with blanks from a device-only source. Which underlying defect should be corrected?
- Discovery cannot reach its targets on the required probes or credentials and therefore cannot refresh host data.
- The field has no appropriate data-source ownership boundary protecting non-discoverable governance values.
- Compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
- The custom path bypasses connector mapping and the common IRE reconciliation route.
Explanation
Correct Answer
B:The field has no appropriate data-source ownership boundary protecting non-discoverable governance values.
Incorrect Answers
A:Discovery requires reachable targets and working probes or credentials; old CI records do not prove that collection is current. The evidence points to the field has no appropriate data-source ownership boundary protecting non-discoverable governance values.
C:Compliance identifiers were not modeled on the relevant CI or related object using structured relationships. The evidence points to the field has no appropriate data-source ownership boundary protecting non-discoverable governance values.
D:The failure is in the certified saas source integration path, not simply a reason to rerun an unrelated dashboard. The evidence points to the field has no appropriate data-source ownership boundary protecting non-discoverable governance values.
Question 95
A privacy officer maintains risk-tier labels on business application CIs that infrastructure probes cannot infer. Source owners and platform configurations can change. Which control is most relevant to this case?
- Maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes.
- Monitor schedule and MID Server/probe failures and prevent stale infrastructure inventory through documented ownership.
- Version and test custom ETL mappings to avoid brittle direct CMDB writes and future upgrade debt.
- Define attribute ownership and periodic certification for manually curated business facts.
Explanation
Correct Answer
D:Long-term integrity for non-discoverable business context depends on Define attribute ownership and periodic certification for manually curated business facts.
Incorrect Answers
A:Maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes. That does not establish define attribute ownership and periodic certification for manually curated business facts.
B:Monitor schedule and MID Server/probe failures and prevent stale infrastructure inventory through documented ownership. That does not establish define attribute ownership and periodic certification for manually curated business facts.
C:Version and test custom ETL mappings to avoid brittle direct CMDB writes and future upgrade debt. That does not establish define attribute ownership and periodic certification for manually curated business facts.
Question 96
During the compliance identifier provenance design review, the team describes this situation: A regulator requires an authoritative control identifier attached to affected service records, but the scanner provides only infrastructure vulnerability details. Which change should be selected?
- Design a governed IntegrationHub ETL mapping that transforms the source into appropriate CI classes and uses IRE.
- Map the approved compliance identifier to the proper CSDM-linked records through a governed source or stewardship process.
- Establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of technical facts.
- Ingest the file through a controlled import set and transform map that routes valid CIs through IRE.
Explanation
Correct Answer
B:Map the approved compliance identifier to the proper CSDM-linked records through a governed source or stewardship process.
Incorrect Answers
A:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. That does not establish map the approved compliance identifier to the proper CSDM-linked records through a governed source or stewardship process.
C:Establish a steward-owned manual or controlled integration workflow for risk tier while preserving automated discovery of technical facts. That does not establish map the approved compliance identifier to the proper CSDM-linked records through a governed source or stewardship process.
D:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. The missing change involves mapping the approved compliance identifier to the proper CSDM-linked records through a governed source or stewardship process.
Question 97
A regulator requires an authoritative control identifier attached to affected service records, but the scanner provides only infrastructure vulnerability details. A governance reviewer wants outcome evidence rather than a configuration screenshot. Which observation is decisive?
- Trace one control identifier from the authoritative source to its related service object and owner.
- Check that approved risk tier values appear on the intended business application records with steward attribution.
- Replay the same CSV and confirm existing CIs update without unintended duplicates or unrecognized target fields.
- Run a scoped discovery and confirm observed host CIs, discovered software and relationships appear under the expected classes.
Explanation
Correct Answer
A:Trace one control identifier from the authoritative source to its related service object and owner. That distinguishes a functioning compliance identifier provenance path from a configuration that was merely entered.
Incorrect Answers
B:Check that approved risk tier values appear on the intended business application records with steward attribution. That check cannot demonstrate attribute-level source authority and update precedence.
C:CI deduplication depends on stable identifiers and relationships, not just visually matching names. Verification of this result involves tracing one control identifier from the authoritative source to its related service object and owner.
D:Run a scoped discovery and confirm observed host CIs, discovered software and relationships appear under the expected classes. That check cannot demonstrate attribute-level source authority and update precedence.
Question 98
After deployment for compliance identifier provenance, the team sees: A compliance report cannot join control IDs to the impacted services because the IDs were stored only in a free-text ticket. What explains this failure?
- Compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
- The import transform inserts target records without reliable identification or IRE processing.
- The mapping did not preserve stable identification attributes through the transform into IRE.
- The field has no appropriate data-source ownership boundary protecting non-discoverable governance values.
Explanation
Correct Answer
A:Compliance identifiers were not modeled on the relevant CI or related object using structured relationships. The underlying failure instead involves compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
Incorrect Answers
B:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. That mechanism cannot explain compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
C:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. The underlying failure instead involves compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
D:The field has no appropriate data-source ownership boundary protecting non-discoverable governance values. That mechanism cannot explain compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
Question 99
A regulator requires an authoritative control identifier attached to affected service records, but the scanner provides only infrastructure vulnerability details. Which continuing operational safeguard most directly protects the intended outcome?
- Prefer maintained certified connectors where available and document connector owner, credentials and update cadence.
- Maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes.
- Monitor schedule and MID Server/probe failures and prevent stale infrastructure inventory through documented ownership.
- Version and test custom ETL mappings to avoid brittle direct CMDB writes and future upgrade debt.
Explanation
Correct Answer
B:Maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes.
Incorrect Answers
A:It preserves the certified saas source integration decision when data sources, policies or operational owners change. It would leave maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes without the specified safeguard.
C:Monitor schedule and MID Server/probe failures and prevent stale infrastructure inventory through documented ownership. It would leave maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes without the specified safeguard.
D:Version and test custom ETL mappings to avoid brittle direct CMDB writes and future upgrade debt. It would leave maintain the regulatory identifier's owner, scope and evidence refresh process as the service structure changes without the specified safeguard.
Question 100
A ServiceNow team is evaluating transform-to-class correctness. An import source sends device_type values server, router and database, but its transform map targets a single generic CI class. What should it implement?
- Design a governed IntegrationHub ETL mapping that transforms the source into appropriate CI classes and uses IRE.
- Map each source device type to the appropriate destination class before running the IRE identification step.
- Map source associations into valid cmdb_rel_ci relationship types with the correct source and target CI identities.
- Call CMDBTransformUtil in an onBefore transform script with the intended data source and suppress duplicate raw target insertion.
Explanation
Correct Answer
B:The Identification and Reconciliation Engine checks identity before a CI is created, preventing a raw import from duplicating the record. The missing change involves mapping each source device type to the appropriate destination class before running the IRE identification step.
Incorrect Answers
A:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. The missing change involves mapping each source device type to the appropriate destination class before running the IRE identification step.
C:Typed CMDB relationships connect CI endpoints with an explicit supported relationship type and direction. That does not establish IRE-based matching instead of uncontrolled duplicate insertion.
D:CI deduplication depends on stable identifiers and relationships, not just visually matching names. The missing change involves mapping each source device type to the appropriate destination class before running the IRE identification step.
Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Practice Tests