Free 500-430 Practice Test Questions and Answers (2026)

The AppDynamics REST API to retrieve metrics allows you to get values generated for metrics by

specifying the path of the metric and the time frame for the data1. Some of the valid reasons to use

this API are12:

To archive 1-minute granularity data. The AppDynamics Controller stores metric data at different

levels of granularity depending on the retention period. For example, it stores 1-minute granularity

data for 8 days, 10-minute granularity data for 32 days, and 1-hour granularity data for 365 days. If

you want to archive the 1-minute granularity data for longer than 8 days, you can use the API to

retrieve and store the data in an external database or file system.

To calculate a new metric based on two existing metrics. The AppDynamics Controller provides some

built-in metrics such as average response time, calls per minute, errors per minute, etc. However,

you may want to calculate a new metric that is not available in the Controller, such as the ratio of

errors to calls, or the percentage of slow transactions. You can use the API to retrieve the values of

the existing metrics and perform the calculation using your own logic or formula.

To retrieve health rule violations. Health rules are the rules that define the performance and

availability thresholds for your application components. When a health rule is violated, the

AppDynamics Controller generates an event and optionally triggers a policy action. You can use the

API to retrieve the list of health rule violations for a given application, time range, and severity level.

This can help you monitor and troubleshoot the health of your application and take corrective actions

if needed. Reference: Retrieve Metric Data, Health Rule API

The AppDynamics Rest API to retrieve business transactions allows you to get a list of all business

transactions in a business application, along with their key metrics and properties1. The correct URL

format for this API is1:

http(s)

://:/controller/rest/applications//business-

transactions

The other options are incorrect because12:

Option A uses an invalid endpoint /allbts, which does not exist in the API.

Option C uses an incorrect base URL /controller/applications, which is used for the Controller UI, not

the Rest API.

Option D uses a misspelled endpoint /allbis, which does not exist in the API. Reference: Retrieve All

Business Transactions in a Business Application, AppDynamics APIs

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.

Reference: Access the Administration Console, License Rules, Data Retention

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the minimum

recommended number of nodes for a redundant Events Service is three ©. The Events Service is a

distributed database that stores and processes the analytics data collected by the AppDynamics

platform. The Events Service cluster consists of multiple nodes that share the data load and provide

fault tolerance and high availability. The minimum number of nodes for a functional Events Service

cluster is one, but this is not recommended for production environments, as it does not provide any

redundancy or resilience. The minimum number of nodes for a redundant Events Service cluster is

three, as this allows the cluster to tolerate the failure of one node without losing any data or

availability. The recommended number of nodes for a redundant Events Service cluster is five or

more, as this provides better performance and scalability12.

The incorrect options are:

1 (A): This is not a valid option because a single-node Events Service cluster does not provide any

redundancy or resilience. If the node fails, the cluster becomes unavailable and the data is lost. A

single-node Events Service cluster is only suitable for testing or development purposes, not for

production environments12.

2 (B): This is not a valid option because a two-node Events Service cluster does not provide sufficient

redundancy or resilience. If one node fails, the cluster becomes unstable and may lose data or

availability. A two-node Events Service cluster is not recommended for production environments12.

4 (D): This is not a valid option because a four-node Events Service cluster is not optimal for

redundancy or resilience. A four-node Events Service cluster has an even number of nodes, which

may cause a split-brain scenario, where the cluster is divided into two equal partitions that cannot

communicate with each other. This may result in data inconsistency or unavailability. A four-node

Events Service cluster can be improved by adding a fifth node to avoid the split-brain scenario12.

Reference:

1: Events Service Deployment - AppDynamics

2: Events Service Requirements - AppDynamics

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two

symptoms that occur if an AppDynamics Controller is not scaled correctly are:

The Controller’s metric reporting is 7 to 10 minutes behind the current time. (D) This is a valid

symptom because the AppDynamics Controller collects, processes, and stores metrics from the

agents that monitor the applications, tiers, nodes, and other entities. If the Controller is not scaled

correctly, it may not have enough resources, such as CPU, memory, disk space, or network

bandwidth, to handle the incoming metrics data. This may result in a backlog of metrics data that

causes the Controller to lag behind the current time. The Controller’s metric reporting delay can

affect the accuracy and timeliness of the performance analysis and troubleshooting12.

The Controller UI performs slowly. (E) This is a valid symptom because the AppDynamics Controller

UI is a web-based application that allows users to access, visualize, and interact with the

performance data and configuration settings of the AppDynamics platform. If the Controller is not

scaled correctly, it may not have enough resources, such as CPU, memory, disk space, or network

bandwidth, to serve the UI requests. This may result in a slow or unresponsive UI that affects the

user experience and productivity12.

The incorrect options are:

Snapshots are not available after 2 weeks. (A) This is not a valid symptom because the AppDynamics

Controller does not store snapshots for more than 2 weeks by default. Snapshots are detailed records

of the execution context and call graphs of the business transactions that are monitored by the

AppDynamics platform. Snapshots are useful for diagnosing performance issues and errors, but they

also consume a lot of disk space. The AppDynamics Controller automatically purges the snapshots

that are older than 2 weeks, unless the retention policy is changed by the user. The availability of

snapshots is not affected by the Controller scaling, unless the disk space is exhausted34.

