DYNATRACE PROFESSIONAL
CERTIFICATION EXAM
QUESTIONS AND ANSWERS 2026
- 2027
What is automatic service detection in Dynatrace? - ANSWERS-The
process where Dynatrace automatically detects deployed applications
and microservices based on specific properties like application
identifier, URL, or server name. These detected attributes are marked
with an asterisk (✱) on the service overview page under Properties
and tags.
In what circumstances would you need to create service detection
rules? - ANSWERS-When the quality of data available to Dynatrace
is insufficient for high-precision service detection, requiring tailored
detection rules to better match your environment's needs.
How are detection rules evaluated in Dynatrace? - ANSWERS-
Detection rules are evaluated from top to bottom, and the first
matching rule applies, so rule positioning in the list is critical.
What are the prerequisites for configuring rule-based service
detection via the Settings API? - ANSWERS-An access token with
Read settings (settings.read) and Write settings (settings.write)
scopes.
,What happens to original services when you define a new detection
rule? - ANSWERS-Depending on the configuration, original services
might get less traffic or no traffic at all, with new monitoring data
redirected according to the rule configuration.
What are the minimum parameters required to identify a service when
creating a detection rule? - ANSWERS-At least one of the following
must be turned on: Application identifier, URL context root, or Server
name.
What happens to historical data when you modify a service detection
rule? - ANSWERS-Historical data remains available only for the
previous service, while all newly captured data is associated with the
new standalone service.
What happens if you delete a service detection rule? - ANSWERS-All
individual services are split and once again treated as standalone
services.
How can you separate fully monitored web request services when
context root is not supported? - ANSWERS-By imposing a context
root on a fully monitored web request, for example, detecting a
service based on specific URL path segments.
How can you merge application data into a single service when the
incoming data is volatile? - ANSWERS-By using service detection
rules to merge services based on common attributes, such as
application IDs that start with the same prefix.
,How can you separate services for "public network services" based on
URL? - ANSWERS-By creating rules that transform service IDs
based on URL segments when the top-level domain ends with specific
wording.
How can you create different services from the same domain? -
ANSWERS-By instructing Dynatrace to detect multiple services
based on the detected hostname instead of just the domain name (e.g.,
separating support.dynatrace.com and blog.dynatrace.com).
How can Dynatrace track performance of different IPs as separate
service instances? - ANSWERS-By setting up detection rules that
retain information about multiple IPs in the detected service, allowing
tracking of different IPs as separate service instances.
How can you remedy web server naming issues where servers default
to "localhost"? - ANSWERS-By using the environment variable
DT_LOCALTOVIRTUALHOSTNAME to define virtual host names,
ensuring multiple physical hosts report the same virtual host.
How can you define unique application names for technologies that
don't provide them? - ANSWERS-By defining an environment
variable called DT_APPLICATIONID to provide a unique name, or
for Java applications, using the system property
dynatrace.application.id.
, How do you handle rotating or random ports in detection rules? -
ANSWERS-By setting the environment variable
DT_IGNOREDYNAMICPORT=true, which removes the port from
detection and replaces it with *.
What are the four types of request rules you can configure in service
detection? - ANSWERS-Full web request rules, Full web service
rules, External web request rules, and External web service rules.
What is the difference between a "full" and an "external" (opaque)
request in Dynatrace? - ANSWERS-A full request provides complete
monitoring data from the client through all services to the database,
while an external (opaque) request refers to calls to unmonitored
third-party services or hosts.
What are process groups in Dynatrace? - ANSWERS-Groups of
related processes that Dynatrace identifies as belonging together
based on a default set of detection rules. Process groups are key
elements in Dynatrace architecture.
Where can you modify the default process-group detection logic in
Dynatrace? - ANSWERS-In Settings > Processes and containers >
Process group detection section, which includes Built-in detection
rules, Simple detection rules, Advanced detection rules, and
Declarative process grouping pages.
What happens when you implement process group detection settings
or rules? - ANSWERS-Process group detection settings and rules
CERTIFICATION EXAM
QUESTIONS AND ANSWERS 2026
- 2027
What is automatic service detection in Dynatrace? - ANSWERS-The
process where Dynatrace automatically detects deployed applications
and microservices based on specific properties like application
identifier, URL, or server name. These detected attributes are marked
with an asterisk (✱) on the service overview page under Properties
and tags.
In what circumstances would you need to create service detection
rules? - ANSWERS-When the quality of data available to Dynatrace
is insufficient for high-precision service detection, requiring tailored
detection rules to better match your environment's needs.
How are detection rules evaluated in Dynatrace? - ANSWERS-
Detection rules are evaluated from top to bottom, and the first
matching rule applies, so rule positioning in the list is critical.
What are the prerequisites for configuring rule-based service
detection via the Settings API? - ANSWERS-An access token with
Read settings (settings.read) and Write settings (settings.write)
scopes.
,What happens to original services when you define a new detection
rule? - ANSWERS-Depending on the configuration, original services
might get less traffic or no traffic at all, with new monitoring data
redirected according to the rule configuration.
What are the minimum parameters required to identify a service when
creating a detection rule? - ANSWERS-At least one of the following
must be turned on: Application identifier, URL context root, or Server
name.
What happens to historical data when you modify a service detection
rule? - ANSWERS-Historical data remains available only for the
previous service, while all newly captured data is associated with the
new standalone service.
What happens if you delete a service detection rule? - ANSWERS-All
individual services are split and once again treated as standalone
services.
How can you separate fully monitored web request services when
context root is not supported? - ANSWERS-By imposing a context
root on a fully monitored web request, for example, detecting a
service based on specific URL path segments.
How can you merge application data into a single service when the
incoming data is volatile? - ANSWERS-By using service detection
rules to merge services based on common attributes, such as
application IDs that start with the same prefix.
,How can you separate services for "public network services" based on
URL? - ANSWERS-By creating rules that transform service IDs
based on URL segments when the top-level domain ends with specific
wording.
How can you create different services from the same domain? -
ANSWERS-By instructing Dynatrace to detect multiple services
based on the detected hostname instead of just the domain name (e.g.,
separating support.dynatrace.com and blog.dynatrace.com).
How can Dynatrace track performance of different IPs as separate
service instances? - ANSWERS-By setting up detection rules that
retain information about multiple IPs in the detected service, allowing
tracking of different IPs as separate service instances.
How can you remedy web server naming issues where servers default
to "localhost"? - ANSWERS-By using the environment variable
DT_LOCALTOVIRTUALHOSTNAME to define virtual host names,
ensuring multiple physical hosts report the same virtual host.
How can you define unique application names for technologies that
don't provide them? - ANSWERS-By defining an environment
variable called DT_APPLICATIONID to provide a unique name, or
for Java applications, using the system property
dynatrace.application.id.
, How do you handle rotating or random ports in detection rules? -
ANSWERS-By setting the environment variable
DT_IGNOREDYNAMICPORT=true, which removes the port from
detection and replaces it with *.
What are the four types of request rules you can configure in service
detection? - ANSWERS-Full web request rules, Full web service
rules, External web request rules, and External web service rules.
What is the difference between a "full" and an "external" (opaque)
request in Dynatrace? - ANSWERS-A full request provides complete
monitoring data from the client through all services to the database,
while an external (opaque) request refers to calls to unmonitored
third-party services or hosts.
What are process groups in Dynatrace? - ANSWERS-Groups of
related processes that Dynatrace identifies as belonging together
based on a default set of detection rules. Process groups are key
elements in Dynatrace architecture.
Where can you modify the default process-group detection logic in
Dynatrace? - ANSWERS-In Settings > Processes and containers >
Process group detection section, which includes Built-in detection
rules, Simple detection rules, Advanced detection rules, and
Declarative process grouping pages.
What happens when you implement process group detection settings
or rules? - ANSWERS-Process group detection settings and rules
