Why should DNS and certificate planning be part of a self-hosted Instana installation plan rather than a follow-up task?
Select an answer to reveal the explanation.
Short Explanation
You can install Instana and still have nothing connect. Agents and users reach the backend by name over TLS, so DNS and certificate trust have to be planned up front.
Full Explanation
The correct answer is the statement that agents and users connect to the backend by name over TLS, so unresolvable names or untrusted certificates prevent the deployment from functioning even when it installed successfully. Agent-to-backend and user-to-backend traffic both depend on resolvable hostnames and certificates the clients trust. Getting either wrong produces a backend that is running but effectively unreachable, and diagnosing that after the fact costs far more than planning it.
The claim that Instana cannot be installed at all until a certificate authority has been configured is incorrect because the installation process itself can proceed; the failure appears at connection time, which is what makes it easy to overlook.
The claim that certificates determine how much telemetry storage the backend allocates is incorrect because certificates are about identity and encryption and have no relationship to storage allocation.
The claim that DNS records are required only for SaaS deployments, not self-hosted ones, is incorrect because self-hosted deployments have a greater DNS burden, not a lesser one, since the organisation supplies the names itself.
For the exam, count network reachability, name resolution and certificate trust among the installation prerequisites.