During a pilot, an administrator finds that the repository sync job worked only because an engineer manually copied a credentials file onto the target host. What does this finding indicate?
Select an answer to reveal the explanation.
Short Explanation
If a sync job only works because someone hand-carried credentials onto a box, you didn't design secure connectivity—you worked around it. That ad-hoc credential copy means the pipeline isn't production-ready.
Full Explanation
Correct: secure connectivity between the mainframe environment and the target was never properly planned or automated, so the pipeline is running on an ad-hoc workaround. A manually placed credentials file is the kind of improvisation that appears when automated connectivity between environments was skipped during planning. The claim that the pilot is functioning exactly as intended and the workaround can stay in place for production is wrong because an undocumented manual workaround is fragile, unauditable, and will not survive being handed to a production team. The claim that the target environment's storage is undersized for the transformed application is wrong because storage sizing is unrelated to how credentials reached the host. The claim that the COBOL source itself contains a defect that the copy uncovered is wrong because the finding is about the connectivity mechanism, not the source code's correctness. For the exam, read manual credential handling as a signal of missing connectivity planning.