Question 430
Fictional Kitewell Logistics runs the project portfolio workload at a coastal facility storage site. While completing capacity change, the field handoff documents: The installer plugs a replication link into a connector assigned to another service on the target array generation. The team requires a direct technical explanation and measured acceptance check. Which preventive control most directly reduces this failure risk?
Explanation
Correct Answer
The ongoing safeguard is: Keep a model-specific port map with the physical patch schedule. The recurring exposure to avoid is: The port-number assumption does not match the model's documented service mapping. A continuing effectiveness check is: Switch and array inventories show the desired service bound to the documented correct interface.
Incorrect Answers
This alternative concerns: Add software version baselines to fleet onboarding prechecks. It is associated with pure fusion minimum release preflight, rather than the question’s determining condition. The case instead turns on: The port-number assumption does not match the model's documented service mapping. The more directly applicable prevention choice is: Keep a model-specific port map with the physical patch schedule.
This option focuses on: Test and document power paths rather than relying on cord colors. That can be relevant to power lead labeling versus actual feeds, but it does not establish the required case-specific result. The current case instead identifies: The port-number assumption does not match the model's documented service mapping. The more directly applicable prevention choice is: Keep a model-specific port map with the physical patch schedule.
This alternative concerns: Review privileged access and revoke temporary install permissions at handover. It is associated with least-privilege initial setup, rather than the question’s determining condition. The case instead turns on: The port-number assumption does not match the model's documented service mapping. The more directly applicable prevention choice is: Keep a model-specific port map with the physical patch schedule.