2024年最新の有効な500-420リアル試験問題(更新された)100%問題集と練習試験合格させます [Q16-Q34]

Share

2024年最新の有効な500-420リアル試験問題(更新された)100%問題集と練習試験合格させます

[更新されたのは2024年]Cisco 500-420問題準備には無料サンプルのPDF

質問 # 16
Which AppDynamics option will allow a Performance Analyst to compare and filter related servers using custom metadata within your environment?

  • A. Standalone Machine Agent
  • B. Server Visibility
  • C. Dynamic Monitoring Mode
  • D. Server Tagging

正解:D

解説:
Server Tagging in AppDynamics allows a Performance Analyst to compare and filter related servers by using custom metadata. This feature enables users to group and organize their servers based on criteria that make sense for their environment, such as role, location, environment type, or any other custom metadata.
References:
AppDynamics documentation on Server Tagging:
https://docs.appdynamics.com/latest/en/infrastructure-visibility/infrastructure-visibility-settings/server-tags


質問 # 17
A team of developers deploys new Java servlet code that should create new business transactions in AppDynamics. After applying load on the new code function, there are no new Business Transactions on the Business Transaction Dashboard. Whichtwo options should the developers check in AppDynamics to make sure the Business Transactions can be discovered?
[Choose two.)

  • A. Auto discovery for service endpoints is turned on.
  • B. The tier with the new code does not have any rules excluding it.
  • C. There is a health rule created to check for transaction performance.
  • D. The metric browser to see if the new transactions appear under Business Transaction Performance.
  • E. Auto Discovery for servlet is turned on for Java agents.

正解:B、E

解説:
When new business transactions are not appearing on the Business Transaction Dashboard after deploying new code, developers should verify that there are no exclusion rules in place on the tier where the new code was deployed. Additionally, it is crucial to ensure that the Auto Discovery feature for servlets is enabled for Java agents, as this allows AppDynamics to automatically detect and name business transactions based on incoming requests to servlets. Both of these checks are necessary to ensure that new business transactions can be discovered and monitored.References:AppDynamics documentation on Business Transaction detection and Java Agent configuration.


質問 # 18
What must a Performance Analyst first configure in order to monitor end-to-end latency performance metrics in AppDynamics?

  • A. define the end-to-end latency transaction
  • B. endpoints for asynchronous transactions
  • C. slow end-point identity markers
  • D. additional demarcator methods

正解:A

解説:
To monitor end-to-end latency performance metrics, a Performance Analyst must first define the end-to-end latency transaction. This involves configuring the business transactions to include the necessary entry and exit points that capture the complete flow of the transaction, thereby enabling the measurement of the total latency.
References:
AppDynamics documentation on Business Transactions:
https://docs.appdynamics.com/latest/en/application-monitoring/business-transactions


質問 # 19
Which two Key Performance Indicators (KPIs) accurately provide insight into server level resource consumption? (Choose two.)

  • A. CPU %Busy
  • B. Application Restarts
  • C. Calls per Minute
  • D. Memory Used%
  • E. Average Response Time
  • F. Availability

正解:A、D

解説:
Key Performance Indicators (KPIs) such as "CPU %Busy" and "Memory Used%" are critical for providing insights into server-level resource consumption. "CPU %Busy" indicates the percentage of time the CPU is actively working on processes, reflecting the server's processing workload. "Memory Used%" shows the proportion of memory utilized, indicating how much of the server's RAM is being consumed by applications and processes. These KPIs are essential for understanding and managing server performance and resource allocation.
References:
AppDynamics documentation on Server Monitoring: Includes information on monitoring server-level metrics, including CPU and memory utilization, to assess resource consumption.


質問 # 20
Which option, in addition to "minutes since creation", would a Performance Analyst use while configuring Automatic Cleanup of stale Business Transactions?

  • A. Number of Calls
  • B. Regular Expression
  • C. Transaction Type
  • D. Class/Method Filter

正解:A

