Cisco AppDynamics Professional Implementer

Answer: C Placing a single-node Events Service deployment behind a load balancer lets clients use a stable endpoint. The deployment can later grow into a multi-node cluster without modifying client configurations; redundancy requires multiple nodes. **Learn more:** [Single Node Deployment | AppDynamics On-Premises](https://help.splunk.com/en/appdynamics-on-premises/events-service-deployment/events-service-deployment/single-node-deployment) · [Load Balance Events Service Traffic | AppDynamics On-Premises](https://help.splunk.com/appdynamics-on-premises/events-service-deployment/events-service-deployment/load-balance-events-service-traffic)

Answer: B, D A Database Agent upgrade preserves its Controller connection configuration by copying `controller-info.xml` from the backed-up agent directory to the new installation. The upgrade procedure also stops the existing Database Agent and starts the new agent after installation. The Controller does not require a restart, and database collectors are configured in the Controller rather than migrated to the replacement agent. **Learn more:** [Upgrade the Database Agent — Splunk AppDynamics](https://help.splunk.com/en/appdynamics-on-premises/database-visibility/26.5.0/administer-the-database-agent/upgrade-the-database-agent)

Answer: B A custom TCP concurrent server uses a nonstandard communication protocol, so transaction context is not automatically propagated and correlated by the monitoring agent. Custom correlation must be configured to inject and retrieve the correlation data across that TCP-based interaction.