Health rule violations occur more frequently. (B) This is not a valid symptom because the

AppDynamics Controller does not cause health rule violations to occur more frequently. Health rule

violations are triggered when the performance or availability metrics of the monitored entities

exceed the thresholds that are defined by the user. Health rule violations indicate the presence of

performance issues or errors in the monitored applications, tiers, nodes, or other entities, not in the

Controller itself. The frequency of health rule violations is not affected by the Controller scaling,

unless the Controller fails to collect or process the metrics data5 .

The average response times of tiers are higher than normal. © This is not a valid symptom because

the AppDynamics Controller does not affect the average response times of tiers. The average

response time of a tier is the average time that the tier takes to process the incoming requests from

the business transactions that are monitored by the AppDynamics platform. The average response

time of a tier is influenced by the performance and behavior of the application code, the

infrastructure, the dependencies, and the workload of the tier, not by the Controller itself. The

average response time of a tier is not affected by the Controller scaling, unless the Controller fails to

collect or process the metrics data .

Reference:

1: Controller System Requirements - AppDynamics

2: Controller Sizing Guidelines - AppDynamics

3: Transaction Snapshots - AppDynamics

4: Configure Data Retention - AppDynamics

5: Health Rules - AppDynamics

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two

recommendations for servers in an Events Service Cluster are:

Should be on the same local network ©: This is a valid recommendation because the Events Service

Cluster is based on Apache Cassandra, which is a distributed database that relies on network

communication between the nodes. Having the servers on the same local network reduces the

network latency and improves the performance and reliability of the cluster. The network bandwidth

should be at least 1 Gbps, and the network firewall should allow the required ports for the Events

Service Cluster12.

Should have identical hardware specifications (D): This is a valid recommendation because the Events

Service Cluster is horizontally scalable, which means that the nodes share the data storage and

processing load equally. Having identical hardware specifications for the servers ensures that the

cluster is balanced and efficient, and avoids performance bottlenecks or failures due to hardware

differences. The hardware specifications should meet the minimum requirements for the Events

Service Cluster, such as CPU cores, RAM, disk space, and disk type12.

The incorrect options are:

Should be installed using the same user account (A): This is not a valid recommendation because the

Events Service Cluster does not require the same user account for installation. The user account that

is used to install the Events Service Cluster should have sudo privileges on the target hosts, but it

does not have to be the same for all the hosts. The user account that is used to run the Events

Service Cluster should have read and write permissions on the installation directory, but it does not

have to be the same for all the hosts either12.

Should have eight or more CPU cores (B): This is not a valid recommendation because the Events

Service Cluster does not require eight or more CPU cores for the servers. The minimum requirement

for the CPU cores is four, and the recommended requirement is six. Having more CPU cores may

improve the performance of the cluster, but it is not a mandatory recommendation12.

Should be running the same operating system version (E): This is not a valid recommendation

because the Events Service Cluster does not require the same operating system version for the

servers. The Events Service Cluster supports various Linux operating systems, such as CentOS, Red

Hat, Ubuntu, and SUSE. The operating system version should be compatible with the Events Service

version, but it does not have to be the same for all the hosts12.

Reference:

1: Events Service Requirements - AppDynamics

2: Events Service Deployment - AppDynamics

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. Reference: Controller System Requirements, Performance and Controller

sizing guidelines, How to Run AppDynamics in Microsoft Azure, Platform Requirements

The AppDynamics Controller properties that govern how long metric data is retained in the database

are1:

metrics.ten.min.retention.period: This property specifies the number of days to retain metric data at

10-minute granularity. The default value is 32 days.

metrics.retention.period: This property specifies the number of days to retain metric data at 1-hour

granularity. The default value is 365 days.

metrics.min.retention.period: This property specifies the number of hours to retain metric data at 1-

minute granularity. The default value is 4 hours.

The other options are incorrect because1:

metrics.ten.sec.retention.period: This property does not exist in the AppDynamics Controller. The

finest granularity for metric data is 1 minute.

metrics.day.retention.period: This property does not exist in the AppDynamics Controller. The

coarsest granularity for metric data is 1 hour.

metrics.week.retention.period: This property does not exist in the AppDynamics Controller. The

metric data retention is based on days, not weeks. Reference: Database Size and Data Retention

The EUM Server is the on-premises version of the EUM Cloud that receives, processes, and stores

data from EUM agents. For production installation, AppDynamics recommends that the EUM Server

and the Controller sit on different hosts, and the EUM Server hosts its own MySQL instance. This

improves the scalability and performance of both components. Moreover, AppDynamics strongly

recommends that SSL traffic from agents to the EUM Server is terminated at a reverse proxy that sits

in front of the EUM Server in the network path, and forwards connections to the EUM Server using

HTTP. This relieves the SSL processing load from the EUM Server, simplifies the certificate

management, and enhances the security by isolating the EUM Server from the external Internet.

Therefore, the best implementation mode for deploying an EUM Server with reverse proxy in a

production environment is option D. Reference: EUM Server Deployment, Install a Production EUM

Server, Reverse Proxy configuration for EUM, and Browser EUM installation in the AppDynamics

documentation and community.

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.

Reference: Platform

Requirements, Controller

System

Requirements, Controller

Disk

Space

Requirements, Controller Disk Space Alert, [High Availability], [High Availability Toolkit]