New (2024) Download free 500-430 PDF for Cisco Practice Tests
100% Free 500-430 Files For passing the exam Quickly
The Cisco AppDynamics Professional Implementer certification validates the candidate’s skills and knowledge in AppDynamics software solutions, which are widely used by organizations to monitor and manage their applications. It demonstrates their ability to design, deploy, and troubleshoot AppDynamics solutions, which is a valuable asset for any organization looking to improve their application performance. Furthermore, Cisco’s reputation as a leading provider of IT solutions makes this certification highly regarded in the industry.
NEW QUESTION # 16
Which three AppDynamics Controller properties govern how long metric data is retained in the database?
(Choose three.)
- A. metrics.ten.sec.retention.period
- B. metrics.ten.min.retention.period
- C. metrics. day retention period
- D. metrics.retention.period
- E. metrics.min.retention. period
- F. metrics week retention period
Answer: B,D,E
Explanation:
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
NEW QUESTION # 17
Which two choices are available when specifying an application in a URL string for the Health Rule REST API? (Choose two.)
- A. Application GUID
- B. Application ID
- C. Application REGEX
- D. Application Alias
- E. Application Name
Answer: B,E
Explanation:
Explanation
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.
NEW QUESTION # 18
Which AppDynamics Controller port(s) does the EUM Server require access to in a configuration where the EUM Server and Controller are on separate hosts (split-host configuration)?
- A. GlassFish administration port
- B. dedicated EUM HTTP(s) ports
- C. Controller primary HTTP{s) port
- D. Controller database and HTTP(s) ports
Answer: C
NEW QUESTION # 19
What are two settings that an administrator can configure from the AppDynamics Controller Admin Console?
(Choose two.)
- A. Controller log file rotation
- B. Metrics baseline calculation
- C. Retention periods
- D. Controller heap size
- E. License allocation
Answer: C,E
Explanation:
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
NEW QUESTION # 20
Which type of Alert and Respond action is available only on an on-premises Controller?
- A. Custom action
- B. Diagnostic action
- C. Remediation action
- D. Cloud auto-scaling
Answer: A
Explanation:
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
NEW QUESTION # 21
The Database Agent collects hardware metrics from a Windows database server using_________ . (Choose the correct option to complete the sentence.)
- A. SSH
- B. PowerShell
- C. Standalone Machine Agent
- D. WHI
Answer: B
Explanation:
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
NEW QUESTION # 22
An administrator is asked toimprove the capacity of an Events Service cluster. What is the recommended way to add capacity to the cluster?
- A. Add more storage to the master nodes of the cluster.
- B. Add nodes running on machines with identical hardware matching the existing nodes.
- C. Add a new Events Service cluster to share the load.
- D. Add more storage to as many of the existing nodes as possible.
Answer: B
Explanation:
Explanation
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the recommended way to add capacity to the Events Service cluster is to add nodes running on machines with identical hardware matching the existing nodes12. This will increase the data storage, replication, and redundancy of the cluster, as well as the processing power for queries. The Events Service cluster is horizontally scalable, so nodes can be added as your data storage requirements grow32. The Events Service must run on dedicated machines with identical directory structures, user account profiles, and hardware profiles1. For heap space allocation, AppDynamics recommends allocating half of the available RAM to the Events Service process, with a minimum of 7 GB up to 31 GB1. Solid-state drives (SSD) can significantly outperform hard disk drives (HDD), and are therefore recommended for production deployments1.
The incorrect options are:
Add a new Events Service cluster to share the load. (A) This is not recommended because it will create additional complexity and overhead for managing multiple clusters and routing data and queries to the appropriate cluster. It will also require more license units to enable analytics on multiple clusters.
Add more storage to the master nodes of the cluster. This is not recommended because it will not increase the data replication and redundancy of the cluster, nor the processing power for queries. It will also create an imbalance in the cluster, as the master nodes will have more storage than the worker nodes, which may affect the performance and stability of the cluster.
Add more storage to as many of the existing nodes as possible. (D) This is not recommended because it will not increase the data replication and redundancy of the cluster, nor the processing power for queries. It will also create an imbalance in the cluster, as some nodes will have more storage than others, which may affect the performance and stability of the cluster.
References:
1: Cisco AppDynamics Professional Implementer (500-430)
2: Events Service Requirements - AppDynamics
3: Events Service Deployment - AppDynamics
4: Events Service Deployment - AppDynamics
NEW QUESTION # 23
What is the minimum recommended number of nodes for a redundant Events Service?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: B
Explanation:
Explanation
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.
References:
1: Events Service Deployment - AppDynamics
2: Events Service Requirements - AppDynamics
NEW QUESTION # 24
What are three reasons you would create custom events using the Machine Agent REST API? (Choose three.)
- A. to create a new metric
- B. to create an event to be displayed in a Controller Audit report
- C. to create an event to track application deployment
- D. to create an event to be displayed along with Time Series data in a custom dashboard
- E. to create an alert that is to be triggered when a custom event is created
- F. to create an event to be used to trigger a health rule violation
Answer: C,D,F
Explanation:
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
NEW QUESTION # 25
What are three valid reasons to use the AppDynamics REST API to retrieve metrics? (Choose three.)
- A. to evaluate health rules
- B. to archive 1-minute granularity data
- C. to create a custom report to be run monthly to show average node availability
- D. to create an alert using a baseline to send to an internal ticketing system
- E. to calculate a new metric based on two existing metrics
- F. to retrieve health rule violations
Answer: B,E,F
Explanation:
Explanation
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. References: Retrieve Metric Data, Health Rule API
NEW QUESTION # 26
Which URL retrieves all AppDynamics business transactions from an application using the AppDynamics Rest API?
- A. http(s)://<controller-host>:<port>/controller/applications/<application_name>/business-transactions
- B. http(s)://<controller-host>:<port=/controller/rest/applications/<application_name>/allbts
- C. httpis)://<controller-host>:<port>/controller/applications/<application_name=>/allbis
- D. http(s)://<controller-host>:<port>/controller/rest/applications/<application_name=>/business-transactions
Answer: D
Explanation:
Explanation
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-host>:<port>/controller/rest/applications/<application_name>/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. References: Retrieve All Business Transactions in a Business Application, AppDynamics APIs
NEW QUESTION # 27
What are two capabilities of the standalone Machine Agent running on Linux? (Choose two.)
- A. It can restart itself if it goes down.
- B. lt can send SNMP alerts.
- C. It can communicate with multiple AppDynamics Controllers.
- D. It can start an HTTP listener for custom metrics.
- E. It can act as a forwarder for analytics events.
Answer: D,E
Explanation:
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]
NEW QUESTION # 28
Which implementation mode should be used when deploying an EUM Server with reverse proxy from a security and performance standpoint in a production environment?
- A. Install the EUM Server on the same host as the Controller, behind the reverse proxy.
- B. Install the EUM Server on a separate host from the Controller, in front of the reverse proxy.
- C. Install the EUM Server on the same host as the Controller, in front of the reverse proxy.
- D. Install the EUM Server on a separate host from the Controller, behind the reverse proxy.
Answer: D
Explanation:
Explanation
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. References: EUM Server Deployment, Install a Production EUMServer, Reverse Proxy configuration for EUM, and Browser EUM installation in the AppDynamics documentation and community.
NEW QUESTION # 29
What are two ways in which large and extra large performance profiles differ from other profile types?
(Choose two.)
- A. They must be installed on a bare metal server.
- B. They must be run with the High Availability Toolkit.
- C. An alert is generated when disk space falls below 2 GB.
- D. They are not supported on Windows.
- E. They require an enterprise-grade database.
Answer: C,E
Explanation:
Explanation
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]
NEW QUESTION # 30
Which data is unavailable in a hybrid deployment of AppDynamics where the AppDynamics Controller and Events Service are installed on-premises and the EUM Server is hosted inAppDynamics' SaaS cloud?
- A. Analytics metrics for End-User Monitoring data sets
- B. End-User Monitoring browser snapshots
- C. End-User Monitoring session information
- D. End-User Monitoring resource loading times
Answer: A
Explanation:
Explanation
In a hybrid deployment of AppDynamics, where the AppDynamics Controller and Events Service are installed on-premises and the EUM Server is hosted in AppDynamics' SaaS cloud, the data that is unavailable is the analytics metrics for End-User Monitoring data sets. This is because the analytics metrics require the Events Service to store and process the unstructured data generated by the EUM agents. However, in a hybrid deployment, the EUM Server and the Events Service are not connected, and the EUM Server does not send the EUM data to the Events Service. Therefore, the analytics metrics for EUM data sets, such as browser records, mobile snapshots, network requests, and custom events, are not available in the Controller UI or the Analytics UI1. The other data, such as resource loading times, session information, and browser snapshots, are available in the EUM Server UI, as they are stored and displayed by the EUM Server itself2. References: Hybrid Deployment and EUM Data Sets in the AppDynamics documentation.
NEW QUESTION # 31
Which two user accounts are created by the AppDynamies Controller during installation? (Choose two.)
- A. Elastic search root user
- B. Customer-specified Controller administrator account
- C. GlassFish asadmin user
- D. OS user that will run the controller
- E. MySQL appd admin user
- F. REST API user
Answer: B,C
Explanation:
Explanation
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.
NEW QUESTION # 32
Which two statements are true when updating the Database Agent? (Choose two.)
- A. All data collectors created from the previous agent must be migrated to the new agent.
- B. 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.
- C. After the Database Agent is upgraded, the AppDynamics Controller must be restarted.
- D. The Database Agent must be stopped and restarted during the upgrade.
- E. Controller-info.xml is the only file that needs to be migrated from the previous agent to the new agent.
Answer: D,E
Explanation:
Explanation
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, <db_agent_home>. Backing up allows you to revert to the previous agent installation if you need to. You can also copy over the controller-info.xml configuration file to the new installation to ensure the agent configuration is maintained.
Install the Database Agent as described for your specific installation in Administer the Database Agent.
Copy the <backup_db_agent_home>\conf\controller-info.xml file to the new installation directory,
<db_agent_home>\conf. To ensure the agent configuration is maintained, copy the
<backup_db_agent_home>\conf\controller-info.xml file to the new installation directory,
<db_agent_home>\conf.
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
NEW QUESTION # 33
Which two statements are true regarding the AppDynamics REST API for retrieving metrics? (Choose two.)
- A. End-time value must be provided if using the time-range-type of AFTER_TIME.
- B. Metrics can be retrieved for a fixed time range.
- C. Minimum and maximum values are meaningful for all metric types.
- D. Wildcards can be used in the REST API metric path.
- E. Median is one of the returned values,
Answer: B,D
Explanation:
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
NEW QUESTION # 34
Which two user accounts are created by the AppDynamies Controller during installation? (Choose two.)
- A. Elastic search root user
- B. Customer-specified Controller administrator account
- C. GlassFish asadmin user
- D. OS user that will run the controller
- E. MySQL appd admin user
- F. REST API user
Answer: B,C
NEW QUESTION # 35
What are three recommended steps to prepare a Linux environment for the installation of an AppDynamics Controller with a Large performance profile? (Choose three.)
- A. Verify the open file descriptor limit.
- B. Install MySQL.
- C. Verify the user account has root access,
- D. Install libaio,
- E. Verify that Java is installed.
- F. Verify the process limit.
Answer: A,D,F
Explanation:
Explanation
To prepare a Linux environment for the installation of an AppDynamics Controller with a Large performance profile, which is suitable for monitoring up to 1000 agents, you need to perform the following steps:
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 the open file descriptor limit on the system. The file descriptor limit determines how many files a process can open at a time. The Controller requires a high file descriptor limit to handle the large number of connections and transactions. AppDynamics recommends setting the file descriptor limit to at least 65535 for the user account that runs the Controller. You can check the current file descriptor limit by running ulimit -n and modify it by editing the /etc/security/limits.conf file2.
Verify the process limit on the system. The process limit determines how many processes a user can run at a time. The Controller requires a high process limit to handle the large number of threads and subprocesses. AppDynamics recommends setting the process limit to at least 65535 for the user account that runs the Controller. You can check the current process limit by running ulimit -u and modify it by editing the /etc/security/limits.conf file2.
Other steps that are not required but recommended for the Controller installation are verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the NUMA configuration2. You do not need to install MySQL or Java separately, as they are included in the Controller installation package3. References: Prepare Linux for the Controller, Install the Controller on Linux, and Controller System Requirements in the AppDynamics documentation.
NEW QUESTION # 36
What is required in order for an upgrade of the Java Agent to succeed?
- A. The Machine Agent must be upgraded first,
- B. The AppDynamics Controller must be restarted.
- C. The application JVM must be restarted after the agent had been updated.
- D. The host machine must be restarted.
Answer: C
Explanation:
Explanation
To upgrade the AppDynamics Java Agent, you need to copy the existing agent directory to a backup location and replace it with the new agent directory. You also need to copy any configuration file changes made in the old directory to the new agent directory. After that, you need to restart the application JVM where the Java Agent is installed, so that the new agent can take effect. Restarting the application JVM is the only required step for the upgrade to succeed. You do not need to restart the host machine, the Machine Agent, or the AppDynamics Controller12. References: Upgrade the Java Agent, Release Upgrade Checklist for Java Agents
NEW QUESTION # 37
......
500-430 Premium Exam Engine - Download Free PDF Questions: https://www.actual4dumps.com/500-430-study-material.html
500-430 Dumps Questions Study Exam Guide : https://drive.google.com/open?id=1oinX6JqhiEwVUIjQldJi82IcUd5INg98