Question 320
Fictional Nobleford Logistics runs the media archiving workload at a district hub storage site. While completing support handoff, the field handoff documents: A field engineer selects the newest available Purity image without checking compatibility with the new controller and installed shelves. 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: Freeze an approved target release in the installation work package. The recurring exposure to avoid is: Software version selection has not been checked against the deployment's hardware support matrix. A continuing effectiveness check is: System version and module inventory align with the approved compatibility record after install.
Incorrect Answers
The offered choice addresses: Reserve cable slack and service access in rack-elevation design. That concerns safe shelf placement and service access, rather than the specific failure described here. The deciding issue in this scenario is: Software version selection has not been checked against the deployment's hardware support matrix. The more directly applicable prevention choice is: Freeze an approved target release in the installation work package.
This option focuses on: Include blanking and cable airflow inspection in physical installation signoff. That can be relevant to rack blanking and airflow paths, but it does not establish the required case-specific result. The current case instead identifies: Software version selection has not been checked against the deployment's hardware support matrix. The more directly applicable prevention choice is: Freeze an approved target release in the installation work package.
This alternative concerns: Keep a model-specific port map with the physical patch schedule. It is associated with physical port role mapping, rather than the question’s determining condition. The case instead turns on: Software version selection has not been checked against the deployment's hardware support matrix. The more directly applicable prevention choice is: Freeze an approved target release in the installation work package.