Question 680
Fictional Kitewell Energy runs the warehouse picking workload at a primary cluster room storage site. While completing change preflight, the field handoff documents: After a staged software change the array's event times diverge significantly from the site's centralized log collector. 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: Trend time synchronization and catch drift before maintenance windows. The recurring exposure to avoid is: Time synchronization drift makes upgrade diagnostics and service integration unreliable. A continuing effectiveness check is: Array and central log timestamps align within the customer-approved tolerance.
Incorrect Answers
The offered choice addresses: Require recovery-asset and maintenance-window verification before hardware transitions. That concerns rollback and recovery hardware readiness, rather than the specific failure described here. The deciding issue in this scenario is: Time synchronization drift makes upgrade diagnostics and service integration unreliable. The more directly applicable prevention choice is: Trend time synchronization and catch drift before maintenance windows.
This option focuses on: Validate NVRAM model numbers during hardware conversion planning. That can be relevant to nvram generation mismatch, but it does not establish the required case-specific result. The current case instead identifies: Time synchronization drift makes upgrade diagnostics and service integration unreliable. The more directly applicable prevention choice is: Trend time synchronization and catch drift before maintenance windows.
This alternative concerns: Validate both array mappings and host discovery at each connectivity change. It is associated with host device rescan after storage change, rather than the question’s determining condition. The case instead turns on: Time synchronization drift makes upgrade diagnostics and service integration unreliable. The more directly applicable prevention choice is: Trend time synchronization and catch drift before maintenance windows.