解説:
When configuring Automatic Cleanup of stale Business Transactions, the "minutes since creation" option is often paired with the "Number of Calls" metric. This setting ensures that business transactions that have not been called within a certain timeframe and have had a negligible number of calls are automatically cleaned up, helping to maintain an organized and relevant set of business transactions in the monitoring system.
References:
AppDynamics documentation on Business Transactions: Discusses best practices for managing business transactions, including the automatic cleanup based on time and call volume thresholds.


質問 # 21
An AppDynamics deployment has Business Transaction Lock Down turned on. The company has just added an important service to its application and wants to track this service as a unique Business Transaction. What action is needed to achieve this?

  • A. Create a Custom Transaction Match Rule based on the Web Service Name and Operation Name
  • B. Modify the Automatic Transaction Discovery rule to include the Web Service Name and Operation Name
  • C. Use the Business Transaction Dashboard for the tier-specific All Other Traffic to register the Business Transaction
  • D. Use live preview to identify the Business Transaction and Register it from there

正解:A

解説:
When Business Transaction Lock Down is enabled in AppDynamics, no new business transactions will be automatically discovered to avoid uncontrolled growth in the number of business transactions. To track a new service as a unique Business Transaction, one needs to create a Custom Match Rule that specifies the criteria for identifying the business transaction. In this case, the Custom Match Rule should be based on the Web Service Name and Operation Name which are the distinguishing characteristics of the new service. This allows for the precise identification and monitoring of the service within the AppDynamics platform.References:AppDynamics documentation on Business Transaction configuration and Custom Match Rules.


質問 # 22
Which option should a Performance Analyst use in an environment where virtual machines are routinely created and destroyed?

  • A. Dappdynamics.agent.node.metainfo and -Dappdynamics.agent.nodeName
  • B. Dappdynamics.agent.reuse.nodeName and - Dappdynamics.agent.reuse.nodeName.prefix
  • C. Dappdynamics.http.proxyHost and -Dappdynamcs.http. proxy User
  • D. Dappdynamics.agent.auto.node.prefix and -Dappdynamics.cron.vm

正解:B

解説:
In environments where virtual machines are frequently created and destroyed, using the agent configuration properties-Dappdynamics.agent.reuse.nodeNameand-Dappdynamics.agent.reuse.nodeName.prefixcan be beneficial. These settings allow AppDynamics agents to reuse node names for newly created instances, facilitating consistent monitoring and tracking across dynamic environments. This approach helps maintain clarity in application topology and ensures that performance data remains coherent even as the underlying infrastructure changes.
References:
AppDynamics documentation on Agent Configuration: Discusses advanced agent configuration options, including node name reuse, to accommodate dynamic environments such as those with frequently changing virtual machines.
AppDynamics documentation on Infrastructure Monitoring: Offers insights into best practices for monitoring in dynamic and virtualized environments.


質問 # 23
What are two examples of backend calls? (Choose two.)

  • A. a request coming from a browser
  • B. a remote services call
  • C. an asynchronous request
  • D. a tier-to-tier request

正解:B、D

解説:
Backend calls in AppDynamics are the interactions that an application component has with external components or services. These can include calls to databases, remote service calls, and interactions between different tiers of an application.
A tier-to-tier request refers to any internal call that happens between different tiers (or nodes) within the same application. For example, a web tier calling an API service tier within the same application ecosystem.
A remote services call is an external call from an application to a service that resides outside of the application's environment, like a call to an external web service, REST API, or a third-party service provider.
References:
AppDynamics documentation on Backend Detection:
https://docs.appdynamics.com/21.6/en/application-monitoring/identify-backends


質問 # 24
Which three pieces of information are required when creating a new database collector? (Choose three.)

  • A. Database hostname/IP address
  • B. System table name
  • C. Database Type
  • D. Port number
  • E. Primary table name

正解:A、C

