Cisco 500-430 - Cisco AppDynamics Professional Implementer(CAPI)
Which two choices are available when specifying an application in a URL string for the Health Rule REST API? (Choose two.)
Application Alias
Application ID
Application GUID
Application Name
Application REGEX
The Answer Is:
B, DExplanation:
The Health Rule REST API allows you to create, configure, update, and delete health rules for multiple applications simultaneously. To use this API, you need to specify the application in the URL string. You can use either the application ID or the application name for this purpose. The application ID is a unique numeric identifier for each application in the Controller. The application name is the display name of the application in the AppDynamics UI. You cannot use the application alias, GUID, or REGEX for the Health Rule REST API. References: Health Rule API and Retrieve All Business Applications in the AppDynamics documentation.
Which two user accounts are created by the AppDynamies Controller during installation? (Choose two.)
Elastic search root user
GlassFish asadmin user
Customer-specified Controller administrator account
OS user that will run the controller
REST API user
MySQL appd admin user
The Answer Is:
B, CExplanation:
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 is admin and the default password is appdynamics. You can change the password for this user after the installation by using the asadmin command-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. References: Controller Installation, Manage Users and Groups, and Update the Root User and Glassfish Admin Passwords in the AppDynamics documentation.
What are two ways in which large and extra large performance profiles differ from other profile types? (Choose two.)
They must be installed on a bare metal server.
They must be run with the High Availability Toolkit.
They are not supported on Windows.
They require an enterprise-grade database.
An alert is generated when disk space falls below 2 GB.
The Answer Is:
D, EExplanation:
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 isbecause 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.
References: Platform Requirements, Controller System Requirements, Controller Disk Space Requirements, Controller Disk Space Alert, [High Availability], [High Availability Toolkit]
Which two statements are true when updating the Database Agent? (Choose two.)
The Database Agent must be stopped and restarted during the upgrade.
If the agent is moved to a new location during the upgrade, the AppDynamics Controller must be reconfigured to reference the new location of the agent.
All data collectors created from the previous agent must be migrated to the new agent.
Controller-info.xml is the only file that needs to be migrated from the previous agent to the new agent.
After the Database Agent is upgraded, the AppDynamics Controller must be restarted.
The Answer Is:
A, DExplanation:
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, when updating the Database Agent, you need to follow these steps12:
Stop the agent as described for your specific installation in Start and Stop the Database Agent.
Make a copy of the existing agent directory,
Install the Database Agent as described for your specific installation in Administer the Database Agent.
Copy the
Start the new agent. See Start and Stop the Database Agent.
Verify the Database Agent Installation. See Verify the Database Agent Installation.
Therefore, the correct statements are:
The Database Agent must be stopped and restarted during the upgrade. (A)
Controller-info.xml is the only file that needs to be migrated from the previous agent to the new agent. (D)
The incorrect statements are:
If the agent is moved to a new location during the upgrade, the AppDynamics Controller must be reconfigured to reference the new location of the agent. (B) This is not true because the controller-info.xml file contains the information about the Controller host, port, account name, access key, and SSL settings. As long as this file is copied to the new agent location, the Controller does not need to be reconfigured.
All data collectors created from the previous agent must be migrated to the new agent. © This is not true because the data collectors are configured on the Controller UI, not on the agent. The agent collects the metrics from the databases and sends them to the Controller. The data collectors do not need to be migrated to the new agent.
After the Database Agent is upgraded, the AppDynamics Controller must be restarted. (E) This is not true because the Controller does not depend on the agent version. The agent and the Controller are compatible as long as they meet the Agent and Controller Compatibility requirements.
References:
1: Upgrade the Database Agent - AppDynamics
2: Release Upgrade Checklist for Database Agents - AppDynamics
What are two valid reasons for using the REST API to retrieve health rule violations? (Choose two.)
For updating an AppDynamics dashboard
For determining which actions have been executed
When searching for historical events
For sending emails
When pushing events to the Event Management System is NOT possible
The Answer Is:
B, CExplanation:
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the REST API for health rule violations allows you to retrieve information about the health rule violations that occurred in a specified time range for a given application1. You can use the REST API for health rule violations for the following valid reasons:
For determining which actions have been executed (B): The REST API response includes the details of the actions that were triggered by the health rule violation, such as email, SMS, HTTP request, or custom action1. You can use this information to verify if the actions were executed successfully, or to troubleshoot any issues with the action execution.
When searching for historical events ©: The REST API allows you to specify a custom time range for retrieving the health rule violations, such as BEFORE_TIME, AFTER_TIME, BETWEEN_TIMES, or BEFORE_NOW1. You can use this feature to search for historical events that occurred in the past, or to analyze the trends and patterns of the health rule violations over time.
The incorrect options are:
For updating an AppDynamics dashboard (A): This is not a valid reason for using the REST API for health rule violations, because the AppDynamics dashboards already display the health rule violations that occurred in the selected time frame, along with the severity, status, affected entities, and actions2. You do not need to use the REST API to update the dashboard, as the dashboard is automatically refreshed with the latest data from the Controller.
For sending emails (D): This is not a valid reason for using the REST API for health rule violations, because the REST API does not send emails directly. The REST API only returns the information about the health rule violations, and the actions that were triggered by them. If you want to send emails based on the health rule violations, you need to configure an email action in the health rule configuration, or use a custom action that invokes an external email service3.
When pushing events to the Event Management System is NOT possible (E): This is not a valid reason for using the REST API for health rule violations, because the REST API does not push events to the Event Management System. The REST API only returns the information about the health rule violations, and the actions that were triggered by them. If you want to push events to the Event Management System, you need to configure an HTTP request action in the health rule configuration, or use a custom action that invokes an external API3.
References:
1: Health Rule Violations API - AppDynamics
2: Health Rule Violations - AppDynamics
3: Actions - AppDynamics
