Question 710
Fictional Quartzlake Energy runs the point-of-sale reconciliation workload at a southern region storage site. While completing post-install acceptance, the field handoff documents: A sanctioned post-upgrade volume presentation is completed but one host has not refreshed its device discovery and still cannot see the mapped LUN. 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: Validate both array mappings and host discovery at each connectivity change. The recurring exposure to avoid is: The operating-system device inventory has not reconciled with the approved storage presentation. A continuing effectiveness check is: The host reports the intended device WWID or NAA identifier and healthy redundant paths.
Incorrect Answers
The offered choice addresses: Treat each array family change as a new physical and interoperability review. That concerns x to xl modernization constraints, rather than the specific failure described here. The deciding issue in this scenario is: The operating-system device inventory has not reconciled with the approved storage presentation. The more directly applicable prevention choice is: Validate both array mappings and host discovery at each connectivity change.
This alternative concerns: Trend time synchronization and catch drift before maintenance windows. It is associated with ntp clock skew during upgrade, rather than the question’s determining condition. The case instead turns on: The operating-system device inventory has not reconciled with the approved storage presentation. The more directly applicable prevention choice is: Validate both array mappings and host discovery at each connectivity change.
The offered choice addresses: Include replication health and remote-site owners in change approval. That concerns replication health before upgrade, rather than the specific failure described here. The deciding issue in this scenario is: The operating-system device inventory has not reconciled with the approved storage presentation. The more directly applicable prevention choice is: Validate both array mappings and host discovery at each connectivity change.