解説:
When creating a new database collector in AppDynamics, the essential pieces of information required include the "Database hostname/IP address," "Database Type," and "Port number." These details are crucial for establishing a connection to the database and ensuring accurate monitoring. The hostname/IP address identifies the server where the database is hosted, the Database Type specifies the database management system (e.g., MySQL, Oracle), and the Port number is necessary for network communication with the database server.
References:
AppDynamics documentation on Database Visibility: This section explains how to set up database collectors, including the required information for successful configuration.


質問 # 25
Which item supplements business transaction and transaction analytics data with application data?

  • A. Endpoint sensors
  • B. Netflow data
  • C. Demarcation collectors
  • D. Data collectors

正解:D

解説:
Data collectors in AppDynamics supplement business transaction and transaction analytics data with application data by capturing additional information during transaction execution. This can include method arguments, return values, and invocation context, which enriches the transaction data with more detailed application-level insights. This capability is crucial for in-depth performance analysis and troubleshooting, providing a more comprehensive view of application behavior.
References:
AppDynamics documentation on Data Collectors: Explains how to configure data collectors to capture and display detailed application data within business transactions.


質問 # 26
A Performance Analyst has an urgent need to gather more data for an ongoing issue. What should the Performance Analyst do?

  • A. Browse the Metric Browser for errors
  • B. Enable Development Level Monitoring
  • C. Carefully monitor the snapshots for errors
  • D. Review the various transaction snapshots to identify anomalies

正解:B

解説:
If a Performance Analyst has an urgent need to gather more data for an ongoing issue, they should enable Development Level Monitoring. This monitoring level increases the amount of detailed diagnostic data collected by the agent, such as snapshots and transaction traces, which can provide deeper insights into the issue at hand.
References:
AppDynamics documentation on Monitoring Levels: Describes the different levels of monitoring available, including Development Level Monitoring and the types of data each level collects.


質問 # 27
Which three reports can be scheduled for periodic generation and delivery to email recipients? (Choose three.)

  • A. Ad Hoc Data
  • B. Controller Audit
  • C. Custom Dashboard
  • D. Error Trends
  • E. Application Health
  • F. Tier List

正解:C、D、E

解説:
AppDynamics allows for several reports to be scheduled for periodic generation and sent to email recipients.
Among these, Application Health, Error Trends, and CustomDashboards are types of reports that can be automatically generated and delivered, providing regular insights into the application's performance and issues.
References:
AppDynamics documentation on Reports:
https://docs.appdynamics.com/latest/en/application-monitoring/reporting


質問 # 28
What are two options tor sharing snapshot details from the snapshot window? (Choose two.)

  • A. Copy to Clipboard
  • B. Custom Report
  • C. Export
  • D. Download PDF
  • E. Custom Dashboard

正解:C、D

解説:
To share snapshot details from the snapshot window in AppDynamics, the options to "Download PDF" and
"Export" are typically used. "Download PDF" allows users to generate a PDF report of the snapshot details, providing a convenient and portable format for sharing and review. The "Export" option enables the extraction of snapshot data in various formats (e.g., CSV, XML), facilitating further analysis or sharing with other tools and stakeholders.
References:
AppDynamics documentation on Snapshots: This section covers how snapshots capture detailed performance data for transactions, including how to share and export this information for collaborative analysis.


質問 # 29
Which tab within the Application Dashboard displays performance trends for each of Snapshots, Average Response Time, and Events within one central view?

  • A. Transaction Score
  • B. Network Dashboard
  • C. Dashboard
  • D. Events
  • E. Application Flow Map

正解:A

解説:
The Transaction Score tab within the Application Dashboard is designed to display performance trends across various metrics including Snapshots, Average Response Time, and Events. It gives a comprehensive view of the transaction performance, providing a score that reflects the health and reliability of transactions over time.
References:
AppDynamics documentation on Application Dashboard:


質問 # 30
Which three Key Performance Indicators (KPIs) are automatically collected when you create an Information Point without adding custom data? (Choose three.)

  • A. CPU Time
  • B. Errors per Minute
  • C. Maximum Response Time
  • D. Minimum Response Time
  • E. Response Time
  • F. Calls per Minute

