A problem opened with the event category of "Slowdown". Assuming Dynatrace is using the default anomaly detection settings, what entity types can be the root cause of this problem? (Select all that apply)
Answer : B, C, E
In Dynatrace, ''Slowdown'' problems are typically triggered by performance degradation detected through anomaly detection on monitored entities.
With default settings, the root cause of slowdown problems is usually identified at:
Services, where response time degradation is detected
Processes, where CPU, memory, or other resource bottlenecks occur
Hosts, where infrastructure-level issues impact performance
Applications are higher-level aggregations and are not typically identified as the root cause entity.
Cloud Providers are not treated as root cause entities in anomaly detection.
Dynatrace's AI (Davis) correlates these entities to pinpoint the most likely root cause in the topology.
===========
Which Dashboard Tiles visualize the status of your entities using Red and Green Hexagons?
Answer : B, C
Dynatrace uses hexagon-style health tiles with green and red indicators to visualize the health status of monitored entities.
These are specifically used in:
Service health tiles -- showing health of services
Application health tiles -- showing overall application health
These tiles provide a quick visual overview of system health using color-coded hexagons.
Other options:
Synthetic monitor health uses different visualization styles
Web applications is not a tile type
Problems shows problem cards, not hexagon visualization
===========
What sort of outage occurs when all Synthetic Locations simultaneously experience 1--5 consecutive failures?
Answer : C
A Global outage is detected when all configured Synthetic locations report failures at the same time within a defined number of consecutive failed executions. This indicates that the issue is not location-specific but instead affects the application or service globally.
Dynatrace Synthetic Monitoring differentiates between:
Local outages, where only a subset of locations fail (indicating regional or network-specific issues)
Global outages, where all locations fail simultaneously, indicating a widespread availability problem
Options such as Public Synthetics and Private Synthetics refer to types of Synthetic locations, not outage classifications.
===========
What type of User Actions exists?
Answer : A, B, C
Dynatrace defines three main types of user actions:
Load Actions -- full page loads
XHR Actions -- background requests (AJAX/fetch)
Custom Actions -- user-defined actions
Click Actions are not a separate action type; clicks are typically captured within other action types such as load or custom actions.
===========
Which steps outline the Business Event Dataflow? (Select all that apply)
Answer : A, B, D
The Business Event Dataflow in Dynatrace follows a structured pipeline that focuses on collecting, handling, and analyzing business events:
Capture -- Business events are ingested into Dynatrace from various sources such as applications, APIs, or external systems
Process -- The captured data is processed, enriched, and stored within the Dynatrace platform (Grail)
Analyze -- Users query and analyze the processed data using tools like dashboards and DQL
Export is not considered a core step in the business event dataflow. While exporting data is possible, it is not part of the primary ingestion-to-analysis pipeline defined in Dynatrace.
===========
Which of the following is the default threshold type used for anomaly detection on Hosts (CPU saturation, memory saturation, disk utilization...)?
Answer : D
Dynatrace uses Automated Multi-Dimensional Baselining as the default anomaly detection method for host metrics such as CPU, memory, and disk utilization.
This approach:
Automatically learns normal behavior patterns over time
Adjusts thresholds dynamically based on historical data
Considers multiple dimensions such as time of day and workload patterns
This allows Dynatrace to detect anomalies more accurately compared to fixed thresholds.
Static thresholds are manually defined and not the default.
Other options are unrelated to anomaly detection mechanisms.
===========
Which Dynatrace app would be best suited to retain the results of a DQL query for later analysis?
Answer : B
Notebooks are the best tool in Dynatrace for retaining and reusing DQL query results.
They allow users to:
Store DQL queries
Keep query results for later analysis
Combine queries with text, documentation, and visualizations
Share insights across teams
Other options:
Dashboards are for visualization, not query retention
Data Explorer is for ad-hoc analysis
Reports are more static and not designed for iterative DQL workflows
===========