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 1Dynatrace Platform Fundamentals
What is the primary function of OneAgent in Dynatrace?
- It stores all observability data and provides long-term retention in Grail.
- It runs cloud-based synthetic browser monitors from multiple global locations.
- It acts as a proxy that forwards third-party API calls to the Dynatrace platform.
- It discovers processes and collects metrics, traces, and logs automatically. Correct answer.
Explanation
OneAgent is deployed on monitored hosts and automatically discovers running processes, then collects metrics, traces, and logs from them. It does not itself run synthetic monitors, store data long term, or act as an API proxy; those are separate platform capabilities.
Question 2Dynatrace Platform Fundamentals
What does Smartscape represent in Dynatrace?
- A query language used to search observability data stored in Grail
- A prebuilt dashboard template that visualizes infrastructure health across hosts
- A rule set that decides which detected problems trigger alert notifications
- A real-time topology model of hosts, processes, services, and dependencies Correct answer.
Explanation
Smartscape continuously maps entities such as hosts, processes, services, and applications together with their dependencies. This topology enables impact analysis and helps Davis determine how a fault propagates.
Question 3Dynatrace Platform Fundamentals
What is a PurePath?
- A retention policy that controls how long log data is stored
- A deployment event recorded when a new build is released
- A distributed trace showing timing and call paths across services Correct answer.
- A scripted synthetic check that runs on a fixed schedule from global locations
Explanation
A PurePath is an end-to-end distributed trace captured by OneAgent that shows the timing and call sequence across services and tiers. It is used to locate slow methods and understand request flow.
Question 4Dynatrace Platform Fundamentals
Which capability is central to Davis AI in Dynatrace?
- Generating synthetic user traffic to test application availability
- Managing user permissions and access boundaries for the platform
- Automatic root-cause analysis of detected problems using causal AI Correct answer.
- Storing metrics and logs in long-term Grail buckets for later analysis
Explanation
Davis analyzes anomalies across the topology and correlates them causally to identify the root cause of a problem. It raises problems rather than merely firing individual metric alerts.
Question 5Dynatrace Platform Fundamentals
Real User Monitoring in Dynatrace captures which kind of data?
- The ingestion rate of third-party log sources into Grail
- The performance of real user sessions in browsers and mobile apps Correct answer.
- The memory consumption of server-side processes on monitored hosts
- The results of scheduled synthetic transactions from global locations
Explanation
Real User Monitoring records actual user sessions in web browsers and mobile apps, including load times, user actions, and errors. This complements server-side tracing with the end-user perspective.
Question 6Dynatrace Platform Fundamentals
What is the purpose of a management zone?
- Define how long metric data is retained in Grail storage buckets
- Partition the environment so teams see only relevant entities Correct answer.
- Assign CPU and memory limits to monitored host processes
- Encrypt API tokens used by integrations and automation
Explanation
Management zones filter the environment so that a team can focus on the hosts, services, and applications it owns. Access and alerting can then be scoped to that subset of entities.
Question 7Dynatrace Platform Fundamentals
What does the abbreviation DQL stand for in Dynatrace?
- Data Quality Ledger
- Dynamic Query Layer
- Dynatrace Query Language Correct answer.
- Distributed Queue Link
Explanation
DQL is the Dynatrace Query Language used to query records stored in Grail, such as logs, events, metrics, and traces. It is used in notebooks, dashboards, and API queries.
Question 8Dynatrace Platform Fundamentals
What role does an ActiveGate play in a Dynatrace deployment?
- An agent installed on hosts that discovers processes and collects data
- A component that runs Davis root-cause analysis on problems
- A secure gateway connecting Dynatrace to monitored environments Correct answer.
- A cloud service that stores logs, metrics, and traces in Grail
Explanation
ActiveGate provides a secure outbound connection from monitored environments to the Dynatrace cluster. It also enables capabilities such as private synthetic monitoring and routing of API traffic.
Question 9Dynatrace Platform Fundamentals
Which approach automatically applies a tag to many related entities at once?
- Add the tag inside a maintenance window configuration
- Attach the tag to an SLO definition and let it propagate
- Manually edit each entity and add the tag one by one
- Create a tagging rule that matches entity properties Correct answer.
Explanation
Tagging rules evaluate entity properties such as name, host group, or process metadata and apply tags automatically. This scales consistently across many entities and keeps tags current as the environment changes.
Question 10Dynatrace Platform Fundamentals
What does an alerting profile control?
- Which OneAgent versions are automatically deployed to hosts
- How long logs and metrics are retained in Grail buckets
- Which API token scopes are available to automation workflows and scripts
- Which problems trigger alerts and where notifications are sent Correct answer.
Explanation
An alerting profile defines filters for the problems that should generate alerts and links them to notification integrations. It lets different teams receive only the alerts relevant to their scope.
Question 11Dynatrace Platform Fundamentals
What happens to problem detection during a maintenance window?
- Stored data for the affected entities is deleted after the window
- Problems are still detected, but notifications are suppressed Correct answer.
- Davis root-cause analysis is disabled for the whole environment
- OneAgent stops collecting all data from the affected hosts
Explanation
Maintenance windows suppress alert notifications for the entities they cover while monitoring continues. This prevents planned work from generating disruptive alerts without losing observability data.
Question 12Dynatrace Platform Fundamentals
What is Grail in the Dynatrace platform?
- A dashboard type used to display infrastructure health and capacity metrics
- A deployment tool that pushes OneAgent updates to hosts
- A data lakehouse storing logs, events, metrics, and traces Correct answer.
- A synthetic monitoring engine that runs browser tests
Explanation
Grail is the platform data store that holds multiple signal types, including logs, events, metrics, and traces, in buckets. Its contents are queried with DQL and governed by bucket retention settings.
Question 13Dynatrace Platform Fundamentals
What does a Dynatrace SLO define?
- A fixed alert threshold that never changes over the evaluation period
- A retention setting for storing logs in a bucket
- A user permission set that controls dashboard access
- A target success rate over a timeframe from a metric expression Correct answer.
Explanation
A service-level objective states a target success rate, such as 99.9 percent, evaluated over a defined timeframe from a metric expression. It expresses reliability goals in business terms rather than raw thresholds.
Question 14Dynatrace Platform Fundamentals
How does Dynatrace typically monitor a Kubernetes cluster?
- An agentless SSH connection polls the Kubernetes API for status every minute
- A log-only integration that forwards container stdout to Grail
- A synthetic monitor that runs kubectl commands on a schedule
- The Dynatrace Operator in the cluster collects metrics, events, and traces Correct answer.
Explanation
The Dynatrace Operator deploys and manages OneAgent and ActiveGate components inside the cluster. It also gathers Kubernetes metrics and events so workloads, nodes, and namespaces are visible in context.
Question 15Dynatrace Platform Fundamentals
Log Monitoring in Grail correlates ingested logs with which other data?
- Traces and entities through trace IDs and context Correct answer.
- IAM policies through access boundary identifiers
- Billing records through cost allocation tags
- Synthetic scripts through browser session cookies
Explanation
Log records can carry trace and span identifiers plus entity context, letting you pivot between logs, traces, and the affected service. This correlation shortens investigation time during incidents.
Question 16Dynatrace Platform Fundamentals
What are Workflows used for on the Dynatrace platform?
- Create and share dashboards for infrastructure health
- Define how long observability data is retained in Grail buckets
- Replace OneAgent with a cloud-based collection service
- Automate remediation and notifications by chaining actions Correct answer.
Explanation
Workflows run on the AutomationEngine and chain actions such as notifications, ticket creation, and remediation scripts in response to events or schedules. They turn detection into an automated response.
Question 17Dynatrace Platform Fundamentals
Which measure protects sensitive user data captured by Real User Monitoring?
- Disable Grail storage for all web applications
- Use only synthetic monitors instead of real user monitoring
- Delete the application from Dynatrace and recreate it
- Configure data privacy masking and blocking rules Correct answer.
Explanation
Data privacy settings let you mask or block captured user actions, input values, and personal data before storage. This supports compliance while retaining performance insight.
Question 18Dynatrace Platform Fundamentals
How do API token scopes affect a Dynatrace integration?
- Tokens have unlimited access once they are created by an administrator
- Scopes limit what an API token can do, such as read metrics Correct answer.
- Tokens encrypt data at rest in Grail buckets
- Tokens replace IAM policies for all platform users
Explanation
Each API token is granted specific scopes that determine which API operations it may perform. Applying least privilege keeps automation integrations from exceeding their intended access.
Question 19Dynatrace Platform Fundamentals
When does Davis raise a problem?
- Any metric changes by a small amount during a single measurement interval
- Davis detects an anomaly that impacts a service Correct answer.
- A OneAgent is installed on a host for the first time
- An API token is created for an automation integration
Explanation
Davis correlates anomalies across the topology and raises a problem when the anomaly has a causal impact on a service. Isolated metric fluctuations that do not affect a service do not become problems.
Question 20Dynatrace Platform Fundamentals
How do dashboards and notebooks differ on the Dynatrace platform?
- Notebooks are only for alerting; dashboards only for DQL queries
- Both are identical and differ only in their display color theme
- Dashboards are for shared views; notebooks for exploratory DQL analysis Correct answer.
- Dashboards store raw logs for retention; notebooks only contain alert definitions
Explanation
Dashboards present curated visualizations intended for a broad audience and at-a-glance monitoring. Notebooks combine DQL queries with narrative and results, making them suited to investigation and analysis.
Question 21Dynatrace Platform Fundamentals
How does retention work for Grail buckets?
- Retention is configured per OneAgent on each monitored host
- Each bucket has its own retention period Correct answer.
- Retention can only be changed by Dynatrace Support
- All buckets share one fixed retention period of ten days
Explanation
Buckets are configured with individual retention periods so that different signal types can be kept for different durations. Queries can span buckets when the user has the required permissions.
Question 22Dynatrace Platform Fundamentals
How do IAM policies and boundaries work together?
- Boundaries replace policies for all automation use cases
- Policies and boundaries are identical and always used together
- Boundaries grant permissions; policies restrict which resources are visible
- Policies grant permissions; boundaries limit the resources they apply to Correct answer.
Explanation
A policy defines the allowed actions, such as viewing logs or editing settings, while a boundary scopes those permissions to a set of resources. Combining both enforces least privilege across large environments.
Question 23Dynatrace Platform Fundamentals
How can OpenTelemetry data be brought into Dynatrace?
- Only by exporting telemetry to a third-party system first
- Only through a proprietary agent that does not support OpenTelemetry
- Through an OTLP endpoint provided by Dynatrace, such as ActiveGate Correct answer.
- Through a database connector that reads telemetry from tables
Explanation
Dynatrace exposes an OTLP ingest endpoint, which can be reached directly or through an ActiveGate in private environments. This allows OpenTelemetry-instrumented services to send traces, metrics, and logs into the platform.
Question 24Dynatrace Platform Fundamentals
How are business events captured and used in Dynatrace?
- Only log files that are parsed with a business-event rule
- Only synthetic browser monitors that replay business transactions
- Ingest APIs, SDKs, and OneAgent, then query them with DQL Correct answer.
- Only host metrics collected by ActiveGate
Explanation
Business events can be sent through ingest APIs and SDKs or captured by OneAgent instrumentation. They are stored in Grail and queried with DQL to support business analytics alongside technical data.
Question 25Dynatrace Platform Fundamentals
What is the purpose of Site Reliability Guardian?
- Replace OneAgent for collecting host metrics
- Validate SLOs during releases and gate deployments Correct answer.
- Store logs and metrics in long-term Grail buckets
- Create dashboards that visualize infrastructure capacity
Explanation
Site Reliability Guardian evaluates objectives such as SLOs and performance criteria during a release pipeline. It can automatically approve or block a deployment based on whether those objectives are met.
Question 26Dynatrace Platform Fundamentals
A team wants to monitor a fleet of Linux servers for CPU, memory, and disk health but does not need code-level tracing of the applications running on them. Which OneAgent monitoring mode fits this requirement?
- Full-Stack monitoring, which instruments host and application code
- Infrastructure monitoring only Correct answer.
- Application-only monitoring
- Discovery mode, which lists detected processes without monitoring
Explanation
OneAgent supports several monitoring modes. Infrastructure mode collects host-level health metrics without deep instrumentation of processes and services, which matches a host-health-only requirement.
Question 27Dynatrace Platform Fundamentals
What does the Smartscape view represent in a Dynatrace environment?
- A chronological record of every configuration change made
- A billing summary of licensing units consumed per host
- A real-time topology of entities and their dependencies Correct answer.
- A list of all configured alerting profiles, ranked by priority
Explanation
Smartscape maintains a continuously updated model of monitored entities across hosts, processes, services, and applications together with their relationships. This topology is what allows impact and dependency analysis during investigations.
Question 28Dynatrace Platform Fundamentals
What is the primary reason to assign hosts to a host group?
- To apply consistent configuration to related hosts as one unit Correct answer.
- To turn the hosts into synthetic monitoring locations
- To restrict which operating-system users can log on to the host
- To extend the retention period of the host metrics stored in Grail
Explanation
A host group is an organizational construct that lets you treat related hosts as a unit and apply the same monitoring configuration to them. It also makes those hosts easy to identify and filter in analysis.
Question 29Dynatrace Platform Fundamentals
Which synthetic monitor type verifies endpoint availability and response status from multiple locations without rendering a page in a browser?
- Browser clickpath monitor
- Browser single-URL monitor
- Real user monitoring
- HTTP monitor Correct answer.
Explanation
HTTP monitors send requests from configured locations and evaluate the response code and timing; no browser is involved. Browser monitors, by contrast, drive a real browser to render and interact with the page.
Question 30Dynatrace Platform Fundamentals
How does Dynatrace typically determine that a group of observed processes constitutes a service?
- By reading a static inventory file provided by the cloud vendor
- By requiring engineers to declare each service in the deployment pipeline
- By applying service detection rules to observed processes Correct answer.
- By deriving service names only from synthetic monitor results
Explanation
OneAgent observes processes, and service detection rules group those processes into services based on technology and identifying attributes. Administrators can adjust those rules when the default grouping does not match the real architecture.
Question 31Dynatrace Platform Fundamentals
What does a PurePath in Dynatrace represent?
- A single end-to-end transaction trace across the tiers it touched Correct answer.
- The ordered list of configuration steps needed to deploy OneAgent
- The retention timeline applied to a Grail bucket
- The network route taken between two ActiveGates
Explanation
A PurePath captures one transaction as it travels through the tiers it touches, including timing per tier and method-level detail. PurePaths underpin response-time analysis and code-level visibility for services.
Question 32Dynatrace Platform Fundamentals
How is the Real User Monitoring JavaScript agent usually delivered to a monitored web application?
- It is fetched by the browser from an ActiveGate over SSH
- It is packaged inside the OneAgent installer for the host
- It is injected into HTML responses automatically Correct answer.
- It is preinstalled as an extension in each visitor's browser
Explanation
The RUM JavaScript agent is normally inserted into the HTML served to the browser, either automatically by the web server module or by adding a script reference. The browser then executes it and reports user actions back to the environment.
Question 33Dynatrace Platform Fundamentals
What is the purpose of a segment in Dynatrace?
- To schedule automatic OneAgent updates for a host group
- To define which users may open dashboards and notebooks
- To filter Grail data consistently across apps Correct answer.
- To store long-term backups of environment configuration
Explanation
Segments define reusable filter criteria, typically based on entities or attributes, that narrow the data shown across Grail-backed apps. They provide a consistent scoping mechanism rather than per-app filtering.
Question 34Dynatrace Platform Fundamentals
Which mechanism does Dynatrace typically use to collect AWS service metrics without installing OneAgent on every resource?
- A cron job on each EC2 instance that pushes CSV files
- Synthetic HTTP monitors deployed inside every AWS region
- A OneAgent extension installed directly on the AWS hypervisor
- A role-based integration that polls CloudWatch metrics Correct answer.
Explanation
The AWS cloud integration authenticates with a role-based connection and pulls metrics and metadata from CloudWatch and related APIs. This provides visibility into managed services that cannot host an agent.
Question 35Dynatrace Platform Fundamentals
What characterizes Settings 2.0 in Dynatrace?
- Configuration is exposed as schema-defined objects Correct answer.
- It removes the need for API tokens and OAuth clients
- All configuration is stored inside Grail as log records
- It replaces classic dashboards with notebooks entirely
Explanation
Settings 2.0 models configuration as typed, schema-defined objects that can be read and written through the UI and the Settings API. This makes configuration consistent and automatable across environments.
Question 36Dynatrace Platform Fundamentals
What is the role of a Dynatrace extension?
- It defines the retention period applied to log buckets
- It collects data from sources OneAgent cannot observe natively Correct answer.
- It replaces OneAgent on every supported operating system
- It converts problems into maintenance windows automatically
Explanation
Extensions add monitoring coverage for technologies and remote data sources that the standard agent modules do not instrument on their own. They typically run on an ActiveGate or alongside OneAgent and feed metrics, events, or logs into the platform.
Question 37Dynatrace Platform Fundamentals
A service has strongly seasonal traffic patterns. Which capability helps Dynatrace avoid false-positive problems on that service?
- Automatic baselining of the service's normal behavior Correct answer.
- Static thresholds configured manually for each service
- Assigning every alerting profile the highest priority
- Disabling problem detection during business hours
Explanation
Automatic baselining learns what normal looks like for each service over time, including recurring seasonal patterns. Deviations are then judged against that learned baseline instead of a fixed number.
Question 38Dynatrace Platform Fundamentals
Users report slow checkout. A problem shows several services on the same host degrading at the same moment, and the host reports saturated CPU. What is the most likely root cause conclusion?
- Resource contention on the shared host Correct answer.
- A misconfigured alerting profile suppressing alerts
- A change to the log retention policy of a bucket
- A network outage between two ActiveGates
Explanation
When multiple services on one host degrade simultaneously and the host itself is saturated, the shared resource is the common factor. Root cause analysis therefore points to host-level contention rather than to any individual service's code.
Question 39Dynatrace Platform Fundamentals
A newly deployed Java application is monitored, but its requests appear under an unexpected service name. Which concept best explains this?
- An ActiveGate rewrote the service name during the handshake
- A synthetic monitor overrode the detected service name
- Service detection rules merged it into an existing service Correct answer.
- Grail buckets renamed the service during data ingestion
Explanation
Services are formed by applying detection rules to observed processes, so processes that match an existing rule land in that service. Adjusting the detection rules changes how the new application is grouped.
Question 40Dynatrace Platform Fundamentals
An external script must push a custom metric with dimensions to Dynatrace every 60 seconds. Which approach is most appropriate?
- Editing the OneAgent configuration file on every host
- Creating a synthetic browser monitor that calls the script
- Writing a log line to Grail and querying it as a metric
- Sending data points to the Metrics API with a scoped token Correct answer.
Explanation
The Metrics API is designed for ingesting custom metric data points together with their dimensions, and access is authorized with a token carrying the appropriate scope. This supports scheduled pushes from outside the monitored hosts.
Question 41Application Observability
What does a PurePath represent in Dynatrace?
- A trace of one transaction showing its calls and their timings across tiers Correct answer.
- An aggregation of a service's hourly average response time over a timeframe
- A snapshot of the OneAgent configuration for a process group
- A copy of the log files collected from the host that runs the service
Explanation
A PurePath is the end-to-end record of a single transaction: every method invocation, remote call, and database call triggered by that request, each with its own timing. Because it is per-request, it supports code-level and cross-tier diagnosis rather than statistical averaging.
Question 42Application Observability
On what basis does OneAgent detect that a process exposes a service?
- The number of processes running under a single host
- Technology-specific entry points such as web request handlers and message listeners Correct answer.
- The operating system and kernel version of the monitored host
- Rules that an administrator must create before any service can be detected
Explanation
OneAgent instruments technology-specific entry points, for example incoming HTTP requests, background jobs, and message consumers, and each detected entry point becomes a service. Administrators can tune detection with service detection rules, but detection is not dependent on them existing first.
Question 43Application Observability
By default, which condition causes an incoming web request to be counted as failed?
- It carries no request attributes
- It is triggered by a synthetic monitor
- It takes longer than one second to complete
- It returns an HTTP status code in the 5xx range Correct answer.
Explanation
Failure detection rules define what counts as a failed request; by default server-side errors in the 5xx range are treated as failures, while 4xx responses are treated as client errors. Slow requests affect response time metrics instead, and can trigger separate performance anomalies.
Question 44Application Observability
What is required before code-level details such as method timings and exceptions appear for a Java process group?
- A maintenance window must cover the process group
- The process group must be placed in a management zone
- An SLO must be created for the service
- Deep monitoring must be active for the process group Correct answer.
Explanation
Code-level visibility comes from deep monitoring, which instruments methods of the process group. Without it, only host and basic process metrics are available, so backtraces, method hotspots, and detailed exception data are missing.
Question 45Application Observability
What does the service flow show for a selected service?
- The CPU and memory consumed by the host that runs it
- The upstream and downstream services that exchange requests with it Correct answer.
- The log files written by its process group
- The deployment events recorded for its process group
Explanation
The service flow visualizes the request relationships around a service, showing which services call it and which services it calls. Selecting a node moves the focus to that service and lets you walk the dependency chain.
Question 46Application Observability
What is the purpose of a request naming rule?
- To assign hosts to management zones
- To define the alerting profile used by the service
- To set the retention period for stored traces
- To group similar requests under a meaningful name for analysis Correct answer.
Explanation
Incoming requests are matched against naming rules so that requests sharing a structure, such as the same URI pattern, are grouped under one request name. All metrics, hotspots, and failure analysis are then reported per request name rather than per raw URL.
Question 47Application Observability
Where can you see the type and stack trace of an exception thrown while a request was processed?
- In the network zone configuration
- In the deployment status overview
- In the process list of the host
- In the PurePath of the affected requests, with type and stack trace Correct answer.
Explanation
Captured exceptions are attached to the request trace, so opening the PurePath of an affected request reveals the exception class, message, and stack trace at the point where it was thrown. This links the error to the exact code path and timing.
Question 48Application Observability
Which mechanism lets Dynatrace link a request that crosses service and host boundaries into one distributed trace?
- W3C Trace Context headers such as traceparent and tracestate Correct answer.
- HTTP cookies set by the user's browser
- SNMP traps sent to the OneAgent
- Syslog messages forwarded from the host
Explanation
Dynatrace propagates a trace context between tiers using standard W3C Trace Context headers, so the callee's PurePath is joined to the caller's trace. The result is one end-to-end trace with a shared trace ID across all participating services.
Question 49Application Observability
What is a backtrace in Dynatrace?
- A code-level breakdown of the method invocations captured while a request is processed Correct answer.
- The set of failure detection rules that apply to a service
- A summary of the OneAgent versions installed in the environment
- A list of synthetic monitors that execute against a service
Explanation
A backtrace is the method-level view of a captured request, showing the call hierarchy and the time spent in each monitored method. It is available only where deep monitoring instruments the code.
Question 50Application Observability
What does the Method hotspots view display for a service?
- The methods that consume the largest share of execution time, aggregated from captured traces Correct answer.
- The requests with the longest URLs in the selected timeframe
- The services that received the most deployment events
- The hosts that consume the most CPU in the environment
Explanation
Method hotspots aggregate method-level timings across many captured requests and rank methods by the total time they consume. This makes it possible to find expensive code even when no single request looks obviously slow.