Cisco AppDynamics Professional Implementer 500-430 CAPI Exam Questions

Answer : D

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

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 : 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

Answer : A, C

The default configuration of the Mobile SDK enablescrash reportsandnetwork requests12.Crash reports capture and report any unhandled exceptions or signals that cause the app to terminate abnormally1.Network requests monitor the performance and errors of HTTP and HTTPS requests made by the app2.These features are enabled by default and do not require any additional code or configuration to work12.Reference:Crash Reports,Network Requests

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 : 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

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.