Question 570
At fictional Lakeshore Finance, a storage integration engineer supporting transaction processing is evaluating customer storage sizing and solution requirements during an incident response drill (HPE-HPE0-J83-PLAN-143). The observed storage integration issue is: A client asks for file shares across offices but the architecture only specifies array block capacity. Which recurring preventive or detective control would most directly reduce recurrence?
Explanation
Correct Answer
The specific preventive or detective safeguard is: Validate NFS or SMB access and locking with application owners. It reduces the risk of: A client asks for file shares across offices but the architecture only specifies array block capacity. The associated correction is: Document named-file protocol namespace and cross-site client behavior before product selection. Successful implementation would show: Authorized clients access the expected files using the selected supported service.
Incorrect Answers
The choice “Review data placement and backup destinations with governance stakeholders.” evaluates another aspect of the storage design: Identify allowed storage and backup jurisdictions before selecting targets or services. The current problem is that a client asks for file shares across offices but the architecture only specifies array block capacity. Document named-file protocol namespace and cross-site client behavior before product selection.
The HPE measure “Reassess data temperature and placement as workloads evolve.” concerns another storage task: Classify applications by latency throughput access frequency and recovery objectives before assigning tiers. The actual acceptance gap is that a client asks for file shares across offices but the architecture only specifies array block capacity. Document named-file protocol namespace and cross-site client behavior before product selection.
This option tests a separate storage control: Validate supported replication consistency host behavior and witness topology. The reported gap is that a client asks for file shares across offices but the architecture only specifies array block capacity. Document named-file protocol namespace and cross-site client behavior before product selection.