A data analyst at Cascade Regional Airlines is deciding between the Cool and Cold access tiers for a set of quarterly maintenance summary reports expected to be accessed a handful of times per year but never truly abandoned? Which factor most directly distinguishes when Cold is preferable to Cool for this data?
Select an answer to reveal the explanation.
Short Explanation
Cold sits a notch further down the shelf than Cool: an even cheaper price to just sit there, but a longer commitment before you can move it again and a bigger charge if you do reach for it. For reports touched only a handful of times a year — rarer than typical Cool traffic — that trade lands in Cold's favor.
Full Explanation
The Cold access tier is positioned between Cool and Archive: it offers a lower storage cost than Cool, making it attractive for data accessed even less frequently than a typical Cool workload, but it carries a longer minimum storage duration commitment and higher data-access costs than Cool, so it fits data like quarterly summaries touched only a few times a year rather than data read on a regular monthly or weekly cadence. Cold tier data remains online and readable without a rehydration step, which is the key distinction from Archive — Archive is offline and requires rehydration before reads succeed, while Cold, like Hot and Cool, serves reads immediately. Cold tier is available on standard general-purpose v2 accounts and is not restricted to Premium performance accounts; Premium block blob accounts, in fact, do not support Hot/Cool/Cold/Archive tiering at all. Cold and Cool are not billed identically — their storage and access cost rates differ, which is the entire reason to choose deliberately between them rather than treating the choice as cosmetic. A concrete check: review the workload's actual historical access frequency in storage analytics logs over the past year before tiering, since guessing at 'a handful of times' without data can pick the wrong tier and increase net cost.