Question 240
A new training code version is deployed even though the pipeline passed using an older component cached result. What should be checked?
Explanation
Correct Answer
Cache reuse must reflect changes in executable dependencies; a new version should not silently consume stale outputs.
Incorrect Answers
Enable appropriate pipeline step reuse or caching for unchanged inputs and configuration. That operation would be relevant if: A preprocessing component is deterministic and expensive; rerunning an identical pipeline wastes time reproducing unchanged outputs. Its corresponding reason or verification is: Reuse can avoid recomputation when the component definition and inputs truly match an eligible prior execution. However the problem in this question is: A new training code version is deployed even though the pipeline passed using an older component cached result. The requirement instead calls for Verify component version and reuse eligibility when code or environment changes; the question-specific check is: Cache reuse must reflect changes in executable dependencies; a new version should not silently consume stale outputs.
Align upstream output and downstream input contracts with a compatible data type. A separate source case supports that approach when: A dataset preprocessing step produces a folder, but the trainer expects one tabular file. The supporting rationale or observable result is: Explicit file-versus-folder contracts prevent runtime failures caused by incompatible component output structures. This question describes a different issue: A new training code version is deployed even though the pipeline passed using an older component cached result. Address it through Verify component version and reuse eligibility when code or environment changes, with the required justification or evidence: Cache reuse must reflect changes in executable dependencies; a new version should not silently consume stale outputs.
Record pipeline component versions, parameters, inputs, outputs, and job run lineage. This is useful for the distinct issue: The operations team wants to compare end-to-end pipeline versions before rolling out a new model training flow. The relevant technical rationale or evidence for that issue is: Lineage provides a reproducible record of which executable stages and data produced the evaluated model version. Here the reported issue is: A new training code version is deployed even though the pipeline passed using an older component cached result. The relevant response is: Verify component version and reuse eligibility when code or environment changes. The first result cannot verify this different correction: Cache reuse must reflect changes in executable dependencies; a new version should not silently consume stale outputs.