The dashboard permissions model in Instana ensures secure, user-specific management of visual analytics content. IBM confirms: "By default, dashboards created by a user are private and accessible only to their creator; they can be shared explicitly with other users or teams for viewing or editing." This model supports controlled collaboration while maintaining ownership accountability. The owner may later assign permissions within the UI, typically under the Dashboard Sharing and Permissions option, defining read or write privileges per user or group. Default private scoping avoids accidental data exposure yet allows managed distribution in team settings. Public dashboards may be intentionally created as shared artifacts, but sharing must always be a conscious user action. These principles align with enterprise-grade security requirements described in the Permissions section of the dashboards documentation and remain unchanged across Instana versions.

To successfully achieve automatic correlation between frontend and backend traces, Instana requires backend services to expose a trace identity. The IBM Instana EUM and tracing correlation section confirms: "Automatic backend correlation requires exposure and propagation of the backend trace ID to connect user interaction traces with backend processing traces." When the EUM agent operates in browsers or mobile interfaces, it injects headers containing Trace and Span IDs into subsequent backend HTTP requests. Backend instrumentation must read and propagate these identifiers through service calls so Instana can unify them into a single end-to-end transaction trace. Proper correlation connects a user's session-to-service journey across web, application, and infrastructure layers, a fundamental aspect of Instana's distributed tracing model. Lacking backend trace ID propagation causes separated traces that cannot be linked, even if HTTPS, SDK, or application perspectives are configured correctly. This mechanism remains fully verified in the IBM Instana Observability Tracing Integration Guide.

According to the IBM Instana Observability documentation, an air-gapped installation is required when your environment is disconnected from the internet or has no access to external networks. The documentation states: "Air-gapped and restricted environments require deploying Instana without any connection to public repositories or backend services, assuring full isolation for compliance and regulatory requirements." The air-gapped setup ensures sensitive data or system configurations are never exposed outside the organization's internal trusted boundaries, making it mandatory for government, defense, or tightly regulated industries. Standard installation processes, including auto-update features and remote license verification, are replaced in air-gapped deployments with manual artifact and key management, as file transfers and package updates must be handled strictly within the controlled environment. The option described in B (high-speed internet) or D (unrestricted internal transfer) does not trigger air-gapping, while option A may require proxy or firewall configuration but is not entirely air-gapped unless full external access is blocked.

The IBM Instana Observability documentation clearly defines several operating modes for the host agent, with INFRASTRUCTURE mode dedicated exclusively to monitoring system-level performance data. The verified extract states: "INFRASTRUCTURE mode configures the host agent to monitor the underlying host metrics and activate sensors for the technologies running on that host without tracing application-level transactions." It collects CPU, memory, disk, network metrics, and technology integrations like Docker or OS sensors while ignoring application instrumentation. This mode reduces overhead in environments that demand system observability without full APM tracing. APM mode, conversely, extends to application traces and requests. Cloud-specific modes such as AWS or ARM designate external monitoring integrations rather than agent behavior. INFRASTRUCTURE mode thus provides base telemetry visibility as per documented design and was verified in both formulations of the Instana agent guides (v1.0.277, v1.0.307).

According to IBM Instana's integration documentation, webhook notifications support Basic Authentication by embedding the username and password into the URL as part of the standard format (https://user:password@hostname/path). The exact extract from IBM states: "For webhooks requiring basic authentication, username and password must be specified by prepending these values to the webhook hostname in the URL." This approach is supported by most HTTP libraries and ensures ease of integration with third-party endpoints. Instana also allows other advanced authentication mechanisms for webhooks, but this is the documented approach for standard Basic Auth scenarios. Additional header configuration (B) is possible but not required for basic authentication, and option D is incorrect as Basic Auth is explicitly supported (and documented). Limiting to only the Authorization header (C) oversimplifies the supported authentication workflows.