Question 620
During HPE storage deployment, the following occurs: A CSI storage class requests unsupported read-write-many behavior. What is the most focused next step?
Explanation
Correct Answer
The most focused response is: Match persistent volume access mode to the underlying service. The implicated technical boundary is that storage plugins cannot override block writer concurrency limits. An integrator can verify the change through the following outcome: Volumes attach only to supported permitted nodes.
Incorrect Answers
This choice concerns Virtualization, containers and persistent storage, for example: A stateful service loses records when its pod moves workers. The current storage issue instead hinges on storage plugins cannot override block writer concurrency limits. The appropriate evidence is volumes attach only to supported permitted nodes.
Although this option is reasonable for 'A VM snapshot is treated as application-consistent without guest coordination.', it is not the specific dependency in the stem. Its action is use application-aware backup coordination where required. The stem is resolved more directly by match persistent volume access mode to the underlying service.
The choice tests a neighboring capability: Storage mapping and host path handling jointly determine VM availability. The proposed correction would apply to 'A virtualized datastore uses an unsupported multipath plugin.' but this incident needs match persistent volume access mode to the underlying service. and a successful test that volumes attach only to supported permitted nodes.