QUESTIONS AND ANSWERS 2025/2026 ALL RATED A+
✔✔How can you further restrict the scope of role-type permissions in Dynatrace? -
✔✔By restricting the scope to individual management zones.
✔✔What is the purpose of the "Default group with all users" in Dynatrace? - ✔✔It
provides minimum permissions to all users, with the ability to add additional permissions
that will be granted to all users.
✔✔What determines a user's group membership when logging in using SAML
federation? - ✔✔The security group claim attribute of the SAML response is used to
determine the user's group membership.
✔✔How can group management tasks be automated in Dynatrace? - ✔✔All group
management tasks can be carried out via the Dynatrace Account Management API.
✔✔What are the three organization levels for IAM policies in Dynatrace and how do
they differ - ✔✔Global (predefined by Dynatrace, apply to all accounts and
environments, cannot be edited), Account (apply to all environments under that account,
used for company-wide policies), and Environment (apply only to a single customer
environment).
✔✔What are built-in policies in Dynatrace? - ✔✔Predefined global policies shipped with
Dynatrace IAM that cannot be edited but can be applied by assigning them to a group
for the whole account or any environment.
✔✔What is the correct syntax for a Dynatrace policy statement? - ✔✔ALLOW
[permission]; or for multiple permissions: ALLOW [permission1], [permission2],
[permission3];
✔✔How do you apply a policy to users in Dynatrace? - ✔✔By binding the policy to a
group, as users inherit permissions from the groups they belong to
✔✔Policy Statement - ✔✔A declaration specifying exactly what permissions a policy
allows, using the ALLOW syntax pattern followed by specific service permissions (e.g.,
"ALLOW settings:objects;")
✔✔What is the default built-in bucket for log data in Grail and what is its retention
period? - ✔✔The default built-in bucket for log data is "default_logs" with a retention
period of 35 days.
✔✔What permissions are required to manage Grail buckets in Dynatrace? -
✔✔storage:bucket-definitions:read
,storage:bucket-definitions:write
storage:bucket-definitions:delete
storage:bucket-definitions:truncate
✔✔How do you identify logs directed to specific buckets using DQL? - ✔✔Use the DQL
filter: | filter dt.system.bucket == 'bucketName' and include dt.system.bucket in the fields
command.
✔✔What happens when two buckets with different retention periods could potentially
store the same logs? - ✔✔The system ensures no duplication by prioritizing the rule that
matches first, guaranteeing that only the first matching rule governs the storage.
✔✔How can you exclude certain logs from storage in Dynatrace? - ✔✔Create a bucket
assignment rule, select "Don't store in a bucket" for the Bucket setting, and define a
DQL matcher that identifies the logs you want to exclude.
✔✔What is the basic format of a Dynatrace Grail permission policy statement? - ✔✔The
basic format is: ALLOW [permission] WHERE [conditions];
Example: ALLOW storage:buckets:read WHERE storage:bucket-name = "default_logs";
✔✔What are the three operators that can be used in the WHERE clause for bucket
permissions? - ✔✔1. = (equals): for exact match
2. STARTSWITH: with an expression in quotation marks
3. IN: for indicating a range
✔✔What permission is required to access log data in Grail? - ✔✔storage:logs:read
permission is required to access log data. Additionally, bucket permissions are needed.
Example: ALLOW storage:logs:read WHERE storage:bucket-name="default_logs";
✔✔What is the purpose of fieldsets in Dynatrace Grail permissions? - ✔✔Fieldsets
allow you to hide fields that might contain sensitive data. Only users with proper
permissions can use sensitive fields in DQL queries for filtering and grouping.
Otherwise, these fields won't appear in query results.
✔✔What are the configuration limits for record permissions in Dynatrace Grail? -
✔✔Maximum 100 statements per policy
Maximum 200 policies per account
✔✔What are Cost Monitors in Dynatrace and when do they begin functioning? -
✔✔Cost Monitors help manage Dynatrace Platform Subscription budget by monitoring
overall forecasted usage and daily costs, alerting when usage changes significantly or
, exceeds thresholds. They begin executing 30 days after the subscription start date
when sufficient forecast data is available.
✔✔What are the two types of events generated by Budget Monitoring in Dynatrace? -
✔✔1. Forecast events when costs exceed a user-defined limit (default 100%)
2. Forecast events when costs increase significantly week-over-week (default threshold
10%)
✔✔What three conditions must be met for Dynatrace to generate a Cost Event? - ✔✔1.
The observed daily value exceeds the forecast upper range by $10 USD
2. The cost increase is statistically relevant compared to previous cost data points
3. The relevance score is determined by comparing the cost increase against the
median cost from the past 14 days
✔✔How can users receive notifications about Cost Monitor events? - ✔✔Users can
receive notifications about Cost Monitor events through:
1. API (documented in Dynatrace Platform Subscription API documentation)
2. Email notifications (sent from ) Users can manage email
settings in the Notification settings section of the Notifications Center.
✔✔What permission is required to manage notification settings for Cost Monitors? -
✔✔The "View and manage account and billing information" account permission is
required to manage notification settings for Cost Monitors.
✔✔What are the core features and default behaviors of Dynatrace Cost Monitors? -
✔✔Help manage DPS budget and identify unexpected cost increases
Monitor overall forecasted usage and daily costs at capability/environment levels
Notify when forecast costs exceed budget or when significant week-over-week
increases occur
Alert when capability costs exceed predicted levels (above upper forecast range)
Enabled automatically for all DPS accounts
Default notifications are sent to license administrators without requiring configuration
License administrators can adjust thresholds and configure email distribution