Question 450
At the Oakport cloud operations center, an external workflow uploads a package using the expected name but there is no evidence of its build origin. Which issue is most directly indicated by the facts?
Explanation
Correct Answer
The critical gap is that a familiar filename alone is not proof that the binary came from the approved build. At the Oakport cloud operations center, correcting that gap requires the team to require trusted provenance or signature checks before admitting artifacts to release stages.
Incorrect Answers
That statement concerns github azure pipelines repository connection; here the reported facts point to a different issue: a familiar filename alone is not proof that the binary came from the approved build. For the Oakport cloud operations center, the priority is to require trusted provenance or signature checks before admitting artifacts to release stages.
This explanation belongs to iac deployment identity. The immediate weakness in the question is that a familiar filename alone is not proof that the binary came from the approved build. For the Oakport cloud operations center, the priority is to require trusted provenance or signature checks before admitting artifacts to release stages.
Although floating transitive versions make artifacts nonreproducible despite unchanged application source, the situation does not describe that specific cause; it instead indicates that a familiar filename alone is not proof that the binary came from the approved build. For the Oakport cloud operations center, the priority is to require trusted provenance or signature checks before admitting artifacts to release stages.