Cisco 500-430 Cisco AppDynamics Professional Implementer CAPI Exam Practice Test

Answer : B

The Events Service is the on-premises data storage facility for unstructured data generated by Application Analytics, Database Visibility, and End User Monitoring deployments. The Events Service can be deployed as a single node or a cluster of three or more nodes, depending on the data volume and availability requirements. The Controller and other Events Service clients connect to the Events Service to store and retrieve analytics data. Therefore, it is essential that the Controller is able to initiate communication with the Events Service cluster, using the Events Service API ports (default 9080/2081). The Events Service cluster does not need to initiate communication with the Controller, as it only responds to the requests from the clients. The Events Service API ports can be reconfigured from the default values, if needed, by modifying theconf/events-service-api-store.propertiesfile on each node. However, the clients must also be updated with the new port values. It is also recommended to use a load balancer or a virtual IP address in front of the Events Service cluster, to provide a single endpoint for the clients and to enable load balancing and failover among the nodes.Reference:Events Service Deployment,Install the Events Service on Linux, andInstall the Events Service on Windowsin the AppDynamics documentation.

Answer : B, C

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.

Answer : A

The <eum_server_home> directory contains the EUM Server installation files, configuration files, and data files. It is recommended to back up this directory as a precaution before upgrading or migrating the EUM Server. The default location of this directory is <installDir>/AppDynamics/EUM, where <installDir> is the directory where you installed the Controller.You can also use the backup-eum.sh script to back up the EUM Server data12.Reference:Upgrade the Production EUM Server,Configure the EUM Server

Answer : A

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the correct method to perform a NET Agent upgrade is to perform the agent upgrade on the application server host by running the MSI Installer Package12. This method will install updated agent files and maintain legacy configurations. You do not need to uninstall the old agent first when you upgrade from the NET Agent >= 3.9, except for patch releases. You need to stop IIS, instrumented Windows services, and instrumented standalone applications before running the MSI Installer Package. You also need to launch an elevated command prompt with full administrator privileges and specify your account access key for single-tenant Controller accounts. After the installation, you need to restart Windows services and standalone applications.

The incorrect options are:

Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API. (B) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller REST API does not provide any endpoint for agent installation or upgrade.The REST API is mainly used for retrieving or updating configuration data, metrics, events, snapshots, and other information from the Controller3.

Perform the agent upgrade on the application server host by running the Agent Configuration Utility. This is not a valid method for upgrading the NET Agent, because the Agent Configuration Utility is a tool for modifying the agent configuration after installation, not for installing or upgrading the agent.The Agent Configuration Utility allows you to change the Controller connection settings, the agent logging level, the proxy settings, and other advanced options4.

Perform the agent upgrade via the AppDynamics Controller UI. (D) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller UI does not provide any feature for agent installation or upgrade.The Controller UI is mainly used for monitoring, analyzing, and troubleshooting the performance of the applications, business transactions, tiers, nodes, and other entities that are instrumented by the agents5.

1: Upgrade the .NET Agent for Windows - AppDynamics

2: Release Upgrade Checklist for .NET Agents - AppDynamics

3: REST API - AppDynamics

4: Configure the .NET Agent - AppDynamics

5: AppDynamics Application Performance Monitoring Platform - AppDynamics

Answer : C

The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent that monitors the performance and health of the Controller itself1.To access the information provided by the internal agent, you need to log in to the Controller UI with the following credentials2:

Account = system

Username = root

Password = <root_user_password>

The system account is a special account that is used only for internal monitoring and troubleshooting purposes.It is not visible in the normal Controller UI and requires a special URL to access it2.The root user is the default administrator user for the system account and has the same password as the admin user for the customer1 account3.Reference:Controller Self-Monitoring,Monitoring a Controller Using the Internal Monitoring Agent,Controller Accounts

Answer : D, E

Before installing an AppDynamics Controller on Linux, you need to perform some preparatory tasks to ensure the system meets the requirements and the installation runs smoothly. Two of these tasks are:

Install libaio on the host machine if it does not already have it installed. This library facilitates asynchronous I/O operations on the system, which are required by the Controller. You can use the package manager of your Linux distribution to install libaio, such as yum or apt-get.For example, on CentOS, you can runyum install libaio1.

Verify that you have enough temporary (tmp) space available on the system, at least 1 GB. The Controller installation uses the tmp space to extract and install the software components.You can check the tmp space by runningdf -h /tmp2.If the tmp space is insufficient, you can either free up some space by deleting unnecessary files, or specify a different temporary directory for the installation by passing the-Djava.io.tmpdirparameter to the installer3.

Other preparatory tasks include verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the file descriptor limit2.Reference:Prepare Linux for the Controller,Install the Controller on Linux, and [Controller System Requirements] in the AppDynamics documentation.

Answer : D

In a split-host configuration, where the EUM Server and Controller are on separate hosts, the EUM Server requires access to the Controller primary HTTP(s) port. This is because the EUM Server needs to communicate with the Controller API server to send data and receive configuration information.The default primary HTTP port for the Controller is 8090 and the default primary HTTPS port is 81811.The dedicated EUM HTTP(s) ports are used by the EUM agents to send data to the EUM Server, not by the EUM Server to access the Controller2.The GlassFish administration port is used to access the Controller Admin Console, not by the EUM Server3.The Controller database port is used by the Controller to connect to the MySQL database, not by the EUM Server4.Reference:Controller Port Settings,Configure the Port for the EUM Agent,Access the Administration Console,Controller System Requirements