I85PREP
⌘ K
IBM Instana Observability Administrator - Professional study materials
IBM Instana Observability Administrator - Professional study resources

IBM Instana Observability Administrator - Professional practice questions

One question at a time. Build your IBM Instana Observability Administrator - Professional understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Installation, Deployment, and Upgrade of Instana Agents and Hosts

A Linux host must run the Instana agent under a non-root service account for security compliance. Which requirement must be satisfied before the agent can monitor process and container data on that host?

  1. The agent must be upgraded to a dynamic agent image rather than a static installer.
  2. The host must be registered in the Instana UI as a containerized host before the agent starts.
  3. The agent user must be granted the capabilities or group memberships needed to read process and container metadata, since a non-root agent cannot access all host telemetry by default. Correct answer.
  4. The agent must be installed with the --rootless flag so it writes configuration to the user home directory instead of /opt/instana.

Explanation

The Instana host agent normally runs as root because it inspects process tables, container runtimes, and kernel-level metrics. When a non-root account is mandated, you must explicitly grant the privileges (capabilities, docker group membership, or similar) that the sensors need. Without those grants the agent connects but sensors such as process and container monitoring stay degraded.

Question 2Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which component does an Instana host agent contact to receive its configuration and to send collected metrics?

  1. The Instana backend (tenant unit) over HTTPS, using the agent key and endpoint supplied at installation. Correct answer.
  2. A Kafka broker that the customer must provision in advance.
  3. The Instana agent's own embedded database, which is later scraped by the UI.
  4. A local etcd cluster installed alongside the agent.

Explanation

The host agent is configured with an agent key and the backend endpoint for the tenant unit, and it communicates with that backend over HTTPS. Configuration updates and monitoring data both flow through this channel. No customer-provisioned message broker or local etcd is part of the standard architecture.

Question 3Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is installing the Instana host agent on a Linux server and wants the installation to be non-interactive for automation. Which approach fits the supported installer workflow?

  1. Run the installer interactively once and then copy the resulting binary to other hosts without configuration.
  2. Pre-create the tenant in the UI for each host and rely on auto-discovery of the key.
  3. Edit the agent's binary to embed the key before installation.
  4. Download the agent package and run the installer with the agent key and backend host supplied as command-line parameters or a configuration file so no prompts appear. Correct answer.

Explanation

The Linux installer accepts the agent key, backend endpoint, and related settings as parameters or via a supplied configuration file, which makes unattended rollout straightforward. This is the documented automation path for mass deployment. Editing binaries or skipping configuration on copied hosts is unsupported.

Question 4Installation, Deployment, and Upgrade of Instana Agents and Hosts

What is the primary purpose of the agent key during host agent installation?

  1. It licenses the host operating system for monitoring.
  2. It identifies and authorizes the agent to report to a specific Instana tenant unit. Correct answer.
  3. It sets the retention period for metrics stored on the backend.
  4. It encrypts the agent's local log files at rest.

Explanation

The agent key ties an agent to a particular tenant unit and authorizes its data ingestion. It is supplied at install time and can be rotated later. It does not govern local log encryption, OS licensing, or backend retention policy.

Question 5Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator needs to update the agent key on a large fleet of already-installed Linux hosts without reinstalling the agent. What is the appropriate mechanism?

  1. Change the key in the agent configuration file (for example configuration.yaml) and restart the agent service on each host. Correct answer.
  2. Rotate the key only in the backend; existing agents adopt it without any local change.
  3. Delete the host entries in the UI so the agents re-register with a new key automatically.
  4. Uninstall and reinstall the agent on every host to pick up the new key.

Explanation

The agent key is a configuration value stored in the agent's configuration file, so it can be updated in place and applied with a service restart. Reinstallation is unnecessary for a key change. Backend-side rotation alone does not rewrite the value on each host.

Question 6Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which statement correctly describes the Instana agent's update behavior on a Linux host when automatic updates are enabled?

  1. The agent periodically checks for and applies available agent updates according to its configured update policy. Correct answer.
  2. The agent never updates itself; the backend pushes new binaries to the host.
  3. The agent only updates when an administrator manually downloads a new package each time.
  4. The agent updates only when the host operating system reboots.

Explanation

With automatic updates enabled, the host agent checks for newer agent versions and applies them based on its update configuration. This keeps sensors current without manual package handling on every host. Manual-only or reboot-only behavior misstates how the update mechanism works.

