To manage Controller security settings, you would need to grant the Security Administrator role to an existing user. The Security Administrator role is a built-in role that allows the user to access and modify the security settings of the Controller, such as encryption, certificates, authentication, authorization, and audit1. The Security Administrator role also inherits the permissions of the Credentials Administrator role, which allows the user to manage the credentials for the Controller and the agents2. The other roles listed do not have the permission to manage Controller security settings. The Administrator role can perform most administrative tasks, but not security-related ones2. The Analytics Administrator role can manage the analytics platform and data, but not theController security3. The Account Owner role can manage the account settings and licenses, but not the Controller security4
Database Visibility provides metrics on the performance of your database and helps troubleshoot performance-related issues. Database Visibility consists of four main components: Database Agent, Collector, Controller, and Events Service (on-premises only). The Database Agent is a standalone Java program that collects performance metrics about your database instances and database servers. The Collector is the process that runs within the Database Agent to collect performance metrics about your database instances and database servers. The Controller is the central interface where you can see all your database instances and database server performance metrics. The Events Service stores high volumes of metric data.
According to the Overview of Database Visibility, the following types of information are sent to the Controller:
Database-level metrics, such as the number of queries processed and other database statistics
Names and attributes of all sessions, clients, queries, and other objects on the monitored system
The following types of information are sent to the Events Service:
Time that each query spends at each wait state
Individual query statistics for databases that support it
Information about individual execution plans in databases that support it
Therefore, B (Average Number of Slow Connections) and C (Top Leaked Connections) are two stats that are available in Database Visibility. References:
According to the Widgets document1, there are various types of widgets that can be used to create visual representations of data in custom dashboards and war rooms. Some of the widget types are:
Flow Map: A flow map widget displays the flow of traffic between different entities, such as applications, tiers, nodes, backends, and so on. You can customize the flow map to show different metrics, filters, and drill-down options.
iFrame: An iFrame widget allows you to embed an external web page or another dashboard within a custom dashboard. You can specify the URL, height, and width of the iFrame widget.
Health List: A health list widget displays the health status of different entities, such as applications, tiers, nodes, business transactions, and so on. You can customize the health list to show different metrics, filters, and drill-down options.
Therefore, the correct answer is A, B, and C. Snapshot and Funnel Analysts are not widget types, but features or tools that can be accessed from other widgets or dashboards. References:
Widgets
Questions 7
In AppDynamics. what are two places you would find metrics to be added to a custom dashboard? (Choose two.)
Metrics are the numerical values that AppDynamics collects and reports to measure the performance and availability of your applications and their components. You can use metrics to create custom dashboards that display the data that is relevant to your needs and interests.
According to the Metrics - AppDynamics, the following two places are where you would find metrics to be added to a custom dashboard:
The JMX tab on the Node: This tab shows the Java Management Extensions (JMX) metrics that are exposed by the Java Virtual Machine (JVM) or the application server. JMX metrics provide information about the JVM memory, threads, garbage collection, and other aspects of the Java environment. You canadd JMX metrics to a custom dashboard by selecting them from the metric browser tree and dragging them to the dashboard canvas.
The Metric Browser: This is a tool that allows you to browse, search, and view all the metrics that are available in AppDynamics. The metric browser shows the metrics in a hierarchical tree structure that reflects the logical organization of your applications and their components. You can add metrics to a custom dashboard by selecting them from the metric browser tree and dragging them to the dashboard canvas.
Therefore, C (the JMX tab on the Node) and D (the Metric Browser) are two places where you would find metrics to be added to a custom dashboard. References: