Which attribute provides a unique value to view a transaction end-to-end?
Answer : D
The W3C trace ID uniquely identifies a distributed trace across all services and components involved in a transaction.
It enables:
End-to-end visibility of a request
Correlation of spans across multiple services
Full trace reconstruction in distributed environments
Other attributes are not unique identifiers:
Span kind describes the role of a span
Process ID identifies a process, not a transaction
Service type categorizes services
Only the W3C trace ID provides a globally unique identifier for a full transaction.
===========
Question 2
Which of the cloud providers does Dynatrace natively support without extensions?
Answer : A, B, D
Dynatrace provides native integration (without requiring extensions) for the major hyperscalers:
Amazon Web Services (AWS)
Microsoft Azure
Google Cloud Platform (GCP)
These integrations provide deep visibility into cloud services, APIs, and metrics.
Other providers:
DigitalOcean and IBM Cloud are not natively supported at the same level and typically require extensions or custom integration.
===========
Question 3
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
===========
Question 4
For supported technologies, do Kubernetes workloads and pods get monitored differently than traditionally monitored OneAgent processes?
Answer : E
Yes, Kubernetes workloads and pods are monitored differently compared to traditional OneAgent-monitored processes. When Dynatrace is deployed into Kubernetes using the Dynatrace Operator, the OneAgent automatically injects itself into each pod at runtime. This means each container is monitored independently and is shown in Dynatrace as a container entity, not as a traditional process.
This container-based visibility is designed to suit the dynamic and short-lived nature of Kubernetes environments. Traditional OneAgent monitoring associates metrics and topology with processes and hosts, but in Kubernetes, the emphasis shifts toward containers, pods, and workloads. This shift allows Dynatrace to provide accurate and timely data on what's really happening inside containerized apps, aligned with Kubernetes-native objects and metrics.
Other answer options either misstate the behavior (e.g., no service data or requiring OpenTelemetry) or oversimplify the relationship between traditional and Kubernetes monitoring (e.g., 'same general information'), making Option E the only correct and fully accurate one.
===========
Question 5
Select the most appropriate tool to use based on this scenario:
A colleague wants to see the Visually Complete time and the User Action time for a subset of user actions, filtered by a specific user action property and multiple different geolocations. This user specifically wants to ensure that they can see all the user actions that have the same name across multiple apps.
Answer : D
Multidimensional Analysis for User Actions is designed specifically for deep analysis of user actions with multiple filters and dimensions.
It allows:
Filtering by user action properties
Comparing across geolocations
Aggregating user actions with the same name across applications
Viewing metrics like Visually Complete time and User Action duration
Other tools are less suitable:
USQL is legacy and less flexible
Dashboards are for visualization, not deep filtering
Data Explorer focuses on metrics, not user actions
Notebooks are not optimized for this specific RUM analysis
===========
Question 6
I want to import metrics on a platform that is not supported by the OneAgent, what options do I have? (Select all that apply)
Answer : A, C
When a platform is not supported by OneAgent, Dynatrace provides alternative methods to ingest metrics:
OpenTelemetry allows ingestion of metrics using open standards, enabling integration with unsupported platforms by exporting telemetry data into Dynatrace
Dynatrace Extensions (especially Extensions v2) allow users to collect custom metrics from technologies that are not natively supported
Installing ActiveGate alone does not enable metric ingestion unless it is used in combination with extensions or APIs. Creating a Dynatrace App is unrelated to metric ingestion and is instead used for building custom UI or workflows within the platform.
===========
Question 7
What Dynatrace tool is utilized to initially perform Application Security monitoring?
Answer : C
OneAgent is the primary component used to initially enable Application Security (AppSec) monitoring in Dynatrace.
It automatically:
Instruments application code
Detects vulnerabilities at runtime
Captures security-related data such as code-level weaknesses and attack vectors
This built-in capability allows Dynatrace to provide continuous application security without requiring additional manual instrumentation.
AppSec Apps are used to analyze and visualize detected vulnerabilities but rely on data collected by OneAgent.
ActiveGate handles communication and routing.
OpenTelemetry is used for telemetry ingestion, not native AppSec monitoring.
All Official Question Types