Question 7Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator wants to pin a specific agent version on a production host to avoid unplanned changes. Which configuration most directly achieves this?

  1. Remove the backend endpoint so the agent cannot receive update instructions.
  2. Disable automatic agent updates in the agent configuration so the installed version remains until changed manually. Correct answer.
  3. Set the agent key to a read-only value.
  4. Install the agent under a non-root account.

Explanation

Version pinning is achieved by turning off automatic updates so the agent stays at its installed version until an administrator acts. Removing the endpoint would also stop monitoring, which is not the goal. The agent key and run-as account do not control update behavior.

Question 8Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which Instana deployment model runs the agent as a container on each Kubernetes node to monitor node and pod activity?

  1. A CronJob that runs the agent every minute.
  2. A single Deployment with one replica in the default namespace.
  3. A StatefulSet with a fixed replica count of three.
  4. A DaemonSet that schedules one agent pod per node. Correct answer.

Explanation

The Kubernetes agent is deployed as a DaemonSet so exactly one agent pod runs on every node, giving node-level and pod-level visibility. A single-replica Deployment would leave most nodes unmonitored. StatefulSets and CronJobs do not match the per-node scheduling requirement.

Question 9Installation, Deployment, and Upgrade of Instana Agents and Hosts

During installation of the Instana agent operator on Kubernetes, which resource typically carries the agent key and endpoint configuration consumed by the operator?

  1. A ConfigMap mounted into the kube-apiserver.
  2. A node label applied to each worker node.
  3. A Kubernetes Secret referenced by the agent custom resource or operator configuration. Correct answer.
  4. An environment variable set only in the administrator's shell.

Explanation

The agent key and backend endpoint are supplied to the operator through a Kubernetes Secret that the agent custom resource references. This keeps credentials out of plain manifests and shell history. Shell-only variables, apiserver ConfigMaps, and node labels are not the configuration channel.

Question 10Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is preparing to install the Instana host agent on a Windows server. Which prerequisite is most relevant to a successful installation?

  1. Removing PowerShell from the host to avoid conflicts.
  2. Confirming the supported Windows version and that the installer is run with administrative privileges. Correct answer.
  3. Disabling all Windows services before installation.
  4. Converting the host to a container host first.

Explanation

Windows agent installation requires a supported OS version and administrative rights so the service can be registered and sensors can collect data. Disabling services, removing PowerShell, or containerizing the host are not prerequisites and would harm the environment.

Question 11Installation, Deployment, and Upgrade of Instana Agents and Hosts

After installing the Instana agent on a host, an administrator sees the host in the UI but no process metrics. Which troubleshooting step is most appropriate first?

  1. Check the agent's local log for sensor errors and confirm the process sensor is enabled and has the privileges it needs. Correct answer.
  2. Disable the agent key and rely on auto-registration.
  3. Delete the tenant and recreate it.
  4. Immediately reinstall the operating system on the host.

Explanation

When a host registers but a specific sensor reports nothing, the agent log is the first place to look for sensor startup errors or permission problems. Confirming the sensor is enabled and privileged narrows the cause quickly. Destructive actions like OS reinstall or tenant recreation are disproportionate and unlikely to help.

Question 12Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which file or directory is the standard location for the Instana host agent's configuration on Linux?

  1. Under the user's home directory in ~/.instana.
  2. Under /var/log/instana only.
  3. Under /opt/instana/agent/etc, where configuration.yaml and related files reside. Correct answer.
  4. Under /etc/systemd/system only.

Explanation

The Linux host agent keeps its configuration under its installation tree, typically /opt/instana/agent/etc, including configuration.yaml. Systemd unit files, home directories, and log paths are not where agent configuration lives. Knowing this path is essential for editing keys, endpoints, and sensor settings.

Question 13Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator wants to deploy the Instana agent to hosts in a network segment with no direct internet access but reachable access to the Instana backend. What should be verified?

  1. That ICMP is enabled in both directions.
  2. That outbound HTTPS connectivity from the host to the tenant unit endpoint is permitted through the firewall. Correct answer.
  3. That the host can reach a public package repository at install time only.
  4. That inbound port 443 from the internet to the host is open.

Explanation

The agent initiates outbound HTTPS connections to the tenant unit endpoint, so firewall rules must allow that egress path. Inbound internet access to the host is not required. Package repository access matters only for installation, and ICMP is not a dependency.

