What should a modernization plan establish before source code, build artefacts and repositories start moving between IBM Z and target runtime environments?
Select an answer to reveal the explanation.
Short Explanation
You need secure, governed connectivity agreed up front between the mainframe, tooling, repositories, and target environments. Don't improvise network paths when code, builds, and metadata start moving.
Full Explanation
The correct answer is secure, governed connectivity between the mainframe, development tooling, repositories, and target environments, agreed up front as part of the plan. Code, builds, and metadata cross organisational and network boundaries repeatedly, so paths must be planned and secured deliberately, not assumed.
The option saying nothing specific is required is wrong because a merely working path may still be unencrypted, unauthenticated, or unmonitored; working is not the same as secure.
The option proposing a one-time firewall exception is wrong because a temporary exception left in place, or removed carelessly, either leaves a hole open or breaks the pipeline later.
The option assuming cloud default network settings meet mainframe security is wrong because defaults are rarely aligned with mainframe-grade controls and must be verified, not assumed.
For the exam, expect connectivity planning to be called out explicitly as a modernization prerequisite.