Question 90
Fictional Rosehaven Research runs the student records workload at a remote operations wing storage site. While completing hardware modernization, the field handoff documents: The receiving team counts boxes but does not compare their part numbers and serials with the approved implementation workbook. 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: Add serial and component reconciliation to the preflight go or no-go checklist. The recurring exposure to avoid is: A physical delivery check cannot verify that the ordered supported configuration actually arrived. A continuing effectiveness check is: The reconciled inventory matches order line items or contains a documented support-approved exception.
Incorrect Answers
This option focuses on: Confirm software media and entitlement during the pre-visit readiness review. That can be relevant to installation software artifact availability, but it does not establish the required case-specific result. The current case instead identifies: A physical delivery check cannot verify that the ordered supported configuration actually arrived. The more directly applicable prevention choice is: Add serial and component reconciliation to the preflight go or no-go checklist.
The offered choice addresses: Add a dedicated file-service readiness row to the site workbook. That concerns flasharray file network prerequisites, rather than the specific failure described here. The deciding issue in this scenario is: A physical delivery check cannot verify that the ordered supported configuration actually arrived. The more directly applicable prevention choice is: Add serial and component reconciliation to the preflight go or no-go checklist.
This option focuses on: Capture cabinet depth and rail part numbers during pre-install site survey. That can be relevant to rail-depth compatibility, but it does not establish the required case-specific result. The current case instead identifies: A physical delivery check cannot verify that the ordered supported configuration actually arrived. The more directly applicable prevention choice is: Add serial and component reconciliation to the preflight go or no-go checklist.