正解:B、E、F

解説:
When an Information Point is created in AppDynamics without adding custom data, it automatically collects three key performance indicators (KPIs): Response Time, Errors per Minute, and Calls per Minute. Response Time measures the time taken to complete a transaction or operation, providing insights into application performance. Errors per Minute tracks the number of errors occurring within the scope of the Information Point, helping identify problematic areas. Calls per Minute counts the number of times the specified operation or transaction is invoked, indicating its usage frequency and potential impact on application performance.
References:
AppDynamics documentation on Information Points: Discusses the creation and configuration of Information Points, including the default metrics collected.


質問 # 31
Which built-in scheduled report Includes load, response time, and error graphs?

  • A. User Experience: Browser Apps
  • B. Application Health Report
  • C. All Application Summary
  • D. Dashboard Report

正解:B

解説:
The "Application Health Report" is a built-in scheduled report in AppDynamics that includes vital metrics such as load, response time, and error graphs. This report provides a comprehensive overview of the application's health and performance, making it an essential tool for Performance Analysts to regularly review and share with stakeholders to ensure the application meets performance standards and user expectations.
References:
AppDynamics documentation on Reporting: Covers the types of reports available within AppDynamics, including the Application Health Report, detailing its contents and how to schedule and customize it.
AppDynamics documentation on Application Performance Management: Provides an overview of key performance indicators and metrics critical for assessing application health, many of which are included in the Application Health Report.


質問 # 32

Refer to the exhibit. Using this heap utilization graph, which method is used to confirm if a memory leak is occurring during a certain time frame?

  • A. Refer to the Tiers and Nodes section and into the Memory tab and visualize Heap Utilization (%) and Heap Current Usage (MB) Vs Max (MB)
  • B. In metric browser go through Application Infrastructure > Hardware Resources and select Memory Total (MB) and Used (MB)
  • C. In metric browser go through Application Infrastructure > Hardware Resources > Memory Total (MB) and Swap Used (MB)
  • D. Refer to the Tiers and Nodes section and into the JMX tab and select JVM > Memory > Heap > Max Available (MB) and Current usage (MB)

正解:A

解説:
To confirm if a memory leak is occurring, one should refer to the Tiers and Nodes section of the AppDynamics Controller UI, navigate to the Memory tab, and observe the Heap Utilization over time in relation to the Heap's Current Usage (MB) versus the Maximum (MB) allocated. Consistent growth in heap utilization or an upward trend that does not decrement even after garbage collection indicates a potential memory leak.References:AppDynamics documentation on Memory Leak Detection and Heap Analysis.


質問 # 33

Refer to the exhibit. The transaction score in the graphic displays an interesting performance pattern outside of business hours on 6/16/18. Which additional performance anomaly should be of most interest to a Performance Analyst?

  • A. Lower than usual volume at 6/17/18
  • B. Elevated Response Time at 6/25/18
  • C. Elevated Response Time at 6/19/18
  • D. Low volume at 6/15/18

正解:C

解説:
The performance pattern outside of business hours on 6/16/18 that would be of most interest to a Performance Analyst is the elevated response time, as indicated on 6/19/18. This is because it shows a significant spike in response time, which could indicate a performance issue that needs to be addressed. Anomalies in response time can often be more indicative of underlying problems than changes in call volume, especially when they occur outside of expected peak periods.
References:
AppDynamics documentation on Transaction Score:
https://docs.appdynamics.com/latest/en/application-monitoring/application-dashboard/transaction-score


質問 # 34
......

500-420豪華セット学習ガイドにはオンライン試験エンジン:https://jp.fast2test.com/500-420-premium-file.html


弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

我々の働いている時間: ( GMT 0:00-15:00 )
月曜日から土曜日まで

サポート: 現在連絡 

English Deutsch 繁体中文 한국어