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

To examine the Java App agent logs on a host without login access, you can use the Controller UI to request the agent logs. This feature allows you to download the agent logs from the Controller UI without having to access the host machine.  You can specify the log level, the time range, and the file size limit for the logs 1 2 

 References :  1 :  Request Agent Logs   2 :  Java Agent Logging

Business Transaction metrics are the key performance indicators that measure the health and performance of your applications. They include metrics such as average response time, calls per minute, errors per minute, and so on. You can use various types of performance degradation analysis to identify and troubleshoot the root causes of performance issues using Business Transaction metrics.

According to the  Troubleshoot Business Transactions - AppDynamics , the following types of performance degradation analysis are used with Business Transaction metrics:

Correlation Analysis: This type of analysis helps you to find the correlation between different metrics and events that may affect the performance of your Business Transactions. For example, you can use the correlation analysis to see how the response time of a Business Transaction is related to the CPU utilization of a node, or how the error rate of a Business Transaction is related to the number of slow database calls.

Remote Services Analysis: This type of analysis helps you to understand how the performance of your Business Transactions is impacted by the calls to remote services, such as databases, web services, message queues, and so on. For example, you can use the remote services analysis to see the response time, call count, error count, and wait time of each remote service call, and drill down to the details of each call.

Compare Releases: This type of analysis helps you to compare the performance of your Business Transactions across different releases of your application. For example, you can use the compare releases analysis to see how the response time, error rate, and throughput of your Business Transactions have changed after a new deployment, and identify any performance regressions or improvements.

Therefore,  A  (Correlation Analysis),  B  (Remote Services Analysis), and  E  (Compare Releases) are three types of performance degradation analysis that are used with Business Transaction metrics.  References:

Troubleshoot Business Transactions - AppDynamics

Business Transaction - AppDynamics

Cisco AppDynamics Associate Performance Analyst Certification

According to the Widgets document 1 , 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

Percentile metrics are a way to measure the distribution of response times for a Business Transaction. They show the value below which a certain percentage of measurements fall. For example, the 50th percentile metric shows the median response time, and the 99th percentile metric shows the worst-case response time for 99% of the transactions. To enable percentile metrics, you need to go to Configuration > Slow Transaction Thresholds and indicate 5 whole numbers between 1 and 99 as Percentiles to Collect. You can then view the percentile metrics in the Metric Browser under Business Transaction Performance > Business Transactions > < Application Name > > < Business Transaction Name > > Percentiles.

https://docs.appdynamics.com/display/PRO45X/Percentile+Metrics