This object indicates whether a check entry, and its associated rules, is stored in volatile memory, lost on reboot, or backed by non-volatile or permanent storage, with permanent(4) implying all objects whose MAX-ACCESS is read-create in that row become effectively unchangeable per the description. An admin configuring checks meant to survive a device restart must explicitly set this to a non-volatile storage type, since leaving it at a volatile default would mean the entire check disappears the next time the device reboots, a common surprise for admins expecting persistent monitoring configuration. A critical threshold check an admin wants surviving a power cycle should have this object set to nonVolatile(3) rather than left at the default volatile(2).