Question 320
After implementing the approved change — Use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls — the data steward needs proof that it fixed: An external inventory provides CSV files weekly and no ready connector exists. What should the steward observe?
Explanation
Correct Answer
This observation directly validates the implemented control. Staging and mapping preserve input validation and can hand CI writes to supported IRE processing. The decisive expected result is: A representative file creates or updates only the intended CI records.
Incorrect Answers
“The associated hardware CI reflects the approved disposition after the asset state changes” can be suitable where the decisive expected result is: The associated hardware CI reflects the approved disposition after the asset state changes. It does not resolve this question’s narrower failure, which follows: Staging and mapping preserve input validation and can hand CI writes to supported IRE processing. The relevant action is “A representative file creates or updates only the intended CI records”.
The alternative focuses on the technical control described by: The imported switch has the expected parent-child relationship rather than an orphan link. The present requirement is governed by: Staging and mapping preserve input validation and can hand CI writes to supported IRE processing. Apply “A representative file creates or updates only the intended CI records” to address that particular cause.
“All staged edges resolve to existing CIs after both ingestion batches complete” can be suitable where processing order and endpoint matching prevent dangling or mismatched relationship references. It does not resolve this question’s narrower failure, which follows: Staging and mapping preserve input validation and can hand CI writes to supported IRE processing. The relevant action is “A representative file creates or updates only the intended CI records”.