Question 14Installation, Deployment, and Upgrade of Instana Agents and Hosts

A team needs to monitor a mainframe (z/OS) environment with Instana. Which statement best reflects the deployment approach?

  1. Mainframes cannot be monitored and require a separate third-party tool.
  2. The standard Linux host agent package is installed unchanged on z/OS.
  3. A dedicated mainframe agent component is installed on the z/OS system and reports to the Instana backend. Correct answer.
  4. Only containerized workloads on z/OS can be monitored.

Explanation

Instana provides a mainframe monitoring component designed for z/OS that reports into the same backend. The ordinary Linux host agent package is not installed unchanged on z/OS. Mainframe monitoring is supported, and it is not limited to containerized workloads.

Question 15Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is deploying the Instana agent into an OpenShift cluster. Which consideration is most specific to OpenShift compared with a plain Kubernetes cluster?

  1. Granting the agent the SecurityContextConstraints permissions it needs to run and collect node-level data. Correct answer.
  2. Disabling the Kubernetes API server.
  3. Converting the cluster to use only static pods.
  4. Removing all namespaces except default.

Explanation

OpenShift enforces SecurityContextConstraints, so the agent's service account must be granted permissions that allow the required host access. Plain Kubernetes lacks this specific admission control layer. Disabling the API server or collapsing namespaces would break the cluster.

Question 16Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which statement about the Instana agent's host tagging capability is accurate?

  1. Tags can only be applied from the backend after the host is deleted.
  2. Tags are limited to predefined values that cannot be customized.
  3. Tags require reinstalling the agent each time a value changes.
  4. Tags can be defined in the agent configuration so that the host and its entities carry custom metadata for filtering and grouping. Correct answer.

Explanation

The agent configuration supports custom tags that propagate to the host and associated entities, enabling filtering and grouping in the UI. Custom tags are not restricted to fixed values, and changing them does not require reinstallation. Tags are applied at monitoring time, not after host deletion.

Question 17Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator needs the Instana agent to monitor a Docker environment on a host. What does the agent typically require to collect container metrics?

  1. Rootless Docker to be disabled permanently.
  2. The Docker daemon to be switched to Swarm mode.
  3. Access to the Docker daemon socket so it can query container metadata and statistics. Correct answer.
  4. A separate Docker plugin installed inside every container.

Explanation

Container monitoring relies on the agent's ability to query the Docker daemon through its socket to obtain container metadata and resource statistics. No per-container plugin is required. Swarm mode and disabling rootless Docker are not prerequisites for basic Docker monitoring.

Question 18Installation, Deployment, and Upgrade of Instana Agents and Hosts

What is the effect of configuring the Instana agent with a proxy for backend communication?

  1. The proxy replaces the need for an agent key.
  2. Agent traffic to the Instana backend is routed through the specified proxy, which must allow HTTPS to the tenant unit endpoint. Correct answer.
  3. The agent stops encrypting its traffic.
  4. All host application traffic is transparently redirected through the proxy.

Explanation

Proxy settings direct the agent's own backend-bound traffic through the proxy, which must permit HTTPS to the tenant unit. The agent does not reroute unrelated application traffic, and encryption and the agent key remain in effect. This is a common requirement in restricted networks.

Question 19Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is planning an upgrade of the Instana host agent across a fleet. Which practice best reduces risk?

  1. Upgrade all production hosts simultaneously during peak traffic.
  2. Skip agent updates indefinitely because updates are never needed.
  3. Upgrade a small pilot group first, validate monitoring, then roll out to the remaining hosts. Correct answer.
  4. Upgrade only the backend and never the agents.

Explanation

A staged rollout starting with a pilot group lets you validate sensor behavior and connectivity before touching the whole fleet. Simultaneous upgrades during peak load increase blast radius. Agents and backend versions must remain compatible, so agents cannot simply be frozen forever.

Question 20Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which outcome indicates that an Instana host agent has successfully registered with the backend?

  1. The host appears in the Instana infrastructure view with a recent agent heartbeat. Correct answer.
  2. The agent log shows only startup lines and no further entries.
  3. The backend rejects the agent key with an authorization error.
  4. The host's operating system reports a new kernel version.

Explanation

Successful registration is visible as the host appearing in the infrastructure view with a current heartbeat from the agent. An authorization error indicates failure, not success. Kernel version changes and truncated logs are not registration signals.

Question 21Installation, Deployment, and Upgrade of Instana Agents and Hosts

