Which statement best summarises the planning that should precede a self-hosted Instana installation?
Select an answer to reveal the explanation.
Short Explanation
You've got three things to nail before you start: meet the prerequisites, size the backend for telemetry and retention, and settle the availability of supporting services. Each one is cheap now and expensive later.
Full Explanation
The best summary is verifying the documented prerequisites, sizing the backend for expected telemetry and retention, and settling the availability of supporting services before the install starts. These three items together determine whether the backend installs cleanly, keeps up with real telemetry, and survives component failure. Each is substantially harder to change once the deployment is carrying production load.
Installing with defaults and revisiting prerequisites, sizing and availability once teams report problems is wrong because a defaults-first approach defers exactly the decisions that are costly to reverse, and the symptoms surface as lost data rather than clear errors.
The claim that planning is only required for software-as-a-service deployments, where the vendor needs the details in advance, is wrong because the vendor-managed model removes most of this burden; it is the self-hosted model that makes the organisation responsible for it.
Confirming that agents are available for the relevant platforms is not sufficient preparation because agent platform support matters but is a separate concern from backend readiness.
For the exam, be able to list prerequisites, sizing and availability as the pre-installation checklist for self-hosted Instana.