What are two types of Data Collectors in AppDynamics APM? (Choose two.)
Answer : A, D
In AppDynamics Application Performance Management (APM), two types of Data Collectors are SQL data collectors and Method invocation data collectors. SQL data collectors capture and record detailed information about SQL queries executed by the application, helping identify slow or inefficient database operations. Method invocation data collectors capture information about specific method calls within the application code, including execution times and parameters, providing deep insights into code-level performance.
AppDynamics documentation on Data Collectors: Provides detailed information on configuring SQL and Method invocation data collectors for in-depth application monitoring.
Which permission allows snapshot archiving?
Answer : C
The permission to enable snapshot archiving in AppDynamics typically falls under advanced operational capabilities, such as those categorized under 'Agent Advanced Operation.' This permission allows users to archive transaction snapshots for long-term storage and analysis, which is essential for historical performance analysis and auditing purposes.
AppDynamics documentation on Role-Based Access Control: Explains the different permissions and roles within AppDynamics, including those related to advanced agent operations and snapshot archiving.
A Performance Analyst has noticed a significant decrease in an application's workload (calls/min) and is trying to identify the root cause. Which option will give the Performance Analyst insight into the behavior of the affected Business Transactions?
Answer : C
When a Performance Analyst observes a significant decrease in an application's workload (calls/min), reviewing the 'Top Business Transactions by Load' in the Application Dashboard can provide valuable insights. This feature allows the analyst to quickly identify which business transactions have experienced the most significant changes in load, potentially pinpointing the root cause of the overall workload decrease. It offers a focused view of the application's performance, highlighting areas that may require further investigation or immediate action.
AppDynamics documentation on Application Dashboard: Describes the features and capabilities of the Application Dashboard, including how to view and analyze the top business transactions by load.
AppDynamics documentation on Business Transactions: Details the importance of monitoring business transactions and how they can be used to understand application performance trends.
Which Application Dashboard view categorizes transactions by load, response time, errors, slow transactions, and stalled transactions in a single aggregated value for a specific time range?
Answer : D
The Transaction Score view in the Application Dashboard categorizes transactions by load, response time, errors, slow transactions, and stalled transactions. It provides an aggregated value for a specific time range, giving an at-a-glance indication of the health and performance of business transactions.
AppDynamics documentation on Transaction Score: https://docs.appdynamics.com/latest/en/application-monitoring/application-dashboard
Which two things should a Performance Analyst check if an agent has failed to register with the Controller after several minutes? (Choose two.)
Answer : B, D
If an agent fails to register with the Controller, a Performance Analyst should check the network/firewall rules to ensure that the agent can communicate with the Controller over the network. Additionally, it is crucial to verify the free license count to confirm that there are available licenses for the agent to register. Insufficient licenses or network communication barriers can prevent successful agent registration.
AppDynamics documentation on Agent Registration: Describes the prerequisites and troubleshooting steps for agent registration with the Controller.
AppDynamics documentation on Licensing: Provides details on how the licensing model works, including how to check for available licenses.
A Performance Analyst is experiencing difficulty with the transaction response time on a node. The Performance Analyst attempts to create a health rule monitoring the business transactions' performance on that node. Which set of data should the Performance Analyst select when creating the health rule?
Answer : D
When a Performance Analyst is faced with issues related to transaction response times on a specific node, focusing on the 'Transaction performance' data is most relevant. This is because transaction performance metrics provide direct insights into the business transactions' speed, response times, and execution times, which are critical for identifying and troubleshooting performance issues. By selecting 'Transaction performance' when creating a health rule, the analyst can monitor specific metrics such as average response time, slow transaction count, and very slow transaction count, which are directly related to the performance of business transactions on the node in question.
AppDynamics documentation on Health Rules: This section explains how to create and configure health rules to monitor application performance metrics, including transaction performance.
AppDynamics documentation on Business Transactions: Provides details on how AppDynamics identifies and monitors business transactions, which are key to understanding application performance.
Which values can be used to identify a split exit point?
Answer : C
A split exit point in AppDynamics is identified using static application values. Static values provide a consistent and predictable way to categorize exit points, making it easier to aggregate and analyze similar types of interactions with external services or components.
AppDynamics documentation on Exit Points: Provides insights into how exit points are defined and identified within AppDynamics, including the use of static values for split exit points.