A school district wants to stop surprise dynamic volumes from expensive default storage. Which admin control directly addresses that risk?
Select an answer to reveal the explanation.
Short Explanation
If the cafeteria’s “default meal” is the pricey steak plate, change what’s marked default—or require an explicit order. Same for StorageClass: manage the is-default-class annotation so forgotten storageClassName fields don’t mint expensive disks. Killing CSI or scaling apps to zero just breaks things while the default still lurks.
Full Explanation
Administrators control default dynamic provisioning by annotating which StorageClass is default or by ensuring none is default so PVCs must name a class explicitly. Removing the CSI driver without fixing defaults, scaling workloads to zero, or renaming PVs does not correctly manage default StorageClass behavior.