Verified 500-430 Exam Dumps PDF [2024] Access using TrainingQuiz [Q28-Q49]

Explanation
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. References: Database Size and Data Retention

Explanation
The AppDynamics Rest API allows you to retrieve information and perform operations on the AppDynamics platform using HTTP requests. To retrieve all AppDynamics business applications from an AppDynamics Controller using the AppDynamics Rest API, you need to use the following URL format:
http(s)://<controller-host>:<port>/controller/rest/applications
This URL returns the business application names and internal numeric identifiers for all the applications that are monitored by the Controller. You can use the application name or ID as a parameter for other API methods that require the application context. You can also specify the output format as XML (default) or JSON by adding the output query parameter. For example:
http(s)://<controller-host>:<port>/controller/rest/applications?output=JSON This URL returns the same information as the previous one, but in JSON format. You can also filter the applications by their status (alive or not) by adding the time-range-type query parameter. For example:
http(s)://<controller-host>:<port>/controller/rest/applications?time-range-type=BEFORE_NOW&duration-in-mi This URL returns only the applications that are alive in the last 60 minutes. An alive application is an application with at least one node that submits at least one metric to the Controller in the provided time range12. References: Application Model API, Metric and Snapshot API

Explanation
The AppDynamics standalone Machine Agent is a Java program that runs on a host machine and collects hardware and infrastructure metrics, such as CPU, memory, disk, and network usage. The Machine Agent can also perform additional functions, such as:
Acting as a forwarder for analytics events: The Machine Agent can be configured to forward business transaction, log, browser, mobile, and synthetic events from the application agents to the AppDynamics Events Service, which is a distributed, scalable data store for analytics data. The Machine Agent can also forward custom events from the SDK or API to the Events Service. This allows you to use the AppDynamics Analytics features, such as dashboards, queries, funnels, and metrics, to analyze the performance and behavior of your applications and users12.
Starting an HTTP listener for custom metrics: The Machine Agent can be configured to start an HTTP listener that can receive custom metrics from external sources, such as scripts, tools, or other applications. The Machine Agent can then report these custom metrics to the AppDynamics Controller, where youcan view them in the Metric Browser or use them in health rules, policies, or dashboards. This allows you to monitor any aspect of your system that is not covered by the default Machine Agent metrics34.
The other statements are false because:
B: The Machine Agent cannot send SNMP alerts. The Machine Agent can only receive SNMP traps from external sources and report them as events to the AppDynamics Controller. The AppDynamics Controller can send SNMP alerts to external systems based on health rule violations or events, but this is not a function of the Machine Agent5 .
C: The Machine Agent cannot communicate with multiple AppDynamics Controllers. The Machine Agent can only communicate with one Controller at a time, which is specified in the controller-info.xml file in the agent configuration directory. If you want to monitor the same host machine with multiple Controllers, you need to install multiple Machine Agents on the same machine, each with a different Controller configuration and port number .
D: The Machine Agent cannot restart itself if it goes down. The Machine Agent does not have a built-in mechanism to automatically restart itself in case of a failure or a crash. You need to use an external tool or script to monitor the Machine Agent process and restart it if necessary. Alternatively, you can use the AppDynamics Agent Installer to deploy the Machine Agent as a service, which can be configured to restart automatically on failure .
References: Analytics Agent, Analytics Data, HTTP Listener, Custom Metrics, SNMP Trap Alerting Integration, [SNMP Integration], [Machine Agent Configuration Properties], [Install the Machine Agent],
[Agent Installer], [Start and Stop the Machine Agent]

Explanation
AppDynamics can collect sensitive data such as credit card numbers from various sources, such as SQL queries, error messages, HTTP headers, cookies, and so on. To protect this data from unauthorized access or exposure, an administrator should configure the user permissions for the following features:
SQL Bind Variables: This feature enables the agents to capture the values of the parameters that are passed to SQL queries. These values can contain sensitive data such as credit card numbers, passwords, or personal information. To prevent this data from being stored or displayed in the Controller UI, the administrator should disable the Capture SQL Bind Values permission for the users who do not need to see this data. Alternatively, the administrator can enable the Mask SQL Bind Values permission, which replaces the values with asterisks (*) in the UI. The administrator can also configure the agent properties to exclude or mask certain bind variables based on patterns or keywords1.
Diagnostic Data Collectors: This feature enables the agents to collect additional data from the application code, such as method arguments, return values, HTTP headers, cookies, and so on. These data can also contain sensitive information that should not be exposed to unauthorized users. To control the access to this data, the administrator should disable the View Diagnostic Data Collectors permission for the users who do not need to see this data. The administrator can also configure the agent properties to exclude or mask certain data collectors based on patterns or keywords2.
Other features that can collect sensitive data and require user permissions are Error Detection, Memory Monitoring, and Policies. However, these features are less likely to capture credit card numbers than SQL Bind Variables and Diagnostic Data Collectors. Therefore, the best answer is option C and E. References: Sensitive Data Collection and Security, SQL Bind Variables, and Diagnostic Data Collectors in the AppDynamics documentation.

Explanation
A custom action is a type of Alert and Respond action that allows you to integrate AppDynamics notifications with your own alerting or ticketing system. You can create a custom action by writing an executable script and an XML file that describe how to pass information from AppDynamics to your system. A custom action can be triggered by a policy based on a health rule violation or an event. A custom action is available only on an on-premises Controller, because it requires access to the Controller file system and the ability to execute scripts on the Controller host machine. For a SaaS Controller, you can use HTTP request templates instead of custom actions to integrate with external systems. References: Build a Custom Action, Alert and Respond, Actions, Custom Actions

Explanation
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.
References: Access the Administration Console, License Rules, Data Retention

