Dynatrace-Associate Exam Results

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

Dynatrace categorizes user types primarily into Real Users and Synthetic Users .

Real Users represent actual human users interacting with applications. Their behavior is captured through Real User Monitoring (RUM), which tracks real-time user interactions, performance, and experience.

Synthetic Users are simulated users generated by Synthetic Monitoring. These are automated scripts that mimic user behavior to test availability and performance proactively.

The terms “Robots” and “Human” are not official Dynatrace user type classifications in the platform. Dynatrace specifically uses the standardized categories of Real and Synthetic users for monitoring and analysis.

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

The Security Investigator app in Dynatrace is designed for advanced security analysis and threat investigation using Dynatrace Query Language (DQL).

It enables users to:

Run and chain multiple queries across logs, metrics, traces, and events

Correlate different data types stored in Grail

Perform deep investigations into potential security incidents

This query-driven approach allows analysts to explore data relationships and uncover threats efficiently.

Other options describe capabilities not related to this app:

Credential vault checks are unrelated

Session investigation is part of RUM and Session Replay

Memory profiling is not a feature of Security Investigator