Dynatrace Dynatrace-Associate Dynatrace Associate Certification Exam Exam Practice Test

When monitoring Kubernetes, Dynatrace provides multiple relevant data sources:

Prometheus metrics – ingested and analyzed alongside other metrics

Infrastructure-level metrics – CPU, memory, disk usage from nodes

Kubernetes-specific events and metrics – pods, deployments, namespaces, cluster events

Other options:

Code-level insights relate to application tracing, not Kubernetes data sources directly

OpenKit is used for custom user session tracking, not Kubernetes monitoring

The Dynatrace Hub is the central location for discovering and managing officially supported extensions that enhance the monitoring capabilities of the Dynatrace platform. It provides a curated collection of extensions built and maintained by Dynatrace, ensuring compatibility and support. These extensions cover a wide range of technologies and use cases, allowing users to tailor their monitoring environment to specific needs.

While GitHub hosts various open-source projects related to Dynatrace, not all are officially supported or maintained by Dynatrace. The Dynatrace Community is a valuable resource for user discussions, troubleshooting, and sharing best practices but does not serve as a repository for official extensions. Dynatrace University offers training and educational materials to help users understand and utilize Dynatrace effectively but is not a source for extensions.

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.

To enable automatic anomaly detection in Kubernetes:

Connect Dynatrace to the Kubernetes API to gather cluster data

Deploy OneAgent (via container/Docker/Operator) to monitor nodes and workloads

Enable Kubernetes anomaly detection settings in Dynatrace

This allows Dynatrace to automatically detect issues like CPU saturation.

RUM is unrelated to infrastructure anomaly detection.

Visually Complete measures the time when all visible elements on a page are fully rendered.

It reflects:

What the user actually sees

Completion of visual loading

Option B refers to Largest Contentful Paint (LCP) , not Visually Complete.

DQL (Dynatrace Query Language) is the primary language used to query ingested data in Dynatrace, including logs.

It enables:

Advanced filtering and aggregation

Correlation across logs, metrics, and traces

Flexible data analysis within Grail

Other options:

USQL is legacy

SQL is not used

JavaScript is not a query language in Dynatrace

Dynatrace recommends selecting the appropriate OneAgent mode depending on the role of the host:

Infrastructure mode is recommended when only host-level monitoring is required with minimal overhead

Full-Stack mode is used when deep monitoring is needed, including process-level visibility and full observability

Options like Full support , Discovery , and Half stack are not valid OneAgent monitoring modes in Dynatrace.

When Dynatrace detects that a vulnerable component is exposed to the internet, it highlights this in the risk assessment by marking it with “public internet exposure.”

This indicates:

The vulnerability is not just present

But also externally accessible , increasing its severity and exploitability

This context is critical in prioritizing security issues, as publicly exposed vulnerabilities pose a significantly higher risk.

Other options are incorrect:

Dynatrace does show this information

Tagging alone is not the primary method of indicating exposure

Email alerts are configurable but not the defining behavior

In Dynatrace Data Explorer , you can configure up to five threshold values for a metric. These thresholds allow users to define multiple levels of severity or ranges for visualization and alerting purposes.

This enables:

Better visualization of metric boundaries

Clear differentiation between normal, warning, and critical states

Enhanced dashboard customization

Options with fewer or more thresholds do not align with the platform’s supported configuration.

The Dynatrace Operator is the recommended tool for Kubernetes/OpenShift:

Automates deployment of OneAgent

Manages configuration and lifecycle

Ensures cloud-native full-stack monitoring

Other options:

CSI Driver handles storage integration

OneAgent is deployed by the Operator

Prometheus is unrelated

Dynatrace event categories include:

Availability

Error

Slowdown

Resource

Custom

Info

Monitoring Unavailable

These categories define different types of detected issues.

Critical and Warning are severity levels, not categories.

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.

Log Events allow Dynatrace to detect specific patterns (such as error messages) in logs and automatically trigger alerts.

They enable:

Detection of error patterns in logs

Creation of events/problems

Notification of support teams

Other options:

Log Processing rules transform logs, not alert

Anomaly detection rules are metric-based

Log Metrics convert logs into metrics but don’t directly alert

Log Viewer is for manual inspection

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.

Waterfall analysis provides a detailed breakdown of all resource requests triggered by a user action, including timing for each request.

It allows developers to:

See exactly how long each resource takes to load

Analyze dependencies between requests

Identify bottlenecks in frontend performance

This is especially useful for analyzing resource loading triggered by actions such as button clicks.

Other options:

Web application view provides overview data

User Session Query Language is for querying session data

User action analysis provides aggregated insights, not detailed request timing

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.

OpenKit is used for custom instrumentation when standard agents are not supported.

It enables:

Tracking user sessions

Sending custom telemetry data

Monitoring IoT or unsupported environments

The Databases app in Dynatrace provides infrastructure and performance-level metrics for databases.

Key metrics include:

Memory Consumption , indicating how much memory the database is using

Active Sessions , showing current connections and workload

These metrics help in understanding database health and performance.

Other options are not part of this app:

Code-level insights are provided via services and distributed tracing

User Calls relate to application/service monitoring

Database vulnerabilities are part of Application Security, not database performance metrics

HTTP monitors are designed specifically to simulate HTTP requests to a defined URL or endpoint. They validate response codes, headers, and content, and measure availability and response time from various locations.

Ping tests only check network-level availability using ICMP and do not perform HTTP requests

Single-URL browser monitors simulate real browser interactions, including page rendering and JavaScript execution

Browser clickpaths simulate multi-step user journeys through an application

Therefore, HTTP monitors are the correct choice for simulating direct HTTP requests.

Agentless RUM enables Real User Monitoring without requiring OneAgent installation on the server. It works by injecting a JavaScript snippet into the web application, which captures user interactions and performance data directly from the browser.

This approach is useful when:

You do not have access to the server

Installing OneAgent is not possible

You still need frontend visibility

Other options do not apply:

Dynatrace Operator is for Kubernetes deployments

ActiveGate is used for routing and extending connectivity

Discovery mode still requires OneAgent installation

Classic dashboard reports can be scheduled:

Weekly

Monthly

Daily and bi-weekly options are not supported in classic reporting.

Dynatrace provides a comprehensive observability platform including:

Application Observability – full-stack monitoring of applications

Infrastructure Observability – monitoring hosts, cloud, and containers

Business Events Monitoring – capturing and analyzing business data

Application Security – runtime vulnerability detection and protection

OpenSource is not a Dynatrace platform capability.

When trace enrichment for logs is enabled in Dynatrace, additional metadata is automatically added to logs to correlate them with distributed traces.

The key properties added include:

dt.trace_id – uniquely identifies the distributed trace

dt.span_id – identifies the specific span within the trace

dt.entity.process_group_instance – links the log to the specific monitored process instance

These attributes enable:

Seamless correlation between logs and traces

End-to-end observability across services

Faster root cause analysis by linking logs directly to transactions

The other options are not part of trace enrichment:

dt.security_context is related to log access control, not trace enrichment

DT_RELEASE_VERSION is used for versioning metadata, not tracing

A Span represents a single unit of work within a distributed trace.

A Trace is the full end-to-end transaction

A Span is one step within that trace

Other options:

Context carries metadata

Span kind defines role

Exporter sends data

Only Span represents a single operation.