A security team requires that the Instana agent not run as root on Kubernetes nodes. Which approach is most aligned with supported deployment?

  1. Run the agent as a root container but label it non-root.
  2. Remove the DaemonSet and monitor only the control plane.
  3. Configure the agent DaemonSet with the specific security context and host access it needs, validating that required sensors still function. Correct answer.
  4. Disable all host-level sensors and rely on application-only tracing.

Explanation

Running the Kubernetes agent with reduced privileges requires a deliberate security context that still grants the host access sensors need, followed by validation that monitoring works. Mislabeling a root container does not satisfy the requirement. Dropping the DaemonSet or all host sensors sacrifices the visibility the agent is meant to provide.

Question 22Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which statement about installing the Instana agent on an IBM AIX host is accurate?

  1. AIX hosts cannot be monitored by Instana.
  2. AIX monitoring requires the Kubernetes operator.
  3. The Linux RPM package installs unchanged on AIX.
  4. A platform-specific agent package for AIX is installed and configured to report to the backend. Correct answer.

Explanation

Instana provides platform-specific agent packages for supported UNIX platforms such as AIX, configured to report to the backend. A Linux RPM is not interchangeable with an AIX package. AIX is supported, and the Kubernetes operator is not the installation path for a standalone AIX host.

Question 23Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator notices that one host in a large fleet stopped sending data while others continue normally. Which first step best isolates whether the issue is host-local or backend-wide?

  1. Rebuild the Instana backend.
  2. Check the affected host's agent service status and log, and confirm whether other hosts in the same tenant are still reporting. Correct answer.
  3. Immediately rotate the agent key for the entire fleet.
  4. Disable monitoring on all other hosts for comparison.

Explanation

Comparing the affected host's service status and logs against the health of peers distinguishes a local agent failure from a broader backend or network problem. Rotating the key fleet-wide or rebuilding the backend is premature. Disabling other hosts destroys the comparison baseline.

Question 24Installation, Deployment, and Upgrade of Instana Agents and Hosts

Which statement best describes the relationship between the Instana host agent and its sensors?

  1. Sensors are optional backend plugins that the agent never loads.
  2. Each sensor runs as an independent operating system service outside the agent.
  3. The host agent hosts and manages sensors that each collect a specific type of telemetry, and sensors can be enabled or disabled through configuration. Correct answer.
  4. Sensors replace the agent entirely once installed.

Explanation

Sensors run within the agent process and each targets a specific technology, with enablement controlled through agent configuration. They are not separate OS services, nor are they backend-only plugins. The agent remains the runtime that hosts them.

Question 25Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator must ensure the Instana agent can monitor a Java application's JVM metrics on a host. Which configuration is most relevant?

  1. Enabling the relevant JVM or Java sensor in the agent configuration and confirming the agent can access the JVM's management interface. Correct answer.
  2. Switching the host to a container-only deployment.
  3. Disabling the host agent and relying on log parsing only.
  4. Installing a second agent inside the JVM process.

Explanation

JVM monitoring depends on the agent's Java-related sensor being enabled and able to reach the JVM's management interface, such as JMX. A second in-process agent is not required. Log-only monitoring or container-only deployment would not deliver the JVM metrics being requested.

Question 26Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is deploying the Instana host agent on a Linux server that must reach the Instana backend through an HTTP proxy. Which configuration element is designed to carry the proxy settings for the agent's outbound communication?

  1. Proxy settings configured exclusively in the operating system's kernel routing table
  2. Proxy settings embedded in the agent key string supplied by the Instana backend
  3. Proxy settings defined in the agent's configuration file under the agent communication section Correct answer.
  4. Proxy settings that must be exported only as shell environment variables before the installer runs

Explanation

The Instana host agent reads its outbound connectivity settings, including proxy host, port, and credentials, from its configuration file, so administrators persist proxy values there rather than relying on transient shell state. Environment variables at install time do not survive service restarts in a predictable way, and the agent key carries identity, not network routing.

Question 27Installation, Deployment, and Upgrade of Instana Agents and Hosts

After installing the Instana host agent on a Linux server, an administrator confirms the service is running but the host never appears in the Instana UI. Which check most directly validates that the agent can reach and authenticate with the backend?

  1. Verify that the host's CPU count meets the recommended sizing for sensor load
  2. Confirm the host's disk has sufficient free space for the agent's sensor cache
  3. Check that the hostname resolves consistently in the local hosts file
  4. Review the agent log for successful backend connection and agent-key acceptance messages Correct answer.

