Study guide
12.1 Management Zones: Scoping Observability, Dashboards & Access Control
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
12.1 Management Zones: Scoping Observability, Dashboards & Access Control
Key Takeaways Explain This Topic AI
Management Zones establish logical, fine-grained access and visibility boundaries across monitored entities without duplicating telemetry or deploying separate Dynatrace environments.
Entities can simultaneously belong to multiple Management Zones, enabling flexible multi-tenant governance across shared infrastructure and independent application teams.
Management Zone rules evaluate dynamic entity attributes including tags, host groups, names, and Kubernetes namespaces, with optional Smartscape propagation across dependent topology layers.
Role-Based Access Control (RBAC) binds user groups to Management Zones with granular permissions such as View Environment, Manage Settings, Log Viewer, and View Sensitive Request Data.
Management Zones act as contextual filters across all platform features, including Davis AI problem detection feeds, Alerting Profiles, Dashboards, and Dynatrace Query Language (DQL) queries.
Last updated: September 2026
Enterprise observability architectures frequently encompass thousands of hosts, tens of thousands of microservice processes, and multiple autonomous business units sharing hybrid cloud infrastructure. In such environments, presenting an unfiltered, global view of all telemetry to every user creates severe operational hazards: alert fatigue, dashboard clutter, accidental configuration changes, and compliance breaches. Dynatrace Management Zones resolve this governance challenge by establishing logical, fine-grained administrative and observational boundaries across the monitored topology without fragmenting data into isolated platform instances.
Architecture of Management Zones: Logical Partitioning vs. Multi-Environment
Historically, organizations attempted to enforce organizational boundaries by deploying multiple, dedicated monitoring environments (e.g., separate Dynatrace SaaS tenants or Managed environments for each business department). While this provided complete physical isolation, it introduced crippling operational penalties:
Blind Spots on Shared Infrastructure: When shared database clusters, message brokers (e.g., Kafka), or Kubernetes worker nodes support multiple business lines, separate environments cannot correlate cross-boundary transaction traces, breaking end-to-end PurePath visibility.
License Inefficiency: Fragmented environments partition Host Unit and Davis Data Unit (DDU) pools, preventing elastic capacity sharing across peaks and valleys.
Administrative Duplication: Operations teams must maintain duplicate synthetic monitors, alerting profiles, extensions, and user directories across dozens of independent consoles.
Management Zones provide virtual partitioning on top of a single, unified Dynatrace environment. Entities exist exactly once in the underlying Grail data lakehouse and Smartscape topological graph. Management Zones act as dynamic lenses or view filters applied dynamically across that shared model. +-----------------------------------------------------------------------------------------+
- | UNIFIED SMARTscape TOPOLOGY |
- | |
- | [Host: k8s-node-01] ---- [Process: Order-Service] ---- [Service: /api/checkout] |
- | | | |
- | [Host: db-cluster-01] -- [Process: Oracle-DB] -------- [Service: OrderDB-Service] |
- +-----------------------------------------------------------------------------------------+
- | |
- +-----------------------+ +-----------------------+
- v v
- +---------------------------------------+ +---------------------------------------+
- | MANAGEMENT ZONE: TEAM-PAYMENTS | | MANAGEMENT ZONE: TEAM-INFRA-OPS |
- | • Scoped Entities: | | • Scoped Entities: |
- | - Service: /api/checkout | | - Host: k8s-node-01 |
- | - Process: Order-Service | | - Host: db-cluster-01 |
- | - Service: OrderDB-Service | | • Access: Infrastructure Admins |
- | • Access: Payment Devs / On-Call SRE | | • Alerting: Node hardware / CPU sat. |
- +---------------------------------------+ +---------------------------------------+
- Overlapping Memberships: Shared Infrastructure Support
A foundational characteristic of Management Zones is that an entity can belong to multiple Management Zones simultaneously . For instance, a shared Kubernetes cluster node running containers for both the "Billing" and "Inventory" applications can belong to:
The Infrastructure-Platform-Ops zone (containing all hosts for cluster-level capacity planning).
The Billing-Production zone (propagated from the billing container process).
The Inventory-Production zone (propagated from the inventory container process).
When a developer from the Billing team logs in, their view is strictly confined to Billing-related services and their associated processes, without displaying unrelated Inventory processes executing on the very same host.
Entity Matching Rules and Smartscape Propagation Mechanics
Management Zones are configured declaratively through rules defined in Settings > Maintenance > Management zones or via the Dynatrace Configuration API ( /api/config/v1/managementZones ). Rules define conditions that determine which entities match the zone.
Supported Entity Types and Condition Criteria
Rules can be defined against all core Dynatrace entity types:
Hosts: Filtered by host name, host group, entity tags, AWS tags, Azure tags, or custom metadata.
Process Groups: Filtered by process group name, executable path, technology type, Docker/Kubernetes container image, or process tags.
Services: Filtered by service name, web service endpoint, web application ID, service type, or service tags.
Applications (Web, Mobile, Custom): Filtered by application name or tags.
Kubernetes / Cloud Applications: Filtered by Kubernetes namespace, cluster name, or workload name.
Synthetic Monitors & Custom Devices: Filtered by monitor name, tag, or target URL.
Topology Propagation Mechanics
In a distributed architecture, services depend on process groups, which in turn execute on hosts. Defining rules manually for every individual host, process, and service would result in thousands of fragile configurations. Dynatrace eliminates this overhead through topological propagation flags :
Propagation Setting Source Entity Target Propagated Entities Common Operational Use Case
Propagate to underlying process groups Service Process Groups hosting the service Grants service owners visibility into JVM/CLR process metrics (garbage collection, memory pools, threads).
Propagate to underlying hosts Service or Process Group Virtual or physical compute hosts Grants application teams visibility into host CPU, memory, and network utilization. (Caution: In multi-tenant hosts, this exposes the host to the service zone).
Propagate to running services Process Group or Host Services spawned by the process/host Used when infrastructure administrators define a zone based on host groups, automatically capturing all application services deployed on those hosts.
Apply to environment Kubernetes Namespace Workloads, pods, containers, and services within the namespace Automatically scopes complete containerized microservice stacks deployed inside a specific namespace.
Exam Key Point: Careful propagation design is essential for security. If an administrator checks "Propagate to underlying hosts" on a rule matching a microservice deployed on a shared, multi-tenant Kubernetes cluster, the entire underlying Kubernetes node becomes visible in that application team's Management Zone. In shared environments, propagation to underlying hosts should generally remain disabled; propagation should stop at the process group level.
Role-Based Access Control (RBAC) & User Permissions
Management Zones serve as the primary enforcement vehicle for Dynatrace Role-Based Access Control. User identity is typically managed via an external Identity Provider (IdP) such as Microsoft Entra ID (Azure AD), Okta, PingFederate, or Keycloak, synchronized using SAML 2.0 and SCIM (System for Cross-domain Identity Management).
In Dynatrace, permissions are not granted to individual user accounts directly. Instead, permissions are assigned to User Groups , and group permissions are scoped either globally or constrained to specific Management Zones.
Granular Management Zone Permissions
When associating a User Group with a Management Zone, administrators can assign granular permission sets:
View environment ( Viewer ): Allows read-only access to all dashboards, Smartscape topology, problem feeds, services, and metrics scoped to the zone. Users cannot modify monitoring configurations, anomaly detection thresholds, or tagging rules.
Manage settings ( Administrator within zone): Permits users to configure service-level anomaly detection, create custom metrics, configure service request naming rules, define web application settings, and manage mute rules within their designated zone.
Log viewer ( View logs ): Enables users to search, stream, and query log data originating from hosts and processes that belong to the zone. If a user lacks this permission, the Logs tab and DQL log queries return empty results for those entities.
View sensitive request data: Grants permission to view unmasked HTTP request parameters, session headers, and database bind parameters. This permission is restricted to compliance-cleared personnel to adhere to PCI-DSS and GDPR privacy standards.
Configure synthetic monitors: Allows creating, modifying, and disabling synthetic browser clicks and HTTP tests assigned to the zone.
Replay user sessions: Permits viewing session replay recordings for end users interacting with web applications within the zone. +-----------------------------------------------------------------------------------------+
- | ACCESS CONTROL PERMISSION UNION |
- +-----------------------------------------------------------------------------------------+
- | User: alex@example.com |
- | Member of Group A: [Zone: Billing] --> Permissions: View environment, View logs |
- | Member of Group B: [Zone: Fulfillment] --> Permissions: View environment, Manage sett.|
- | |
- | Effective Permissions: |
- | • Zone "Billing": Can view metrics and read logs; CANNOT edit settings. |
- | • Zone "Fulfillment": Can view metrics and edit settings; CANNOT read logs. |
- | • Global / Other Zones: NO access (entities invisible in UI and DQL). |
- +-----------------------------------------------------------------------------------------+
When a user belongs to multiple groups that have access to the same Management Zone, Dynatrace calculates the effective permission as the union (the most permissive combination) of all assigned group permissions for that zone.
Operational Scoping: Dashboards, Alerting Profiles & Problem Detection
Beyond access control, Management Zones function as operational filters across day-to-day triage workflows.
The Global Management Zone Filter
At the top of the Dynatrace console, the Management Zone Selector allows users to filter their active workspace. Selecting a Management Zone restricts:
Smartscape Topology: Only displays nodes, processes, and services within the zone.
Problem Feed: Shows only active and resolved Davis AI incidents impacting entities inside the zone.
Services and Hosts Screens: Excludes all entities outside the zone boundaries.
Diagnostic Tools: Filters Service Flow, Top Web Requests, and PurePath distributed trace searches to transactions touching zone entities.
Dashboard Governance
Dashboards can be configured with a default Management Zone filter. When an administrator shares a global "Executive Overview" dashboard, the dashboard dynamically adapts its metric tiles to display only the data belonging to the viewing user's accessible Management Zones. Alternatively, individual tiles can be pinned to explicit Management Zones, allowing a single dashboard to display side-by-side performance comparisons across independent teams.
Alerting Profiles and Notification Routing
Davis AI detects problems at the entity level. To ensure on-call engineers are not alerted for issues outside their domain, Alerting Profiles incorporate Management Zone filters. An Alerting Profile configured with the filter Management Zone: Order-Processing will only trigger notification integrations (e.g., PagerDuty, Slack, ServiceNow) when the root cause or impacted entity resides within that specific zone.
Governance Comparison Matrix
Architectural Layer Management Zone Host Group Tenant Environment
Primary Purpose RBAC access boundary and operational data filtering Infrastructure grouping, OneAgent configuration, and aggregation Complete physical separation of telemetry, licensing, and databases
Entity Membership Many-to-Many (Entities belong to multiple zones) One-to-Many (A host belongs to exactly ONE host group) Mutually exclusive (Entities cannot cross environments)
PurePath Continuity Fully preserved across zones in single trace Fully preserved across host groups Broken (Requires manual HTTP header stitching)
License Consumption Shared global license pool Shared global license pool Dedicated/isolated license quota
Configuration Scope Scopes dashboards, alert profiles, and RBAC Scopes OneAgent updates, network zones, and process detection rules Scopes all global tenant settings and storage policies
Enterprise Governance Best Practices
Drive Management Zones via Automated Tags: Never define management zone rules using static, hardcoded hostnames or IP addresses. Instead, define rules that evaluate standardized tags (e.g., Owner:Team-Billing or Environment:Production ). This ensures newly provisioned cloud instances are dynamically ingested into the correct zone upon deployment.
Avoid Rule Explosion: Consolidate rules using regular expressions or Kubernetes namespace matching rather than creating separate rules for each microservice.
Segregate Production and Non-Production: Maintain strict separation between production and lower environments within alerting profiles and access control groups by incorporating environment-level metadata into management zone boundaries.