Which implementation mode should be used when deploying an EUM Server with reverse proxy from a security and performance standpoint in a production environment?

Which implementation mode should be used when deploying an EUM Server with reverse proxy from a security and performance standpoint in a production environment?
A . Install the EUM Server on the same host as the Controller, behind the reverse proxy.
B . Install the EUM Server on a separate host from the Controller, in front of the reverse proxy.
C . Install the EUM Server on the same host as the Controller, in front of the reverse proxy.
D . Install the EUM Server on a separate host from the Controller, behind the reverse proxy.

View Answer

Answer: D

Explanation:

The EUM Server is the on-premises version of the EUM Cloud that receives, processes, and stores data from EUM agents. For production installation, AppDynamics recommends that the EUM Server and the Controller sit on different hosts, and the EUM Server hosts its own MySQL instance. This improves the scalability and performance of both components. Moreover, AppDynamics strongly recommends that SSL traffic from agents to the EUM Server is terminated at a reverse proxy that sits in front of the EUM Server in the network path, and forwards connections to the EUM Server using HTTP. This relieves the SSL processing load from the EUM Server, simplifies the certificate management, and enhances the security by isolating the EUM Server from the external Internet. Therefore, the best implementation mode for deploying an EUM Server with reverse proxy in a production environment is option D.

Reference: EUM Server Deployment, Install a Production EUM Server, Reverse Proxy configuration for EUM, and Browser EUM installation in the AppDynamics documentation and community.