Free Cisco 500-430 Exam Practice Questions & Explanations

The AppDynamics Controller is a Java web application that runs on a GlassFish application server and uses a MySQL database. During the installation of the Controller, two user accounts are created by default:

The GlassFish asadmin user is the administrative user for the GlassFish server. This user has the authority to start, stop, and configure the GlassFish server and its domains. The default username for this user isadminand the default password isappdynamics.You can change the password for this user after the installation by using theasadmincommand-line tool1.

The customer-specified Controller administrator account is the user account that you provide during the installation wizard. This is the account that you use to access the AppDynamics User Interface (UI) for the first time and perform various tasks such as creating applications, configuring agents, managing users and groups, and so on. You can choose any username and password for this account, but AppDynamics recommends using only ASCII characters.You can also create additional user accounts in the Controller UI after the installation2.

The other options are not user accounts that are created by the Controller installation. The Elastic search root user, the REST API user, and the MySQL appd admin user are user accounts that are used internally by the Controller components and are not exposed to the end user.The OS user that will run the controller is a user account that you need to create on the host machine before the installation, and it is not created by the Controller installation3.Reference:Controller Installation,Manage Users and Groups, andUpdate the Root User and Glassfish Admin Passwordsin the AppDynamics documentation.

The AppDynamics Rest API allows you to retrieve information and perform operations on the AppDynamics platform using HTTP requests. To retrieve all AppDynamics business applications from an AppDynamics Controller using the AppDynamics Rest API, you need to use the following URL format:

http(s)://<controller-host>:/controller/rest/applications

This URL returns the business application names and internal numeric identifiers for all the applications that are monitored by the Controller. You can use the application name or ID as a parameter for other API methods that require the application context. You can also specify the output format as XML (default) or JSON by adding the output query parameter. For example:

http(s)://<controller-host>:/controller/rest/applications?output=JSON

This URL returns the same information as the previous one, but in JSON format. You can also filter the applications by their status (alive or not) by adding the time-range-type query parameter. For example:

http(s)://<controller-host>:/controller/rest/applications?time-range-type=BEFORE_NOW&duration-in-mins=60

This URL returns only the applications that are alive in the last 60 minutes.An alive application is an application with at least one node that submits at least one metric to the Controller in the provided time range12.Reference:Application Model API,Metric and Snapshot API

The EUM agent is a special agent that runs in web, mobile, or IoT applications and collects metrics on the end user experience.The EUM agent communicates with the EUM Collector, which is a component that verifies, aggregates, and packages the raw metrics sent by the EUM agent12.The EUM Collector can be either a SaaS service provided by AppDynamics or an on-premises server installed by the customer12.The EUM Collector then sends the processed metrics to the AppDynamics Controller and the Events Service for storage, analysis, and visualization12.Reference:Overview of End User Monitoring,EUM Data

To upgrade the AppDynamics Java Agent, you need to copy the existing agent directory to a backup location and replace it with the new agent directory. You also need to copy any configuration file changes made in the old directory to the new agent directory. After that, you need to restart the application JVM where the Java Agent is installed, so that the new agent can take effect. Restarting the application JVM is the only required step for the upgrade to succeed.You do not need to restart the host machine, the Machine Agent, or the AppDynamics Controller12.Reference:Upgrade the Java Agent,Release Upgrade Checklist for Java Agents

A custom action is a type of Alert and Respond action that allows you to integrate AppDynamics notifications with your own alerting or ticketing system. You can create a custom action by writing an executable script and an XML file that describe how to pass information from AppDynamics to your system. A custom action can be triggered by a policy based on a health rule violation or an event. A custom action is available only on an on-premises Controller, because it requires access to the Controller file system and the ability to execute scripts on the Controller host machine.For a SaaS Controller, you can use HTTP request templates instead of custom actions to integrate with external systems.Reference:Build a Custom Action,Alert and Respond,Actions,Custom Actions