Question 210
At Summit Rail Authority, the production environment supports ticketing database LUNs and station file shares with separately managed development and production resources. Investigators find: A clone-heavy test environment copies full production datasets for every refresh, exhausting thin storage. The team reports that the correction is complete. Which observation BEST proves the stated problem is resolved?
Explanation
Correct Answer
Clone creation completes rapidly and allocated physical blocks grow mainly with changed data. The observation verifies that the chosen action (Use FlexClone writable point-in-time copies when supported instead of duplicating all parent data) has corrected the initiating failure (A clone-heavy test environment copies full production datasets for every refresh, exhausting thin storage). This is directly measurable for Summit Rail Authority's ticketing database LUNs and station file shares rather than merely reporting task completion.
Incorrect Answers
A forecast capacity test triggers the agreed alert before the volume or local tier becomes full. This is a valid test for another condition (A team provisions a small FlexVol for a fast-growing workload without monitoring available local-tier capacity) after a different correction (Configure suitable volume growth planning and alerts while checking available physical capacity). It does not establish the necessary result for Summit Rail Authority's ticketing database LUNs and station file shares: Clone creation completes rapidly and allocated physical blocks grow mainly with changed data.
A client lookup of the intended mount path resolves to the new volume and reads its data. This is a valid test for another condition (A NAS administrator creates a FlexVol but never mounts it in the SVM namespace and users cannot access its intended path) after a different correction (Mount the volume using an appropriate junction path within the serving SVM namespace). It does not establish the necessary result for Summit Rail Authority's ticketing database LUNs and station file shares: Clone creation completes rapidly and allocated physical blocks grow mainly with changed data.
A renamed or remounted volume remains reachable through the documented SVM namespace route. This is a valid test for another condition (A storage team grants clients direct access to an unmounted volume's internal cluster path instead of the SVM junction namespace) after a different correction (Establish a consistent SVM namespace and use junction paths for client-visible exports). It does not establish the necessary result for Summit Rail Authority's ticketing database LUNs and station file shares: Clone creation completes rapidly and allocated physical blocks grow mainly with changed data.