500-430 Question #45: Real Exam Question with Answer & Explanation

Question

Options

• AUse the modifyJvmOptions utility provided by AppDynamics.
• BDefine JVM options on the Controller Settings page of the Enterprise Console.
• CPass JVM options to the Controller via java -javaagent:"options jar".
• DUse the controller.sh script provided by AppDynamics.
• EDefine JVM options manually in the domain. xmi file.

Explanation

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two methods that are available to define JVM options for an AppDynamics Controller so that the JVM options are retained across upgrades of the Controller are: Use the modifyJvmOptions utility provided by AppDynamics. (A) This is a valid method because the modifyJvmOptions utility is a script that allows you to add, remove, or list the JVM options for the Controller without manually editing any files. The utility also validates the syntax and format of the JVM options and creates a backup of the original configuration. The utility is located in the <controller_home>/bin directory and can be run on Linux or Windows platforms. The utility updates the <controller_home>/appserver/glassfish/domains/domain1/config/domain.xml file with the specified JVM options, which are preserved during the Controller upgrade. Define JVM options on the Controller Settings page of the Enterprise Console. (B) This is a valid method because the Controller Settings page of the Enterprise Console is a graphical user interface that allows you to configure various settings for the Controller, including the JVM options. The Enterprise Console is a web-based application that provides a centralized way to manage the AppDynamics platform components, such as the Controller, the Events Service, and the EUM Server. The Enterprise Console also handles the Controller upgrade process and preserves the JVM options that are defined on the Controller Settings page.

No community discussion yet for this question.