What is the consequence of deferring retention planning until storage is full?
Select an answer to reveal the explanation.
Short Explanation
You still make the retention call, just under pressure, and it often turns into emergency cuts or data loss instead of a solid policy.
Full Explanation
Capacity exhaustion converts a planning question into an incident. The correct choice is the one saying the decision is made under pressure, with likely outcomes being emergency retention cuts or data loss rather than a considered policy. The available responses are abrupt retention reduction or accepting loss, and compliance obligations may make the first of those unavailable. The option claiming the backend automatically extends storage when capacity is reached is incorrect because storage does not expand by itself in a self-hosted deployment. The option claiming retention becomes fixed and can no longer be adjusted is incorrect because retention remains configurable; the constraint is circumstantial. The option claiming agents stop collecting telemetry until storage is expanded is incorrect because agents continue sending regardless of backend capacity, which is part of what makes the situation urgent. For the exam, plan retention alongside sizing rather than reactively.