Two types of information that can be shared without an AppDynamics login are Flow Map and Custom Dashboards. Flow Map is a graphical representation of the application topology, showing the interactions between the tiers, nodes, backends, and remote services. Custom Dashboards are user-defined views of the application performance data, metrics, and events.  You can share these types of information by generating a shareable link from the Controller UI, which can be accessed by anyone who has the link, without requiring a login 1 2   References :  1 :  Share a Flow Map   2 :  Share a Custom Dashboard

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 audit 1 .  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 agents 2 . 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 ones 2 .  The Analytics Administrator role can manage the analytics platform and data, but not the Controller security 3 .  The Account Owner role can manage the account settings and licenses, but not the Controller security 4

https://docs.appdynamics.com/appd/21.x/21.1/en/application-monitoring/install-app-server-agents/agent-to-controller-connections

According to the Java Memory Leaks document 1 , one of the ways to detect and troubleshoot Java memory leaks is to use the Automatic Leak Detection feature on the Memory tab of the Node Dashboard. This feature captures and analyzes the collections that are actively used and growing in size over time, indicating a potential memory leak. You can also drill down into the leaking collections to see the content summary and the access traces that show the code path and the business transactions that access the collection. Therefore, the correct answer is D. Examining the values on the Server tab, configuring Object Instance Tracking, or verifying and adjusting the Memory Monitoring configuration may not directly reveal the source of the memory leak, but they may provide some useful information or metrics to support the diagnosis.  References :

Java Memory Leaks

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:

Cisco AppDynamics Associate Administrator Certification

Overview of Database Visibility - AppDynamics

Database Visibility - AppDynamics

A group can contain multiple roles, which means that the users in the group inherit the permissions of all the roles assigned to the group.  For example, you can create a group that has both the Administrator and the Analytics Administrator roles, and the users in that group can perform both the administration and the analytics tasks 1   References :  1 :  Roles and Permissions

A data collector is used to capture application data in a single business transaction. A data collector is a configuration that specifies what data to capture from a business transaction and how to store it in the AppDynamics Controller or the analytics platform. You can capture data from HTTP requests, method invocations, custom fields, or information points. You can also apply filters and transformations to the captured data. The captured data can be used for various purposes, such as adding context to business transactions, creating custom metrics, triggering health rules, enriching transaction analytics, or creating business journeys. https://university.appdynamics.com/certifications/associate-administrator

https://docs.appdynamics.com/appd/22.x/latest/en/application-monitoring/business-transactions

https://docs.appdynamics.com/display/PRO45X/Install+the+Database+Agent

To properly configure a database agent from a zip file, you need to provide the following minimum details:

Controller Host: This is the hostname or IP address of the machine where the Controller is installed.  You need to specify this so that the Database Agent can communicate with the Controller and send the collected data 1

Controller Port: This is the port number that the Controller listens on for incoming connections. You need to specify this so that the Database Agent can connect to the Controller using the correct protocol.  The default ports are 8090 for HTTP and 8181 for HTTPS for on-premise Controllers, and 80 for HTTP and 443 for HTTPS for SaaS Controllers 1

Account Access Key: This is the key that authenticates the Database Agent with the Controller. You need to specify this so that the Database Agent can register itself with the Controller and access the license.  You can find the account access key in the Controller UI under Settings > License > Account 1

Account Name: This is the name of the account that the Database Agent belongs to. You need to specify this so that the Database Agent can associate itself with the correct application and user permissions.  You can find the account name in the Controller UI under Settings > License > Account 1

References :  1 :  Install the Database Agent

By default, the Java Agent enables two Sensitive Data Filters substring: substring “key” and substring “password”. These filters prevent the agent from capturing and sending any data that contains these substrings to the Controller, such as query parameters, HTTP headers, cookies, environment variables, or system properties. This helps to protect sensitive information from being exposed in the Controller UI or reports.  You can also add more filters or modify the existing ones by editing the agent configuration file 1   References :  1 :  Filter Sensitive Data