Question 50
During HPE storage deployment, the following occurs: A Kubernetes pod writes only to ephemeral container layers. What is the most focused next step?
Explanation
Correct Answer
The most focused response is: Use supported CSI persistent volumes with appropriate lifecycle controls. The implicated technical boundary is that container filesystems are ephemeral unless durable volumes are explicitly provided. An integrator can verify the change through the following outcome: Data remains after a rescheduled pod starts.
Incorrect Answers
This choice concerns Virtualization, containers and persistent storage, for example: A virtualized datastore uses an unsupported multipath plugin. The current storage issue instead hinges on container filesystems are ephemeral unless durable volumes are explicitly provided. The appropriate evidence is data remains after a rescheduled pod starts.
Although this option is reasonable for 'Multiple Kubernetes replicas mount a single-writer block volume simultaneously.', it is not the specific dependency in the stem. Its action is match persistent volume access mode to the underlying service. The stem is resolved more directly by use supported CSI persistent volumes with appropriate lifecycle controls.
The choice tests a neighboring capability: Transparent failover requires coherent storage ownership across sites. The proposed correction would apply to 'Disconnected storage arrays both grant write ownership to hosts.' but this incident needs use supported CSI persistent volumes with appropriate lifecycle controls. and a successful test that data remains after a rescheduled pod starts.