MENU
Which three things should a Performance Analyst verify to validate a Java Agent's configuration? (Choose three.)
To validate a Java Agent configuration, the Performance Analyst should inspect the startup script, controller-info.xml, and relevant environment variables.
The startup script must contain the correct -javaagent argument pointing to the Java Agent JAR. It may also define Java system properties for the Controller host, port, SSL setting, application name, tier name, node name, account credentials, and other agent parameters. Incorrect paths or conflicting -Dappdynamics.* values can prevent registration or cause the agent to report under the wrong entity.
The controller-info.xml file is the Java Agent's primary configuration file. The analyst should verify Controller connectivity settings, account details, access key, application identity, tier identity, node identity, and SSL configuration.
Environment variables must also be reviewed because containerized and automated deployments commonly provide AppDynamics settings through variables. These values may override or supplement file-based configuration and can explain unexpected registration behavior.
/etc/sysctl.conf contains operating-system kernel parameters and is not a Java Agent configuration source. controller-info.yaml is not the standard Java Agent configuration file.
Relevant CAAPA topics include Java Agent Installation, Agent Registration, Controller Connectivity, controller-info.xml, Java System Properties, Environment Variables, and Application--Tier--Node Naming.