Free Practice Questions for Cisco 500-430 Exam

The most important factor in determining sizing for AppDynamics Controller is the projected metric load per minute on the Controller. This is because the metric load represents the actual workload on the Controller, which depends on the nature of the application, the AppDynamics configuration, and the usage patterns. The number of agents, the type of agents, the number of administrators/end users, and the number of AppDynamics applications are only rough estimates that can vary greatly depending on the specific scenario. Therefore, it is recommended to test the performance of the system in a staging environment and verify the Controller sizing using the metric upload rate before deploying to production. References: Controller System Requirements, Performance and Controller sizing guidelines, How to Run AppDynamics in Microsoft Azure, Platform Requirements

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. References: Prerequisites for High Availability

The AppDynamics .NET Agent can instrument both 32-bit and 64-bit processes, as long as they are running on a supported .NET Framework version and operating system. The agent automatically detects the process architecture and loads the appropriate profiler DLL. You can also specify the process architecture manually in the agent configuration file1. The AppDynamics .NET Agent also supports instrumentation of multiple instances of the same application, such as Windows services or standalone applications. You can configure the agent to assign different tier and node names for each instance, based on the process name, process ID, or command line arguments. This allows you to monitor the performance and health of each instance separately2.

The other statements are false because:

A. AppDynamics .NET Agent does support instrumenting processes running multiple App domains. The agent can monitor multiple App domains within a single process, as long as they are running the same .NET Framework version. The agent can also monitor multiple applications within a single App domain, by using the Standalone Applications element in the agent configuration file3.

B. AppDynamics .NET Agent does not automatically discover all the Windows services to be instrumented. The agent automatically instruments IIS applications only. For Windows services or standalone applications, you need to manually configure the agent by editing the agent configuration file and adding the Windows Services or Standalone Applications element. You also need to provide the executable name, tier name, and node name for each service or application4.

D. AppDynamics .NET Agent does not require that the Windows services are running under the “App.pool identity user” account. The agent can instrument Windows services running under any user account, as long as the account has sufficient permissions to load the agent profiler DLL and access the agent configuration and log files. The “App.pool identity user” account is only required for IIS applications that run in an application pool5.

References: .NET Agent Configuration Properties, Configure the .NET Agent for Windows Services and Standalone Applications, Instrument the DefaultDomain for Standalone Applications, Install the .NET Agent for Windows, Administer the .NET Agent

To install a .NET Agent patch, which is a minor update to the existing .NET Agent version, you do not need to uninstall the old agent or restart the machine. You only need to follow these steps:

Download the .NET Agent patch from the AppDynamics Download Center.

Launch an elevated command prompt with full administrator privileges.

Execute the Installer.bat file from the patch archive. The batch file installs the patch and starts the AppDynamics Agent Coordinator service.

Restart the instrumented applications, such as IIS, Windows services, or standalone applications.

References: .NET Agent and How do I deploy a .NET Agent? in the AppDynamics documentation and community.

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

The Database Agent collects hardware metrics from a Windows database server using PowerShell1. PowerShell is a scripting language and a command-line shell that allows the Database Agent to execute commands and access Windows Performance Counters on the target host12. The Database Agent uses PowerShell to collect metrics such as CPU, memory, disk, and network utilization from the Windows database server1. To enable hardware monitoring for a Windows database server, the Database Agent requires the following permissions1:

The user that runs the Database Agent must have permission to execute PowerShell scripts on the local machine.

The user that runs the Database Agent or the Collector Service user (if using Windows Authentication) must have permission to establish a WMI connection to the target host and collect Windows Performance Counters. References: Required Monitored Host Permissions, PowerShell Overview

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 the eum.sh or eum.bat script 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. References: Upgrade the Production EUM Server and Start and Stop the EUM Server in the AppDynamics documentation.

The Machine Agent REST API allows you to create custom events that can be used for various purposes in AppDynamics. Some of the reasons you would create custom events using this API are12:

To create an event to track application deployment. You can use the API to send a custom event that marks the start and end of an application deployment process. This can help you monitor the impact of the deployment on the application performance and availability, as well as correlate any issues or anomalies with the deployment event.

To create an event to be displayed along with Time Series data in a custom dashboard. You can use the API to send a custom event that contains any relevant information or context that you want to display in a custom dashboard. For example, you can send a custom event that contains the details of a configuration change, a maintenance window, a business transaction, or a user action. You can then use the custom dashboard to visualize the custom event data along with the Time Series data for the metrics you are interested in.

To create an event to be used to trigger a health rule violation. You can use the API to send a custom event that contains a metric value that you want to use as a condition for a health rule. For example, you can send a custom event that contains the CPU utilization of a machine, and then create a health rule that evaluates the CPU utilization metric and triggers a violation if it exceeds a certain threshold. You can then use the health rule violation to generate alerts, notifications, or remediation actions. References: Machine Agent HTTP Listener, Create Custom Events

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 =

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. References: Controller Self-Monitoring, Monitoring a Controller Using the Internal Monitoring Agent, Controller Accounts