DYNATRACE PRO CERTIFICATION EXAM
SOLVED QUESTIONS AND VERIFIED
SOLUTIONS
◉ OneAgent to ActiveGate connection port.
Answer: OneAgent connects to an Environment ActiveGate on port
9999 (HTTPS).
◉ ActiveGate to Cluster connection ports.
Answer: Environment ActiveGates communicate with the Dynatrace
cluster typically on port 443 or 8443.
◉ Network zones.
Answer: A Network Zone is a logical label that helps control and
optimize OneAgent traffic routing by assigning it to nearby
ActiveGates.
◉ Multi-environment support.
Answer: Dynatrace Managed allows multiple monitoring
environments (tenants) on one cluster, each logically separated with
its own data.
◉ Embedded ActiveGate (Managed cluster).
,Answer: Each Dynatrace Managed cluster node includes an
embedded ActiveGate for cluster-level communication.
◉ Update cadence (SaaS vs Managed).
Answer: SaaS clusters are updated by Dynatrace automatically, while
Managed clusters are updated manually by the administrator.
◉ OneAgent update mechanism.
Answer: OneAgents can be upgraded centrally by the cluster,
automatically or manually depending on settings.
◉ ActiveGate update mechanism.
Answer: Environment ActiveGates support auto-update when
configured or can be updated manually.
◉ High availability for ActiveGates.
Answer: Multiple ActiveGates can be installed in the same zone for
failover and load balancing.
◉ Scaling Dynatrace Managed.
Answer: Add nodes with similar specs or increase node resources to
scale Dynatrace Managed clusters.
,◉ Data storage (Dynatrace cluster).
Answer: Dynatrace cluster nodes use Cassandra for metrics and
Elasticsearch for events/traces.
◉ SaaS data centers vs Managed.
Answer: In SaaS, data is stored in Dynatrace cloud regions. In
Managed, data resides on your own nodes.
◉ Mission Control connectivity requirement.
Answer: Managed clusters must connect to Mission Control
periodically unless using offline mode.
◉ OneAgent performance overhead.
Answer: Typical CPU usage is 1-5% and memory use is modest,
making OneAgent lightweight.
◉ oneagentctl.
Answer: Command-line tool used to configure OneAgent settings
like proxy, network zone, tenant, or restart features.
◉ OneAgent installation methods.
Answer: Install via shell script, MSI installer, or deployment tools
like Chef, Puppet, or Ansible.
, ◉ Dynatrace Managed installation requirements.
Answer: Requires supported Linux OS, recommended hardware, and
open ports between nodes.
◉ Dynatrace Managed node OS and time sync.
Answer: All nodes must run supported OS and have synchronized
time via NTP.
◉ Upgrading Dynatrace Managed cluster.
Answer: Admins upgrade the cluster via Cluster Management
Console, usually once per month.
◉ OneAgent auto-update settings.
Answer: Auto-updates are enabled by default but can be restricted
or scheduled.
◉ ActiveGate installation.
Answer: Run the installer on a networked host and register it to the
target environment using a token.
◉ ActiveGate requirements.
SOLVED QUESTIONS AND VERIFIED
SOLUTIONS
◉ OneAgent to ActiveGate connection port.
Answer: OneAgent connects to an Environment ActiveGate on port
9999 (HTTPS).
◉ ActiveGate to Cluster connection ports.
Answer: Environment ActiveGates communicate with the Dynatrace
cluster typically on port 443 or 8443.
◉ Network zones.
Answer: A Network Zone is a logical label that helps control and
optimize OneAgent traffic routing by assigning it to nearby
ActiveGates.
◉ Multi-environment support.
Answer: Dynatrace Managed allows multiple monitoring
environments (tenants) on one cluster, each logically separated with
its own data.
◉ Embedded ActiveGate (Managed cluster).
,Answer: Each Dynatrace Managed cluster node includes an
embedded ActiveGate for cluster-level communication.
◉ Update cadence (SaaS vs Managed).
Answer: SaaS clusters are updated by Dynatrace automatically, while
Managed clusters are updated manually by the administrator.
◉ OneAgent update mechanism.
Answer: OneAgents can be upgraded centrally by the cluster,
automatically or manually depending on settings.
◉ ActiveGate update mechanism.
Answer: Environment ActiveGates support auto-update when
configured or can be updated manually.
◉ High availability for ActiveGates.
Answer: Multiple ActiveGates can be installed in the same zone for
failover and load balancing.
◉ Scaling Dynatrace Managed.
Answer: Add nodes with similar specs or increase node resources to
scale Dynatrace Managed clusters.
,◉ Data storage (Dynatrace cluster).
Answer: Dynatrace cluster nodes use Cassandra for metrics and
Elasticsearch for events/traces.
◉ SaaS data centers vs Managed.
Answer: In SaaS, data is stored in Dynatrace cloud regions. In
Managed, data resides on your own nodes.
◉ Mission Control connectivity requirement.
Answer: Managed clusters must connect to Mission Control
periodically unless using offline mode.
◉ OneAgent performance overhead.
Answer: Typical CPU usage is 1-5% and memory use is modest,
making OneAgent lightweight.
◉ oneagentctl.
Answer: Command-line tool used to configure OneAgent settings
like proxy, network zone, tenant, or restart features.
◉ OneAgent installation methods.
Answer: Install via shell script, MSI installer, or deployment tools
like Chef, Puppet, or Ansible.
, ◉ Dynatrace Managed installation requirements.
Answer: Requires supported Linux OS, recommended hardware, and
open ports between nodes.
◉ Dynatrace Managed node OS and time sync.
Answer: All nodes must run supported OS and have synchronized
time via NTP.
◉ Upgrading Dynatrace Managed cluster.
Answer: Admins upgrade the cluster via Cluster Management
Console, usually once per month.
◉ OneAgent auto-update settings.
Answer: Auto-updates are enabled by default but can be restricted
or scheduled.
◉ ActiveGate installation.
Answer: Run the installer on a networked host and register it to the
target environment using a token.
◉ ActiveGate requirements.