Explanation

Registration with the backend requires a successful outbound connection plus acceptance of the agent key, and both outcomes are recorded in the agent log. Disk space, CPU sizing, and hostname resolution affect agent health but do not by themselves prove backend authentication succeeded.

Question 28Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator wants to install the Instana host agent on a Linux host using a scripted, repeatable method that avoids interactive prompts. Which approach best supports unattended installation?

  1. Install the agent interactively once and then clone the host's disk image for other servers
  2. Rely on the agent to prompt for the key on first service start
  3. Run the installation script with parameters that supply the agent key and endpoint non-interactively Correct answer.
  4. Manually edit the packaged configuration template after copying it to the host

Explanation

The Linux installation script accepts command-line parameters, including the agent key and backend endpoint, so it can run without prompts in automation pipelines. Editing templates or cloning images creates drift and does not scale as a supported deployment method.

Question 29Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is preparing to install the Instana host agent on a Linux host that will monitor many containerized workloads. Which prerequisite most directly affects the agent's ability to collect container-level metrics?

  1. An NTP client configured to sync with the Instana backend's time source
  2. A dedicated GPU on the host for sensor acceleration
  3. Access to the container runtime's socket or API so the agent can query container metadata Correct answer.
  4. A second network interface reserved for backend traffic

Explanation

Container visibility depends on the agent being able to query the container runtime, typically through its socket or API, to map processes and containers. GPU hardware, extra interfaces, and time synchronization do not enable container metadata collection.

Question 30Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator must upgrade the Instana host agent on a large Linux fleet with minimal disruption. Which practice best limits the blast radius of the upgrade?

  1. Disable all sensors permanently before upgrading to avoid version conflicts
  2. Upgrade every host simultaneously during a maintenance window to finish quickly
  3. Upgrade a small canary group first, validate host and sensor health, then proceed in batches Correct answer.
  4. Skip validation and rely on automatic rollback to fix any failed hosts

Explanation

Staged rollouts let administrators confirm that the new agent version registers, reports host metrics, and runs sensors correctly before widening the change. Simultaneous upgrades maximize impact, and disabling sensors removes the very signals needed to judge success.

Question 31Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator installs the Instana host agent on a Linux server and later moves that server to a different network zone. The host still reports, but it appears as a new entity in the UI. Which factor most likely explains the duplicate host identity?

  1. The host identity is derived from attributes such as hostname or machine ID that changed during the move Correct answer.
  2. The backend created a new entity because the agent version changed
  3. The agent key was rotated automatically by the backend during the move
  4. The agent's sensor set was refreshed and created a second entity by design

Explanation

Instana derives host identity from stable attributes, so changing the hostname or machine identity during a move can cause the backend to treat the host as a new entity. Agent key rotation, sensor refresh, and version changes do not by themselves create duplicate host entities.

Question 32Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator needs the Instana agent on Kubernetes to be deployed and managed declaratively, with the agent key stored as a Kubernetes Secret. Which deployment approach aligns with this requirement?

  1. Use a DaemonSet manifest that embeds the key as a plain environment variable
  2. Run the host agent installer directly on each node's operating system
  3. Install the Instana agent operator and reference the Secret from the custom resource Correct answer.
  4. Deploy the agent as a standalone Deployment with the key hardcoded in the pod spec

Explanation

The Instana agent operator reconciles a custom resource and can consume the agent key from a Kubernetes Secret, keeping credentials out of manifests. Hardcoding keys in pod specs or environment variables exposes credentials, and manual node installers bypass declarative management.

Question 33Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is planning to monitor an IBM i host with Instana. Which statement best reflects the deployment approach for that platform?

  1. A platform-specific agent component is installed on the IBM i system and reports to the Instana backend Correct answer.
  2. IBM i monitoring requires the Kubernetes operator to run on the same partition
  3. Only the backend-side remote poller can collect IBM i metrics without any agent
  4. The standard Linux host agent binary is copied to IBM i and runs unchanged

Explanation

IBM i is monitored through a platform-specific agent component installed on the system, which then communicates with the Instana backend. The Linux host agent binary is not portable to IBM i, and the Kubernetes operator is irrelevant to that platform.

