Study guide
1.1 Dynatrace Platform Capabilities, Web UI Navigation & the Dynatrace Hub
Dynatrace Certified Associate Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Platform Overview, Deployment Models & Architecture
1.1 Dynatrace Platform Capabilities, Web UI Navigation & the Dynatrace Hub 1.2 SaaS vs. Dynatrace Managed Architecture & Security 1.3 Core Telemetry Components: OneAgent, ActiveGate & Grail Lakehouse 1.4 Licensing Models: Dynatrace Platform Subscription (DPS) & Davis Data Units (DDUs)
2 Chapter 2: ActiveGate Architecture & Network Topologies
2.1 ActiveGate Types: Environment vs. Cluster ActiveGates 2.2 ActiveGate Capabilities: Proxying, Private Synthetic, Cloud Integrations & Extensions 2.3 Network Zones, Multi-DC Routing & Firewall Traversal
3 Chapter 3: OneAgent Deployment, Configuration & Management
3.1 OneAgent Architecture, Components & Automatic Injection 3.2 Host Installation on Linux, Windows & Containerized Hosts 3.3 Cloud-Native Deployment: Dynatrace Operator on Kubernetes & OpenShift 3.4 Kubernetes Observability: Clusters, Nodes, Namespaces, Workloads & Events
4 Chapter 4: Monitoring Modes, Process Groups & Infrastructure Observability
4.1 Monitoring Modes: Full-Stack vs. Infrastructure-Only vs. Discovery 4.2 Process Groups, Process Instances & Custom Process Group Detection Rules 4.3 Host Groups, Host Naming Rules & Environmental Metadata Extraction 4.4 Infrastructure & Operations: Host Health, Disk, Network & Availability Analysis 4.5 Database Observability: The Databases App, Connection Pools & Storage Latency
5 Chapter 5: Smartscape Topology & Service Flow
5.1 The 5-Layer Smartscape Topology: Datacenter to Application 5.2 Service Detection: Web Services, Background Tasks & Custom Services 5.3 Service Flow, Backtrace Analysis & Horizontal/Vertical Dependency Mapping
6 Chapter 6: PurePath Distributed Tracing & Code-Level Diagnostics
6.1 PurePath Architecture, Distributed Tracing & Request Context Propagation 6.2 Method Hotspots, CPU Profiling & Memory Allocation Thread Analysis 6.3 Database Service Diagnostics, Slow Queries & Exception Analysis
7 Chapter 7: Davis AI Engine, Baselining & Causation
7.1 Davis Deterministic Causation Engine vs. Pure Correlation 7.2 Automated Dynamic Baselining, Percentiles & Traffic Seasonality 7.3 Event Ingestion, Event Types & Event Hierarchy in Problem Evolution
8 Chapter 8: Problem Lifecycle, Root Cause Analysis & Alerting
8.1 Problem Lifecycle, Severity Categories & Root Cause Cards 8.2 Alerting Profiles, Delay Filters & Management Zone Routing 8.3 Problem Notification Integrations: Webhooks, Slack, ServiceNow & ITSM
9 Chapter 9: Digital Experience Monitoring: Synthetic Monitoring
9.1 Synthetic Monitors: HTTP, Single-Step Browser & Multi-Step Clickpaths 9.2 Private Synthetic Locations, ActiveGate Engines & Credential Vault 9.3 Outage Detection, Performance Baselining & Maintenance Suppression
10 Chapter 10: Digital Experience Monitoring: Real User Monitoring (RUM)
10.1 RUM Architecture, OneAgent Script Injection & Mobile/OpenKit Telemetry 10.2 User Actions: Load vs. XHR/Fetch Actions, Visually Complete & Speed Index 10.3 Apdex Performance Ratings, User Sessions & Session Replay Masking
11 Chapter 11: Log Management and Analytics on Grail with DQL
11.1 Log Management on Grail: Storage, Ingestion Pipelines & Log Masking 11.2 Dynatrace Query Language (DQL): Fetch, Filter, Fields & String Operations 11.3 DQL Aggregations: Summarize, MakeTimeseries, Sorting & Visualizations
12 Chapter 12: Platform Governance, OpenTelemetry & Automation
12.1 Management Zones: Scoping Observability, Dashboards & Access Control 12.2 Tagging Strategies: Automated Rule-Based Tags, Manual Tags & AWS/K8s Metadata 12.3 OpenTelemetry Ingestion, OpenPipeline & Dynatrace Workflows Automation
13 Chapter 13: Cloud Integrations & Agentless Infrastructure Ingestion
13.1 AWS, Azure & Google Cloud Integrations 13.2 VMware vSphere, Extensions & Other Agentless Ingestion Paths
14 Chapter 14: Business Analytics & Business Events
14.1 Business Events: Capture, Ingestion & the bizevents Grail Table 14.2 Business Analytics: Connecting Performance to Revenue, Conversion & KPIs
15 Chapter 15: Notebooks, Dashboards & Data Visualization
15.1 Notebooks: Section-Based Investigation & Shareable Analysis 15.2 Dashboards: Tiles, Variables, Segments & Continuous Monitoring 15.3 Choosing Visualizations: Data Explorer, Chart Types & Metric Selection
16 Chapter 16: Reporting, Metrics & User Behavior Analysis
16.1 Metrics on Grail: Built-in Metrics, Granularity & Retention 16.2 Dashboard Reports, Subscriptions & Exporting Data via APIs 16.3 User Behavior Analysis: Bounce Rate, Landing & Exit Pages, Conversion Goals 16.4 Session Segmentation, User Journeys & Funnel Drop-Off Analysis
17 Chapter 17: Security, Vulnerability Analytics & Application Protection
17.1 Platform Security: Data Privacy, Encryption & Access Control 17.2 Third-Party Vulnerabilities, the Davis Security Score & Security Advisor 17.3 Code-Level Vulnerabilities, Attacks & Runtime Application Protection 17.4 Security Investigator, Notifications & the Remediation Workflow
1.1 Dynatrace Platform Capabilities, Web UI Navigation & the Dynatrace Hub
Key Takeaways Explain This Topic AI
Dynatrace groups its value into four capability pillars — Observability, Security, Automation, and Integration — and the Associate exam's largest scored topic, Foundational Platform Capabilities, tests your ability to name them and place a feature under the right one.
The modern platform is app-based: use-case apps such as Infrastructure & Operations, Kubernetes, Distributed Tracing, Logs, Vulnerabilities, and Business Flow sit on top of five core technologies — Grail, DQL, Davis AI, AppEngine, and AutomationEngine.
Grail is the schema-on-read data lakehouse that stores logs, events, business events, traces, and metrics in one place, and DQL is the single query language used to read all of it.
The Dynatrace Hub is the in-product marketplace for apps, extensions, and technology integrations; it is where you activate a capability rather than installing separate software.
Dynatrace Documentation, the Support Center, the Community, Dynatrace University, and the free Playground tenant are the five official resources the certification learning path expects you to be able to name.
Last updated: September 2026
Before you can deploy a OneAgent or write a single line of DQL, the Dynatrace Associate exam expects you to be able to answer a deceptively simple question: what is Dynatrace, and where do I click? Foundational Platform Capabilities is one of the twelve scored topics on the exam score report, and it is consistently one of the heaviest. Candidates who jump straight into deployment mechanics without learning the platform's vocabulary lose easy points on questions that ask which capability solves a given business problem, or which app a piece of data lives in.
The Four Capability Pillars
Dynatrace describes itself as a platform that delivers analytics and automation for unified observability and security . Its own learning path breaks the value proposition into four pillars, and exam questions frequently ask you to classify a feature into one of them.
Pillar What it means Representative features
Observability Real-time monitoring and visualization of applications, services, and infrastructure OneAgent, PurePath distributed tracing, Smartscape, Real User Monitoring, Synthetic
Security Runtime vulnerability detection, attack protection, data privacy, and compliance Runtime Vulnerability Analytics, Application Protection, Security Investigator
Automation AI-driven discovery, analysis, and no-code/low-code remediation Davis AI, AutomationEngine, Workflows, auto-instrumentation
Integration Ingesting and correlating data from clouds, containers, and open standards Cloud integrations, OpenTelemetry, Extensions, OpenPipeline
The unifying claim is that these are not four products bolted together — they read from the same topology and the same data store , which is why Dynatrace can tell you that a vulnerable library is running in a process that serves a revenue-critical checkout service.
Core Platform Technologies
Underneath the apps sit five named technologies. Memorize what each one is , because distractor answers routinely swap them.
Grail — the schema-on-read data lakehouse . Logs, events, business events, spans, and metrics all land here. Grail requires no up-front schema definition, unlike a relational database.
DQL (Dynatrace Query Language) — the single query language used to read everything in Grail. One language for logs, traces, metrics, and business events.
Davis AI — the causation engine that turns raw anomalies into a small number of ranked problems with an identified root cause.
AppEngine — the framework that lets customers and partners build and share custom apps on top of platform data.
AutomationEngine — the no-code/low-code engine behind Workflows , used to act on observability and security insights.
Two more names appear constantly: OpenPipeline , which processes, enriches, filters, and masks data on ingest before it is stored, and Smartscape , the automatically discovered topology model that gives every entity its relationships.
The App Model and the Web UI
The modern Dynatrace UI is a collection of apps rather than a fixed menu tree. From the Launcher you open the app that matches your use case:
- Infrastructure & Operations — host, process, disk, and network health
- Kubernetes — clusters, nodes, namespaces, workloads, pods
- Distributed Tracing and Services — request-level analysis
- Logs and Notebooks — investigation surfaces
- Dashboards — continuous monitoring surfaces
- Problems — Davis-detected problems and root causes
- Vulnerabilities and Attacks — Application Security
- Business Flow and Business Analytics — business events
- Settings — configuration, and Account Management for licensing
A point of real confusion — and a favourite exam distractor — is that some screens are labelled Classic . Dynatrace is mid-migration from the older, page-based experience (Hosts Classic, Metrics Classic, Synthetic Classic, RUM Classic) to Grail-backed apps. When a question contrasts "the Hosts page" with "the Infrastructure & Operations app," it is usually testing whether you know that the newer app reads from Grail and is queryable with DQL.
Global search and Davis CoPilot (natural-language assistance, including DQL generation) are the two fastest navigation aids in the product.
The Dynatrace Hub
The Dynatrace Hub is the in-product marketplace. It is where you browse, install, and manage:
- Apps — first-party and partner-built UI experiences
- Extensions — technology-specific data collectors (databases, message queues, network devices, VMware, SNMP)
- Technologies and integrations — cloud services, CI/CD tools, ITSM connectors
The exam framing to remember: you do not download and install separate agents to add a capability. You activate it from the Hub, and OneAgent or an ActiveGate picks up the new collection job. A question that offers "download the installer from the support portal" as an option for adding, say, MySQL monitoring is nearly always wrong — the Hub is the answer.
Official Resources You Are Expected to Name
The certification learning path explicitly asks candidates to visit and bookmark these:
Resource Use it for
Dynatrace Documentation (docs.dynatrace.com) Authoritative product behaviour, limits, and configuration reference
- Dynatrace Support Center Support tickets, on-demand courses, live training, certification
- Dynatrace Community Peer discussion, tips, product news
- Dynatrace University Learning plans, the Associate learning path, exam scheduling
- Dynatrace Playground A live, pre-populated demo tenant for hands-on practice at no cost
The Playground matters practically: the Associate exam includes 10 to 15 practical questions , and the practical section is open book. Candidates who have never clicked through a real tenant lose those points regardless of how much theory they memorized. Every "Call to Action" in the official learning path is a Playground exercise — treat them as exam prep, not optional enrichment.
Exam Traps in This Section
Grail is not a database you define schemas for. Answers describing table creation or column typing before ingest are wrong.
DQL is one language for all data types. Distractors that pair a separate query language with logs versus metrics are wrong.
Davis is not "machine learning that correlates." It is deterministic causation built on the Smartscape dependency graph — covered in depth in Chapter 7.
The Hub activates capabilities ; the Support Center is for tickets and training, not feature activation.