Dynatrace Associate study plan

Diagram the Dynatrace platform layers (OneAgent, ActiveGate, cluster, Grail) and state the data flow from agent to UI from memory

Distinguish entity types in Smartscape (host, process, service, application, Kubernetes node) and explain how relationships are inferred

Explain the difference between metrics, logs, events, traces, and business events as stored in Grail and which query language accesses them

Write and run 8 basic DQL queries covering fetch, filter, summarize, and sort against sample data

Compare SaaS, Managed, and cluster deployment models on data residency and upgrade responsibility

Complete the fundamentals domain self-check and list every missed concept as a remediation task

Trace a single user request end-to-end across browser, service, and database tiers and label each span type

Explain how services are detected and named, and predict how code changes alter service boundaries

Read a distributed trace to identify the slowest span and the failing span, and articulate the difference

Configure an alerting profile and a notification integration in a sandbox tenant

Analyze backtraces and method hotspots to isolate the exact method responsible for latency in a sample application

Define request attributes and capture rules, then verify capture on live traffic

Build a failure-detection rule and interpret the resulting problem card and root-cause hints

Explain how exception analysis groups and correlates exceptions across services

Set a service-level objective on a key request and describe what a budget burn rate alert does

Interpret host health signals including CPU, memory, disk, and network saturation and distinguish cause from symptom

Monitor a process group and explain what makes a process a monitoring target versus incidental

Navigate Kubernetes observability views to relate pod, workload, and node health to application impact

Connect a cloud service (e.g., a managed database or load balancer) and confirm metrics are flowing

Write an infrastructure-focused problem notification and explain why the threshold you chose is appropriate

Complete the infrastructure self-assessment and rewrite every wrong answer as a study note

Explain the difference between real user monitoring, synthetic monitoring, and session replay, and pick the right one for three given scenarios

Deploy the RUM JavaScript agent on a test page and confirm user actions appear in the UI

Configure user action naming rules and custom actions so a multi-step funnel is legible

Create and interpret a browser clickpath synthetic monitor, including validation rules and scheduling

Analyze Core Web Vitals and front-end performance metrics to locate a rendering bottleneck

Set up a conversion goal or key user action and read the resulting user journey funnel

Investigate a session replay to describe the user's path to an error and the affected user segment

Explain how mobile and custom application monitoring differ from browser monitoring

Explain the Application Security module's three pillars - vulnerability analytics, threat observability, and security posturing - and what each answers

Investigate a reported third-party vulnerability and identify the affected library, process, and exposure path

Interpret a detected attack event and determine whether it was blocked or only observed

Use the security posture view to identify a misconfiguration risk and state the remediation

Explain how security settings, sensitivity levels, and detection rules change what is flagged

Re-run timed practice assessments domain by domain and record a score per domain

Remediate every domain scoring below 75% by re-reading notes and redoing missed items

Build a one-page cheat sheet covering the concept most often confused across all five domains

Rehearse explaining three troubleshooting scenarios aloud in exam-style reasoning order