[2026年10月]更新のDynatrace-Associate問題集本日限定!無料アクセス可能に!GoShikenで試そう
学習材料は有効Dynatrace-Associate効率的問題集!
質問 # 33
What are the critical features available with the Dynatrace Application Security feature?
- A. Automatic Vulnerability Remediation
- B. On-Demand Code Security Analysis
- C. Runtime Application Protection
- D. Runtime Vulnerability Analytics
正解:C、D
解説:
Dynatrace Application Security provides:
* Runtime Vulnerability Analytics - detection of vulnerabilities in running applications
* Runtime Application Protection (RASP) - protection against exploits in real time It does NOT provide:
* Automatic remediation
* Traditional static/on-demand code scanning
Reference: Based on official Dynatrace University training materials on Application Security.
質問 # 34
A problem opened with the event category of "Slowdown". Assuming Dynatrace is using the default anomaly detection settings, what entity types can be the root cause of this problem? (Select all that apply)
- A. Services
- B. Applications
- C. Hosts
- D. Processes
- E. Cloud Providers
正解:A、C、D
解説:
In Dynatrace, "Slowdown" problems are typically triggered by performance degradation detected through anomaly detection on monitored entities.
With default settings, the root cause of slowdown problems is usually identified at:
Services, where response time degradation is detected
Processes, where CPU, memory, or other resource bottlenecks occur
Hosts, where infrastructure-level issues impact performance
Applications are higher-level aggregations and are not typically identified as the root cause entity.
Cloud Providers are not treated as root cause entities in anomaly detection.
Dynatrace's AI (Davis) correlates these entities to pinpoint the most likely root cause in the topology.
Reference: Based on official Dynatrace University training materials covering problem detection and Davis AI root cause analysis.
質問 # 35
If a cloud provider does not support installing OneAgent to a specific service (such as for cloud-provided load balancers), is there any way to get code-level data?
- A. No, the only thing available to use is metric data and logs
- B. It depends, if a cloud provider supports sending data in an OpenTelemetry format it can be possible toingest into Dynatrace
- C. Yes, all services support using OpenTelemetry to send code-level data back to Dynatrace
- D. No, cloud providers use their own proprietary tools that are incompatible with Dynatrace
正解:B
解説:
If OneAgent cannot be installed, code-level visibility depends on alternative data ingestion methods .
* If the service supports OpenTelemetry , trace data can be sent to Dynatrace
* This enables partial or full observability depending on the implementation Therefore:
* It is not always possible , but depends on OpenTelemetry support
Other options are incorrect because:
* It's not strictly impossible
* Not all services support OpenTelemetry
* Dynatrace is compatible with cloud providers via multiple ingestion methods Reference: Based on official Dynatrace University training materials on OpenTelemetry and data ingestion.
質問 # 36
What is the default retention period for Logs?
- A. 35 days
- B. 5 years
- C. 10 days
- D. 10 years
正解:A
解説:
Dynatrace stores logs with a default retention period of 35 days .
This provides:
* Sufficient time for analysis
* Balance between storage and cost
Reference: Based on official Dynatrace University training materials on log management.
質問 # 37
Which capability provides a single view of multiple hyperscalers' resources?
- A. Dynatrace RUM
- B. Clouds App
- C. Kubernetes App
- D. Dynatrace Extensions v2
正解:B
解説:
The Clouds App in Dynatrace provides a unified, single-pane view across multiple cloud providers (hyperscalers), such as AWS, Azure, and Google Cloud. It aggregates cloud services, resources, and their relationships into one centralized interface.
This capability allows users to:
* Monitor multi-cloud environments in one place
* Analyze dependencies across different cloud providers
* Gain visibility into cloud services, costs, and performance
Other options do not serve this purpose:
* Extensions v2 extend monitoring capabilities
* RUM focuses on end-user experience
* Kubernetes App focuses specifically on Kubernetes environments
Reference: Based on official Dynatrace University training materials covering cloud platform monitoring and multi-cloud visibility.
質問 # 38
Which steps would I need to perform to automatically detect anomalies, such as cluster CPU-request saturation events on a node, in my Kubernetes environment?
- A. Deploy OneAgent as a Docker container
- B. Enable Dynatrace RUM
- C. Connect Dynatrace to the Kubernetes cluster API
- D. In Dynatrace enable Kubernetes anomaly detection
正解:A、C、D
解説:
To enable automatic anomaly detection in Kubernetes:
* Connect Dynatrace to the Kubernetes API to gather cluster data
* Deploy OneAgent (via container/Docker/Operator) to monitor nodes and workloads
* Enable Kubernetes anomaly detection settings in Dynatrace
This allows Dynatrace to automatically detect issues like CPU saturation.
RUM is unrelated to infrastructure anomaly detection.
Reference: Based on official Dynatrace University training materials on Kubernetes monitoring and anomaly detection.
質問 # 39
Log files from my application may contain messages with errors. Whenever messages like these occur, we wish to notify support teams to investigate. Which Dynatrace feature would best address this ask?
- A. Anomaly Detection rules
- B. Log Viewer
- C. Log Metrics
- D. Log Events
- E. Log Processing rules
正解:D
解説:
Log Events allow Dynatrace to detect specific patterns (such as error messages) in logs and automatically trigger alerts.
They enable:
* Detection of error patterns in logs
* Creation of events/problems
* Notification of support teams
Other options:
* Log Processing rules transform logs, not alert
* Anomaly detection rules are metric-based
* Log Metrics convert logs into metrics but don't directly alert
* Log Viewer is for manual inspection
Reference: Based on official Dynatrace University training materials on log monitoring and alerting.
質問 # 40
Which attribute provides a unique value to view a transaction end-to-end?
- A. Span kind
- B. Service type
- C. Process id
- D. W3C trace id
正解:D
解説:
The W3C trace ID uniquely identifies a distributed trace across all services and components involved in a transaction.
It enables:
* End-to-end visibility of a request
* Correlation of spans across multiple services
* Full trace reconstruction in distributed environments
Other attributes are not unique identifiers:
* Span kind describes the role of a span
* Process ID identifies a process, not a transaction
* Service type categorizes services
Only the W3C trace ID provides a globally unique identifier for a full transaction.
Reference: Based on official Dynatrace University training materials covering distributed tracing.
質問 # 41
Which of the following best describes the functionality of the Security Investigator app?
- A. Investigate user sessions for instances of malicious actors and different cyber-attack vectors
- B. Conduct memory profiling tests to investigate the integrity of short-term data in the case of an attack
- C. Run multiple DQL queries to connect multiple types of data for the primary purpose of investigating security issues
- D. Checks for secure passwords in the credential vault
正解:C
解説:
The Security Investigator app in Dynatrace is designed for advanced security analysis and threat investigation using Dynatrace Query Language (DQL).
It enables users to:
Run and chain multiple queries across logs, metrics, traces, and events Correlate different data types stored in Grail Perform deep investigations into potential security incidents This query-driven approach allows analysts to explore data relationships and uncover threats efficiently.
Other options describe capabilities not related to this app:
Credential vault checks are unrelated
Session investigation is part of RUM and Session Replay
Memory profiling is not a feature of Security Investigator
Reference: Based on official Dynatrace University training materials on Security Investigator and Grail.
質問 # 42
For supported technologies, do Kubernetes workloads and pods get monitored differently than traditionally monitored OneAgent processes?
- A. Yes, workloads and pods must be instrumented with OpenTelemetry to gain deep monitoring insights
- B. No, workloads and pods show different metrics than a process, but give you the same general information
- C. No, workloads and pods show the exact same metrics as a process
- D. Yes, if OneAgent is installed with the Dynatrace Operator, a container will be shown in Dynatrace INSTEAD of a process
- E. Yes, workloads and pods will not have any service data when monitored with Dynatrace
正解:D
解説:
Yes, Kubernetes workloads and pods are monitored differently compared to traditional OneAgent-monitored processes. When Dynatrace is deployed into Kubernetes using the Dynatrace Operator, the OneAgent automatically injects itself into each pod at runtime. This means each container is monitored independently and is shown in Dynatrace as a container entity , not as a traditional process.
This container-based visibility is designed to suit the dynamic and short-lived nature of Kubernetes environments. Traditional OneAgent monitoring associates metrics and topology with processes and hosts, but in Kubernetes, the emphasis shifts toward containers, pods, and workloads. This shift allows Dynatrace to provide accurate and timely data on what's really happening inside containerized apps, aligned with Kubernetes-native objects and metrics.
Other answer options either misstate the behavior (e.g., no service data or requiring OpenTelemetry) or oversimplify the relationship between traditional and Kubernetes monitoring (e.g., "same general information"), making Option E the only correct and fully accurate one.
Reference: Based on official Dynatrace University training content and architecture documentation.
質問 # 43
Welcome to the Practical section of your exam!
This portion of the exam requires you to configure and analyze various components within Dynatrace and is open book using Dynatrace documentation ONLY by opening a new tab. The Dynatrace Operator is already deployed for you in a Kubernetes environment (Linux host) in Cloud-Native Full-Stack. The easyTrade and easyTravel applications are also already deployed for you. You will most likely only interact with the Dynatrace Environment (SaaS Platform). For a majority of these questions: paste or attach your screen captures directly to the question using the image control.
Information for connecting to exam components is provided in Dynatrace University in your event classroom.
Open the Associate Exam Event / Classroom and go to the Environments tab, https://universitv.dvnatrace.com
/account/events
If you deem it necessary: you may use SSH through the built in terminal or through an SSH client of your choice. Use the IP address and credentials provided to log in to the Linux virtual machine running your Kubernetes cluster. When you SSH to the public IP and are presented with the credential prompt, enter the provided username and then the provided password.
Review these and additional instructions for connecting to your environment and creating screenshots by clicking 'View all questions' and then the 'Info' icon.
easyTravel Information
easyTravel is a multi-tier application implemented in .Net and Java. It provides a web portal which allows users to log in, search for journeys to various destinations, select promotional journeys that are offered, and to book a journey using credit card details. Additionally, a Business-to-Business (B2B) web portal for travel agencies is provided where travel agencies can manage the journeys that they offer and can review reports about created bookings.
easyTrade Information
easyTrade is also a multi-tier application that allows you to login as a fake user or even create a new user.
After which point, you are able to buy and sell stocks or deposit money into your balance using fake information. These interactions will create transactions in Dynatrace for you to analyze. However, there is a load generator running which means that interacting with this page should not be necessary to answer the questions.
Tips for completing tasks:
1. Read each task carefully and fully before starting, and then follow the instructions to complete each task.
2. Be sure your screen captures match the requirements stated and are readable.
3. To create your screen captures, you can zoom your screen, or take multiple screenshots to show all the areas requested. You can attach multiple images to the same question. It is recommended to provide more proof than necessary and document your steps. When in doubt, the old saying "show your work", comes in handy.
4. Use a screen capture tool to create and then copy to your clipboard and paste screen captures directly into the file upload control. To upload a file, allowed file types for the upload are: Jpg, .jpeg, and .png.
5. When saving your images for upload into the test be sure that your image titles do not contain the following characters:!,-,_,.,",',(,).
6. To access the web portal, use the links found in the SSH terminal. They will be listed as soon as you login.
Tasks1:
An application team needs to know how much memory their application, EasyTrade, is taking up in their Kubernetes cluster. They have to see the memory usage for all the pods running in the "easytrade' namespace, summed up into a single metric. Use a Dashboard in the new Platform interface (not Dashboards Classic) to show this information to the team and set the timeframe for this data to look at the last 30 minutes. Call this dashboard "EasyTrade memory usage".
Screen capture(s) required:
Upload image(s) that show the following:
1. A dashboard "EasyTrade memory usage".
2. The tile used to display memory usage for all pods in the "easytrade" namespace as well as its configuration.
正解:
解説:
See the solution below
Explanation:
Objective
Create a dashboard in the new Dynatrace platform (NOT Classic) that shows:
* Memory usage
* For all pods
* In easytrade namespace
* Summed into a single metric
* Timeframe = Last 30 minutes
* Dashboard name = EasyTrade memory usage
# STEP-BY-STEP EXECUTION
# Step 1: Open Dashboards (New Platform)
* Go to: # Dashboards & Notebooks
* Click: # Dashboards
* Click: # Create Dashboard
# Step 2: Name the Dashboard
* Set name exactly as: # EasyTrade memory usage
## Match spelling exactly (case-sensitive matters sometimes)
# Step 3: Add a Tile
* Click: # Add Tile
* Select: # Data Explorer
# Step 4: Select the Correct Metric
In the metric selector:
# Choose:
* Kubernetes container memory usage
Typical metric:
builtin:kubernetes.container.memory.usage
# Step 5: Apply Namespace Filter
* Add filter: # Kubernetes Namespace = easytrade
## This is CRITICAL (without this # wrong answer)
# Step 6: Aggregate Data (MOST IMPORTANT STEP)
* Set: # Aggregation = SUM
# This ensures:
All pods memory = ONE combined value
# Step 7: Remove Splitting
* Ensure: # No Split by anything (pod/container/etc.)
## If you see multiple lines # YOU DID IT WRONG
# Step 8: Choose Visualization
Pick one:
* # Single value tile (BEST for exam)
* OR simple graph (no split)
# Step 9: Set Timeframe
Top right of dashboard:
# Set:
* Last 30 minutes
# Step 10: Save Dashboard
* Click: # Save
質問 # 44
I need fine-grained control of the Business Events data ingested. Adding which attribute allows me to achieve this?
- A. dt.traceid
- B. dt.spanid
- C. dt.security.context
- D. dt.entity.process_group_instance
正解:C
解説:
The dt.security.context attribute enables fine-grained access control over ingested data, including Business Events.
It allows:
* Segmentation of data
* Restricting access to specific users or groups
* Applying security boundaries to sensitive datasets
Other attributes are related to tracing:
* dt.traceid and dt.spanid are for distributed tracing
* dt.entity.process_group_instance links data to entities
Only dt.security.context provides control over data access and segmentation.
Reference: Based on official Dynatrace University training materials covering Grail and data security.
質問 # 45
Given a scenario where you have a service with a problem of a high failure rate, which service page should be the first one to check?
- A. Comparisons
- B. Distributed Traces
- C. Response Time Hotspots
- D. Failure Analysis
正解:D
解説:
The Failure Analysis page is the primary view for investigating high failure rates.
It provides:
* Breakdown of errors
* Failure patterns
* Root cause indicators
This makes it the first place to investigate when failures increase.
Reference: Based on official Dynatrace University training materials on service analysis.
質問 # 46
I need to perform data transformation on logs during the ingestion phase, which capability provides this functionality?
- A. Anomaly Detection rules
- B. Custom process monitoring rules
- C. Service detection rules
- D. Log Events
- E. Log Processing rules
正解:E
解説:
Log Processing rules in Dynatrace allow transformation of log data during the ingestion phase.
They enable:
* Parsing and structuring log data
* Masking sensitive information
* Enriching logs with additional attributes
* Filtering and modifying log content before storage
Other options are unrelated:
* Anomaly detection rules are for alerting
* Log events are outputs, not transformation tools
* Custom process monitoring rules and service detection rules are unrelated to logs Reference: Based on official Dynatrace University training materials on log monitoring and processing.
質問 # 47
How best is the "Visually complete" metric defined?
- A. The amount of time the first CSS element takes to load
- B. A simulated test that's run on the user's browser to evaluate how fast the browser can render an image
- C. When all of the elements visible to the user on a webpage are 100% loaded and rendered
- D. When the largest element of the page is reported as rendered by the browser
正解:C
解説:
Visually Complete measures the time when all visible elements on a page are fully rendered.
It reflects:
* What the user actually sees
* Completion of visual loading
Option B refers to Largest Contentful Paint (LCP) , not Visually Complete.
Reference: Based on official Dynatrace University training materials on RUM metrics.
質問 # 48
I want to view versioning metadata of the components I monitor in Dynatrace. Which options do I have for configuring this data? (Select all that apply)
- A. Security vulnerability
- B. Kubernetes labels
- C. Environment variables
- D. Events ingestion
- E. Smartscape
正解:B、C、D
解説:
Dynatrace allows adding versioning and metadata to monitored entities through multiple configurable inputs:
Events ingestion can be used to push deployment and version information into Dynatrace, which is then associated with entities Kubernetes labels allow attaching version metadata (such as app version or build number) to workloads and pods Environment variables can be used to define version information that OneAgent automatically captures and associates with services or processes Smartscape is a visualization tool and does not configure metadata.
Security vulnerability relates to application security findings, not version metadata configuration.
Reference: Based on official Dynatrace University training materials on metadata, tagging, and deployment tracking.
質問 # 49
I need to restrict access of certain log files to specific Dynatrace users, which Dynatrace capability provides this?
- A. Log Viewer
- B. SAML Configuration
- C. Log Processing rules
- D. OAuth token
- E. Log Security Context
正解:E
解説:
Log Security Context in Dynatrace allows restricting access to specific logs based on user roles and permissions.
It enables:
* Fine-grained access control over log data
* Segmentation of logs based on teams or responsibilities
* Secure handling of sensitive log information
Other options do not provide this capability:
* Log Processing rules transform logs, not control access
* SAML configuration handles authentication
* OAuth tokens manage API access
* Log Viewer is only for viewing logs
Reference: Based on official Dynatrace University training materials covering log management and access control.
質問 # 50
How can Business Event data be ingested into Dynatrace?
- A. OpenTelemetry
- B. Logs
- C. Dynatrace API
- D. Web and mobile RUM
- E. Dynatrace OneAgent
正解:A、C
解説:
Business Event data can be ingested into Dynatrace using:
* Dynatrace API - allows sending structured business events directly into the platform
* OpenTelemetry - supports ingestion of custom event data through open standards Other options are incorrect:
* OneAgent focuses on observability data, not business events
* Logs are separate data types, not primary business event ingestion
* RUM captures user interactions, not structured business events
These ingestion methods enable flexible integration of business data into Dynatrace for analysis.
Reference: Based on official Dynatrace University training materials on Business Events and Grail ingestion.
質問 # 51
Which of the following Synthetics simulate a user performing multiple actions across your website(s)?
- A. Ping test
- B. HTTP monitor
- C. Single URL browser monitors
- D. Browser clickpaths
正解:D
解説:
Browser clickpaths simulate full user journeys across multiple steps in a web application.
They:
* Perform multiple actions (clicks, navigation, form submissions)
* Simulate real user workflows
* Validate end-to-end functionality
Other options:
* HTTP monitor = single request
* Single URL browser monitor = single page load
* Ping test = network check only
Reference: Based on official Dynatrace University training materials on Synthetic Monitoring.
質問 # 52
Which metrics are presented within the Databases app? (Select all that apply)
- A. Active Sessions
- B. Memory Consumption
- C. Database vulnerabilities
- D. User Calls
- E. Code-level insights
正解:A、B
解説:
The Databases app in Dynatrace provides infrastructure and performance-level metrics for databases.
Key metrics include:
* Memory Consumption , indicating how much memory the database is using
* Active Sessions , showing current connections and workload
These metrics help in understanding database health and performance.
Other options are not part of this app:
* Code-level insights are provided via services and distributed tracing
* User Calls relate to application/service monitoring
* Database vulnerabilities are part of Application Security, not database performance metrics Reference: Based on official Dynatrace University training materials covering database monitoring.
質問 # 53
......
Dynatrace Dynatrace-Associate 認定試験の出題範囲:
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
| トピック 7 |
|
| トピック 8 |
|
| トピック 9 |
|
| トピック 10 |
|
最新のDynatrace-Associate試験エンジンPDFで全部無料問題集保証:https://www.goshiken.com/Dynatrace/Dynatrace-Associate-mondaishu.html