Question 660
Fictional Goldcrest Energy runs the regional reporting workload at a metro data hall storage site. While completing service continuity review, the field handoff documents: A proposed target release changes requirements for a feature used by the customer's file and replication services. 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: Maintain an inventory of enabled features against future software changes. The recurring exposure to avoid is: The upgrade plan omitted a feature-by-feature compatibility check. A continuing effectiveness check is: Documented tests show critical replication and file workflows operate on the approved target release.
Incorrect Answers
This option focuses on: Use observed workload patterns to choose future data-movement windows. That can be relevant to performance impact of long evacuations, but it does not establish the required case-specific result. The current case instead identifies: The upgrade plan omitted a feature-by-feature compatibility check. The more directly applicable prevention choice is: Maintain an inventory of enabled features against future software changes.
This alternative concerns: Add site-specific identity reachability tests to Fusion onboarding. It is associated with fusion ldap domain integration, rather than the question’s determining condition. The case instead turns on: The upgrade plan omitted a feature-by-feature compatibility check. The more directly applicable prevention choice is: Maintain an inventory of enabled features against future software changes.
The offered choice addresses: Plan capacity conversions using realistic data movement and onsite staging assumptions. That concerns multi-visit transition sequencing, rather than the specific failure described here. The deciding issue in this scenario is: The upgrade plan omitted a feature-by-feature compatibility check. The more directly applicable prevention choice is: Maintain an inventory of enabled features against future software changes.