Cisco AppDynamics Professional Implementer 500-430 CAPI Exam Questions

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, E

To upgrade an EUM Server that is currently in production, the administrator should follow these steps:

Stop the EUM Server before the upgrade. This ensures that the EUM Server does not process any incoming data from the EUM agents during the upgrade process.The administrator can use theeum.shoreum.batscript to stop the EUM Server gracefully1.

Run the new installer on the EUM host machine. The installer will detect the existing EUM Server installation and prompt the administrator to upgrade it to the latest version. The installer will also migrate the EUM data from the old version to the new version, if needed.The administrator should follow the instructions on the installer wizard to complete the upgrade2.

The other options are not necessary or correct for upgrading the EUM Server. The administrator does not need to stop or upgrade the EUM agents, as they are compatible with the new version of the EUM Server. The administrator does not need to update the EUM Server access key, as it remains the same after the upgrade.The administrator does not need to install MySQL, as it is bundled with the EUM Server installation package2.Reference:Upgrade the Production EUM ServerandStart and Stop the EUM Serverin the AppDynamics documentation.

Answer : A, D, F

To prepare a Linux environment for the installation of an AppDynamics Controller with a Large performance profile, which is suitable for monitoring up to 1000 agents, you need to perform the following steps:

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 the open file descriptor limit on the system. The file descriptor limit determines how many files a process can open at a time. The Controller requires a high file descriptor limit to handle the large number of connections and transactions. AppDynamics recommends setting the file descriptor limit to at least 65535 for the user account that runs the Controller.You can check the current file descriptor limit by runningulimit -nand modify it by editing the/etc/security/limits.conffile2.

Verify the process limit on the system. The process limit determines how many processes a user can run at a time. The Controller requires a high process limit to handle the large number of threads and subprocesses. AppDynamics recommends setting the process limit to at least 65535 for the user account that runs the Controller.You can check the current process limit by runningulimit -uand modify it by editing the/etc/security/limits.conffile2.

Other steps that are not required but recommended for the Controller installation are verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the NUMA configuration2.You do not need to install MySQL or Java separately, as they are included in the Controller installation package3.Reference:Prepare Linux for the Controller,Install the Controller on Linux, andController System Requirementsin the AppDynamics documentation.

Answer : A

Custom correlation is needed when the default detection mechanisms of AppDynamics are not capable of auto-correlating transactions across tiers or across parent-child threads in complex multithreaded applications. Custom correlation enables the user to configure AppDynamics to propagate a unique correlation key by using the extension points of the distributed protocol or by decorating the payload. Among the four options, a custom TCP concurrent server is the most likely to require the implementation of custom correlation, as it is an unsupported framework and protocol that may not have easily-defined method calls or payload objects to configure as exit points or entry points. The other options, such as SOAP, JMS, and WCF, are supported by AppDynamics and can be automatically correlated by the agents without the need for custom configuration.Reference:Custom Correlation for Java ApplicationsandConfigure Custom Correlation for .NET Applicationsin the AppDynamics community.

Answer : D, E

The AppDynamics Controller Admin Console lets you configure certain global settings for the Controller, such as metric retention periods, UI notification triggers, tenancy mode, and accounts in multi-tenancy mode1. Two of the settings that an administrator can configure from the AppDynamics Controller Admin Console are:

License allocation: This setting allows you to view and manage the license usage and availability for your Controller. You can see the total number of licenses, the number of licenses in use, the number of licenses available, and the license expiration date for each agent type.You can also allocate licenses to specific applications or accounts, and set license limits and alerts2.

Retention periods: This setting allows you to specify how long the Controller retains the metric data and the event data for your monitored applications. You can configure the retention periods for different types of data, such as minute-level metrics, hour-level metrics, day-level metrics, transaction snapshots, and events.You can also configure the data purge schedule and the data backup schedule3.

Answer : D, E

AppDynamics performance profiles are predefined sets of system requirements and configuration settings that are designed to support different levels of load and scalability for the AppDynamics platform. The performance profiles range from small to extra large, depending on the number of agents, metrics, and events that the platform needs to handle. The large and extra large performance profiles differ from other profile types in the following ways:

They require an enterprise-grade database: The large and extra large performance profiles require an external MySQL database that is enterprise-grade, meaning that it has high availability, scalability, performance, and security features. The database should also have enough disk space, memory, and CPU resources to handle the expected load and growth.The AppDynamics platform uses the database to store configuration data, metric data, event data, and analytics data12.

An alert is generated when disk space falls below 2 GB: The large and extra large performance profiles have a built-in alert mechanism that notifies the administrator when the disk space on the Controller host falls below 2 GB. This is because the Controller needs enough disk space to store temporary files, logs, backups, and snapshots. If the disk space is insufficient, the Controller may experience performance degradation, data loss, or corruption.The administrator should monitor the disk space usage and free up space or add more disk capacity as needed34.

The other statements are false because:

A) They do not need to be installed on a bare metal server. The large and extra large performance profiles can be installed on any supported operating system, such as Linux or Windows, and on any supported platform, such as physical, virtual, or cloud.However, the host machine should have enough CPU, memory, and network resources to meet the performance profile requirements12.

B) They do not need to be run with the High Availability Toolkit. The High Availability Toolkit is an optional tool that can be used to configure and manage a high availability deployment of the AppDynamics platform, where multiple Controllers are clustered together to provide redundancy and failover. The High Availability Toolkit can be used with any performance profile, not just the large and extra large ones. However, the High Availability Toolkit requires a license and additional hardware and software resources .

C) They are supported on Windows. The large and extra large performance profiles can be installed on Windows Server 2012, 2012 R2, 2016, or 2019, as long as the host machine meets the performance profile requirements.However, some features or configurations may not be available or supported on Windows, such as the High Availability Toolkit, the Enterprise Console, or the Events Service12.

Answer : A, D, F

To set up AppDynamics Controllers as a high availability pair, you need to meet the following requirements1:

Passwordless SSH must be configured between the two Controller servers. This allows the Enterprise Console to automate the configuration and administration tasks associated with a highly available deployment on Linux systems.

Both servers must have the Controller software installed prior to setting up high availability. The Controllers in an HA pair must be equivalent versions, and be in the same data center.

Both servers must have identical directory structures for the Controller installation. The individual machines in the Controller HA pair need to have an equivalent amount of disk space.Reference:Prerequisites for High Availability