Explanation
The <eum_server_home> directory contains the EUM Server installation files, configuration files, and data files. It is recommended to back up this directory as a precaution before upgrading or migrating the EUM Server. The default location of this directory is <installDir>/AppDynamics/EUM, where <installDir> is the directory where you installed the Controller. You can also use the backup-eum.sh script to back up the EUM Server data12. References: Upgrade the Production EUM Server, Configure the EUM Server

Explanation
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. References: Controller Port Settings, Configure the Port for the EUM Agent, Access the Administration Console, Controller System Requirements

Explanation
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.
References:
1: Events Service Requirements – AppDynamics
2: Events Service Deployment – AppDynamics

Explanation
As an AppDynamics Controller grows beyond supporting 500 agents, network throughput becomes more important. This is because the Controller needs to handle a large volume of data from the agents, as well as serve requests from the UI and API clients. Network throughput is the measure of how much data can be transferred over a network in a given time. A low network throughput can cause delays, errors, or timeouts in the communication between the Controller and the agents or clients. Therefore, it is recommended to monitor the network throughput of the Controller and ensure that it meets the minimum requirements for the expected load123. References: Controller System Requirements, Performance and Controller Sizing Guidelines, How to Run AppDynamics in Microsoft Azure

Explanation
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons that would require an administrator to install the Events Service cluster manually are:
Security concerns with passwordless SSH (B): This is a valid reason because the automated installation of the Events Service cluster requires passwordless SSH access to the target hosts. Passwordless SSH allows the Enterprise Console to execute commands on the remote hosts without prompting for a password. However, some organizations may have security policies that prohibit passwordless SSH access, as it may pose a risk of unauthorized access or malicious attacks. In such cases, the administrator can install the Events Service cluster manually, by following the steps described in the Manual Installation of the Events Service Cluster document1.
Security requirements to install using a non-root user account : This is a valid reason because the automated installation of the Events Service cluster requires root privileges on the target hosts. Root privileges allow the Enterprise Console to create directories, change permissions, and install packages on the remote hosts. However, some organizations may have security policies that restrict root access, as it may pose a risk of accidental or intentional damage to the system. In such cases, the administrator can install the Events Service cluster manually, by following the steps described in the Manual Installation of the Events Service Cluster document1. The administrator can use a non-root user account that has sudo privileges to perform the manual installation.
The incorrect options are:
Installation on SUSE Linux (A): This is not a valid reason for manual installation, because the automated installation of the Events Service cluster supports SUSE Linux as one of the compatible operating systems. The Enterprise Console can install the Events Service cluster on SUSE Linux hosts using the automated installation process, as long as the hosts meet the prerequisites described in the Events Service Requirements document2.
Installation on Windows (D): This is not a valid reason for manual installation, because the Events Service cluster does not support Windows as an operating system. The Events Service cluster can only run on Linux hosts, as it is based on Apache Cassandra, which is a Linux-based distributed database. The Events Service cluster cannot be installed on Windows hosts, either manually or automatically2.
References:
1: Manual Installation of the Events Service Cluster – AppDynamics
2: Events Service Requirements – AppDynamics

Explanation
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

Explanation
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 .
References:
1: Controller System Requirements – AppDynamics
2: Controller Sizing Guidelines – AppDynamics
3: Transaction Snapshots – AppDynamics
4: Configure Data Retention – AppDynamics
5: Health Rules – AppDynamics

Explanation
AppDynamics recommends that you terminate SSL connections from agents at a reverse proxy or a load balancer in front of the Controller, rather than at the Controller itself. This improves the performance and scalability of the Controller by offloading the SSL processing to the proxy or load balancer. It also simplifies the configuration and management of SSL certificates and truststores. To enable this option, you need to configure the proxy or load balancer to accept SSL connections from agents and forward them to the Controller using HTTP. You also need to configure the agents to use SSL and point to the proxy or load balancer host and port. See Enable SSL for the Java Agent for an example. References: Agent-to-Controller Connections and Enable SSL and SSH for Database Agent Communications in the AppDynamics documentation.

Explanation
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.

Explanation
The Database Agent collects hardware metrics from a Windows database server using PowerShell
1. 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

Explanation
The AppDynamics REST API for retrieving metrics allows you to get values generated for metrics by specifying the path of the metric and the time frame for the data1. The following statements are true regarding this API12:
Metrics can be retrieved for a fixed time range. You can use the time-range-type parameter to specify a fixed time range such as BEFORE_NOW, AFTER_TIME, or BETWEEN_TIMES. You can also use the duration-in-mins parameter to specify the length of the time range in minutes.
Wildcards can be used in the REST API metric path. You can use the asterisk () character as a wildcard to match any metric name or part of a metric name. For example, you can use the metric path Business Transaction Performance|Business Transactions||*|Average Response Time (ms) to retrieve the average response time for all business transactions in all tiers. References: Retrieve Metric Data, Retrieve Metric Hierarchy

Explanation
The user under which the JVM runs must have write privileges to the conf and logs directories in the Java Agent home. This is because the conf directory contains the agent configuration files, such as controller-info.xml and agent-config.xml, which may need to be modified or updated by the user. The logs directory contains the agent log files, such as agent.log and agent-errors.log, which are generated by the agent and may need to be accessed or rotated by the user. The user can install the agent as the same user that owns the JVM or as an administrator on the host machine. The user can restrict the remaining contents of the agent directory, such as the lib and bin directories, to read-only access12. References: Install the Java Agent, Java Agent fails to start

Explanation
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 run yum 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 running df -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.tmpdir parameter 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. References: Prepare Linux for the Controller, Install the Controller on Linux, and [Controller System Requirements] in the AppDynamics documentation.