Dynatrace-Associate Dynatrace Associate Certification Exam Question and Answers

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

Dynatrace Application Security provides:

Runtime Vulnerability Analytics – detection of vulnerabilities in running applications

Runtime Application Protection (RASP) – protection against exploits in real time

It does NOT provide:

Automatic remediation

Traditional static/on-demand code scanning

Log Security Context in Dynatrace allows restricting access to specific logs based on user roles and permissions.

It enables:

Fine-grained access control over log data

Segmentation of logs based on teams or responsibilities

Secure handling of sensitive log information

Other options do not provide this capability:

Log Processing rules transform logs, not control access

SAML configuration handles authentication

OAuth tokens manage API access

Log Viewer is only for viewing logs

Dynatrace allows adding versioning and metadata to monitored entities through multiple configurable inputs:

Events ingestion can be used to push deployment and version information into Dynatrace, which is then associated with entities

Kubernetes labels allow attaching version metadata (such as app version or build number) to workloads and pods

Environment variables can be used to define version information that OneAgent automatically captures and associates with services or processes

Smartscape is a visualization tool and does not configure metadata.

Security vulnerability relates to application security findings, not version metadata configuration.

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.

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.

The Credential Vault in Dynatrace is used to securely store sensitive data such as usernames, passwords, and tokens for capabilities that require authentication.

It is used by:

Synthetic Browser monitors for login simulations and scripted interactions

Synthetic HTTP monitors for authenticated API testing

Dynatrace Extensions v2 for connecting to external systems that require credentials

Other options are not applicable:

Dynatrace API uses tokens but not stored via Credential Vault in this context

Dynatrace Apps do not rely on Credential Vault for authentication storage

This ensures secure handling of credentials without exposing them in plain text.

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

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.

Log Processing rules in Dynatrace allow transformation of log data during the ingestion phase.

They enable:

Parsing and structuring log data

Masking sensitive information

Enriching logs with additional attributes

Filtering and modifying log content before storage

Other options are unrelated:

Anomaly detection rules are for alerting

Log events are outputs, not transformation tools

Custom process monitoring rules and service detection rules are unrelated to logs

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.

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.

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.

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.

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

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

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

Log ingestion rules in Dynatrace are configured at the environment level .

This ensures:

Centralized control of log ingestion

Consistent processing and filtering across all monitored entities

Unified configuration for all logs entering the platform

Other options are not valid configuration levels:

ActiveGate handles routing, not rule configuration

Host, Process Group, and Host Group are entity levels, not ingestion rule scopes

Classic dashboard reports can be scheduled:

Weekly

Monthly

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

Private Synthetics are used to monitor internal applications that are not publicly accessible.

They run from:

Private locations within your network

Behind firewalls

This allows monitoring of internal-only systems securely.

The 'Databases' app in Dynatrace offers a comprehensive, vendor-agnostic view of all monitored databases. It consolidates performance metrics such as CPU usage, memory consumption, active sessions, response times, and failed connections. It is designed to give users a centralized location for investigating the health and performance of databases, making it the primary tool for such tasks. The app enables teams to correlate issues with underlying infrastructure, understand resource consumption, and identify performance bottlenecks directly tied to the database.

Provided dashboards from a database extension may contain useful visualizations but lack the breadth of metrics and insights that the dedicated Databases app provides. Synthetic tests are primarily used for simulating user behavior to test availability and performance from the user's perspective—not for internal database monitoring. Looking at service data can help in understanding application-level issues but does not deliver detailed or direct metrics from the database layer.