Question 790
At fictional Lakeshore Finance, a storage integration engineer supporting transaction processing is evaluating block/file/object architecture and SAN transport during a production acceptance test (HPE-HPE0-J83-FOUNDATION-198). The observed storage integration issue is: A database team places latency-sensitive transactional volumes on object storage and expects block-device semantics. Which specific storage integration action best addresses the reported issue?
Explanation
Correct Answer
The most direct corrective action is: Provision a suitable block-storage service with a compatible host protocol and filesystem design. The specific problem is: A database team places latency-sensitive transactional volumes on object storage and expects block-device semantics. Expected acceptance evidence is: The database host sees a block device and its transactional writes meet the tested latency target. The underlying storage principle is: Block and object storage expose different addressing and application-access semantics.
Incorrect Answers
The HPE measure “Evaluate representative data patterns and separately measure dedupe and compression ratios.” concerns another storage task: another storage design or acceptance condition. The actual acceptance gap is that a database team places latency-sensitive transactional volumes on object storage and expects block-device semantics. Block and object storage expose different addressing and application-access semantics.
“Calculate realistic potential data loss and set RPO based on observed lag and link behavior.” would examine another storage topic: another storage design or acceptance condition. That does not resolve the stated failure: a database team places latency-sensitive transactional volumes on object storage and expects block-device semantics. Block and object storage expose different addressing and application-access semantics.
This option tests a separate storage control: another storage design or acceptance condition. The reported gap is that a database team places latency-sensitive transactional volumes on object storage and expects block-device semantics. Block and object storage expose different addressing and application-access semantics.