Question 34Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator wants to install the Instana host agent on a Linux host that has no outbound internet access but can reach an internal package mirror containing the agent packages. Which configuration element is essential for the installation to succeed?

  1. Disabling TLS verification for all agent traffic to the backend
  2. Removing the agent key so the installer skips backend validation
  3. Setting the agent to run in a read-only filesystem mode
  4. Pointing the agent's package source or download location at the internal mirror Correct answer.

Explanation

When the host cannot reach the public package source, the installer must be directed to an internal mirror that hosts the agent packages. Disabling TLS or removing the key weakens security and does not solve package availability.

Question 35Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is troubleshooting a Linux host where the Instana agent service starts but exits shortly afterward. Reviewing the agent log shows a configuration parse error. Which action most directly addresses the root cause?

  1. Rotate the agent key in the backend and restart the service
  2. Increase the host's memory allocation and restart the service
  3. Reinstall the operating system to clear corrupted system libraries
  4. Correct the malformed syntax in the agent configuration file and restart the service Correct answer.

Explanation

A configuration parse error means the agent cannot load its settings, so fixing the syntax in the configuration file is the direct remedy. Memory, OS libraries, and key rotation do not resolve malformed configuration syntax.

Question 36Installation, Deployment, and Upgrade of Instana Agents and Hosts

An administrator is designing a rollout where the Instana host agent must be installed on Windows servers across several data centers. Which consideration is most specific to automating that Windows deployment at scale?

  1. Assuming the agent requires no configuration because Windows hosts self-register anonymously
  2. Distributing the installer and supplying the agent key through a supported silent installation mechanism Correct answer.
  3. Relying on the Linux installation script with a compatibility flag for Windows
  4. Using the Kubernetes operator to schedule the installer on each Windows node

Explanation

Windows hosts are deployed by distributing the platform installer and running it silently with the agent key supplied, which is what makes large-scale automation feasible. The Linux script does not target Windows, hosts do not self-register without a key, and the Kubernetes operator does not install Windows host agents.

Question 37Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator needs a host agent to report to a specific Instana backend instead of the default endpoint. Which agent configuration file controls the backend connection settings on a Linux host?

  1. com.instana.agent.main.sender.File_backend.cfg Correct answer.
  2. instana-agent.properties
  3. agent.conf
  4. configuration.yaml

Explanation

On a standard Linux host agent the backend endpoints are defined in the sender configuration file com.instana.agent.main.sender.File_backend.cfg, which lists the host, port, and protocol used to reach the Instana backend. Editing that file and restarting the agent redirects telemetry to the intended endpoint.

Question 38Agent Configuration, Dynamic Focus Queries, and Sensor Management

A Dynamic Focus Query is being written to select only production Kubernetes namespaces. Which query syntax correctly filters on the namespace tag?

  1. tag(kubernetes.namespace.name, production)
  2. entity.kubernetes.namespace.name:production Correct answer.
  3. kubernetes.namespace.name == production
  4. namespace = 'production'

Explanation

Dynamic Focus Queries use the syntax tag:value, and Kubernetes namespace tags are referenced by their canonical tag name such as entity.kubernetes.namespace.name. The colon separates the tag from the value and the query matches entities carrying that tag value.

Question 39Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator wants Dynamic Focus Query expressions to combine two conditions so that both must be true. Which operator is used?

  1. AND Correct answer.
  2. NOT
  3. OR
  4. XOR

Explanation

Dynamic Focus Queries support the boolean operators AND and OR. Using AND between two tag conditions requires both conditions to match for an entity to be selected.

Question 40Agent Configuration, Dynamic Focus Queries, and Sensor Management

Which Instana capability automatically discovers and instruments supported technologies running on a monitored host without manual agent installation per process?

  1. Synthetic monitoring
  2. Log ingestion pipelines
  3. Auto-tracing sensors Correct answer.
  4. Manual SDK injection

Explanation

Instana auto-tracing sensors detect supported runtimes and frameworks on a monitored host and instrument them automatically. This removes the need to install a separate agent for each process or technology.

Question 41Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator needs to prevent a specific sensor from being activated on all agents. Where is this controlled in the Instana UI?

  1. The application dashboard settings
  2. The alert channel configuration
  3. The sensor management settings under agent configuration Correct answer.
  4. Agent configuration profiles only

Explanation

Sensor enablement is governed centrally through the sensor management settings in agent configuration, where sensors can be enabled or disabled across the environment. This central control overrides local activation for the affected sensors.

