A team preparing a production rollout wants to avoid connectivity problems surfacing late. What should the plan get right early?
Select an answer to reveal the explanation.
Short Explanation
Get connectivity settled deliberately, early, before your pipeline is quietly depending on whoever's laptop happens to have access. Define and secure the network paths between IBM Z, the development tooling, the repositories, and the target environments before the rollout leans on them.
Full Explanation
Define and secure the network paths between IBM Z, the development tooling, the repositories, and the target environments before the pipeline depends on them. Planning secure, governed connectivity up front avoids the pipeline relying on undocumented, ad-hoc access that breaks or gets flagged later. The cloud-hosted assumption is wrong because cloud hosting does not make connectivity automatic; network paths, identities, and permissions still need configuration. Delaying until a production incident is wrong because it discovers the gap the expensive way, in production. Relying on individual ad-hoc access is wrong because it is fragile and unauditable, exactly what proper planning replaces. For the exam, connectivity planning is a rollout prerequisite, not a fallback.