Question 100
Fictional Thornhill Research runs the customer onboarding workload at a central campus storage site. While completing migration readiness, the field handoff documents: A customer expects a new DirectFlash Shelf to attach to an older array without consulting the supported hardware matrix. 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: Recheck model compatibility whenever the BOM or target software release changes. The recurring exposure to avoid is: The planned array-shelf pairing has not been validated for model generation and Purity interoperability. A continuing effectiveness check is: The exact array generation shelf type and software version appear together in an approved compatibility plan.
Incorrect Answers
This alternative concerns: Set a formal last-valid revision check before dispatch and maintenance execution. It is associated with implementation workbook signoff, rather than the question’s determining condition. The case instead turns on: The planned array-shelf pairing has not been validated for model generation and Purity interoperability. The more directly applicable prevention choice is: Recheck model compatibility whenever the BOM or target software release changes.
The offered choice addresses: Inspect both cabinet faces against maintenance diagrams during the site survey. That concerns front and rear service clearance, rather than the specific failure described here. The deciding issue in this scenario is: The planned array-shelf pairing has not been validated for model generation and Purity interoperability. The more directly applicable prevention choice is: Recheck model compatibility whenever the BOM or target software release changes.
This option focuses on: Review support-egress architecture with network security before installation. That can be relevant to pure1 egress through a site proxy, but it does not establish the required case-specific result. The current case instead identifies: The planned array-shelf pairing has not been validated for model generation and Purity interoperability. The more directly applicable prevention choice is: Recheck model compatibility whenever the BOM or target software release changes.