If using SSL for agent communication with an AppDynamics Controller, it is recommended that agent SSL traffic

If using SSL for agent communication with an AppDynamics Controller, it is recommended that agent SSL traffic
A . is encrypted with a 64-bit encryption key
B . is decrypted and then encrypted again at the firewall
C . terminates at a reverse proxy or a load balancer in front of the Controller
D . terminates at the Controller

View Answer

Answer: C

Explanation:

AppDynamics recommends that you terminate SSL connections from agents at a reverse proxy or a load balancer in front of the Controller, rather than at the Controller itself. This improves the performance and scalability of the Controller by offloading the SSL processing to the proxy or load balancer. It also simplifies the configuration and management of SSL certificates and truststores. To enable this option, you need to configure the proxy or load balancer to accept SSL connections from agents and forward them to the Controller using HTTP. You also need to configure the agents to use SSL and point to the proxy or load balancer host and port. See Enable SSL for the Java Agent for an example.

Reference: Agent-to-Controller Connections and Enable SSL and SSH for Database Agent Communications in the AppDynamics documentation.