Question 42Agent Configuration, Dynamic Focus Queries, and Sensor Management

A Dynamic Focus Query must select entities whose tag value exactly equals a string containing spaces. How should the value be written?

  1. Enclosed in single quotes Correct answer.
  2. Enclosed in double quotes
  3. With a backslash before each space
  4. With no special handling

Explanation

In Dynamic Focus Query syntax, a value containing spaces must be enclosed in single quotes so the parser treats the whole string as one value. Unquoted values are terminated at the first space.

Question 43Agent Configuration, Dynamic Focus Queries, and Sensor Management

Which file on a Linux host agent is used to set the agent's own log level for troubleshooting?

  1. com.instana.agent.main.config.Agent.cfg Correct answer.
  2. com.instana.agent.main.root.cfg
  3. com.instana.agent.main.sender.File_backend.cfg
  4. instana-agent.log

Explanation

The agent's primary configuration file com.instana.agent.main.config.Agent.cfg contains settings such as the agent log level. Adjusting it and restarting the agent increases diagnostic verbosity.

Question 44Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator wants a Dynamic Focus Query to exclude a set of test hosts from a dashboard scope. Which approach achieves this?

  1. Use the AND operator with the tag condition
  2. Use the NOT operator with the tag condition Correct answer.
  3. Add the tag to the include list twice
  4. Prefix each tag with a minus sign

Explanation

Dynamic Focus Queries support the NOT operator to negate a condition, so NOT followed by a tag condition excludes matching entities. This is the documented way to build exclusion scopes.

Question 45Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator configures a Dynamic Focus Query with a tag name that contains a dot, such as entity.zone. What must be done to match on it?

  1. Wrap the tag name in single quotes
  2. Replace the dot with an underscore
  3. Drop the prefix before the dot
  4. Reference the full tag name exactly as defined Correct answer.

Explanation

Dynamic Focus Queries match on the full canonical tag name, dots included, so entity.zone must be referenced exactly as defined. Altering the tag name causes the condition to match nothing.

Question 46Agent Configuration, Dynamic Focus Queries, and Sensor Management

A host agent is installed but shows as not connected in the Instana UI. Which configuration item should be verified first?

  1. The alert channel recipient list
  2. The application dashboard filter
  3. The synthetic test schedule
  4. The backend host and port in the sender configuration file Correct answer.

Explanation

Connectivity depends on the agent reaching the backend endpoint declared in the sender configuration file. Verifying the host, port, and protocol there is the first step when an agent fails to connect.

Question 47Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator deploys the agent with a key that is later rotated in the Instana backend. What must be updated on the host agent?

  1. The agent log level
  2. The host's DNS resolver
  3. The agent key in the agent configuration Correct answer.
  4. The sensor list in the UI

Explanation

The agent authenticates to the backend using the agent key stored in its configuration. When the key is rotated, the local configuration must be updated with the new key and the agent restarted.

Question 48Agent Configuration, Dynamic Focus Queries, and Sensor Management

A team wants to scope a dashboard to entities tagged with a custom tag created in Instana. Which Dynamic Focus Query condition selects them?

  1. customTag(value)
  2. entity(type, custom.tag)
  3. entity.custom.tag:value Correct answer.
  4. tag:customTag=value

Explanation

Custom tags are referenced in Dynamic Focus Queries using the entity.custom.tag tag name followed by a colon and the value. This selects entities carrying that custom tag value.

Question 49Agent Configuration, Dynamic Focus Queries, and Sensor Management

An administrator disables a sensor centrally in sensor management. What is the effect on agents that already detected the technology?

  1. Only new agents are affected
  2. The technology is uninstalled from the host
  3. The sensor remains active locally until each agent is restarted
  4. The sensor stops being activated for the affected technology across the environment Correct answer.

Explanation

Central sensor management controls activation across the environment, so disabling a sensor stops it from being activated for that technology. Local detection does not override the central setting.

Question 50Agent Configuration, Dynamic Focus Queries, and Sensor Management

A Dynamic Focus Query uses OR between many conditions and returns more entities than expected. What is the most likely cause?

  1. OR only matches the first condition
  2. OR requires all conditions to match
  3. OR widens the match set so any single matching condition qualifies Correct answer.
  4. OR is an invalid operator

Explanation

OR is a union operator, so an entity qualifies if any one condition is true, widening the result set. Replacing OR with AND where all conditions must hold narrows the scope.