What is the risk of beginning a self-hosted Instana installation before the documented storage requirements are met?
Select an answer to reveal the explanation.
Short Explanation
The dangerous case isn't a failed install—it's one that works in the pilot and quietly loses data under real load. If you start with too little storage, the backend can look healthy and then drop telemetry when real ingest volume arrives.
Full Explanation
The correct answer is the option stating that the backend may install and then fail or begin discarding telemetry once real ingest volume arrives, producing gaps in exactly the data teams rely on. Insufficient storage typically surfaces under production load rather than during installation. The result is a monitoring system that appears healthy while dropping or truncating data, which is worse than a clear failure because teams trust what they see.
The installer-refuses-to-run option is incorrect because prerequisite shortfalls are not always blocking; a light pilot workload can run happily on undersized storage.
The agents-connect-but-cannot-authenticate option is incorrect because storage capacity and agent authentication are unrelated concerns.
The retention-locked option is incorrect because retention remains configurable, though shortening it under storage pressure is a forced compromise rather than a design decision.
Exam caveat: associate skipped prerequisites with silent data loss under load rather than with an obvious installation failure.