CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Cisco®
  5. 500-430

Free 500-430 Exam Braindumps (page: 5)

Page 4 of 13
PDF with 50 Questions

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)?

  1. dedicated EUM HTTP(s) ports
  2. GlassFish administration port
  3. Controller database and HTTP(s) ports
  4. Controller primary HTTP{s) port

Answer(s): D

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 Controller. The GlassFish administration port is used to access the Controller Admin Console, not by the EUM Server. The Controller database port is used by the Controller to connect to the MySQL database, not by the EUM Server.


Reference:

Controller Port Settings, Configure the Port for the EUM Agent, Access the Administration Console, Controller System Requirements



Which two preparatory tasks are required prior to installing an AppDynamics Controller on Linux? (Choose two.)

  1. Install JRE.
  2. Ensure that MySQL port (3388) is opened.
  3. Install SSH.
  4. Install libaio.
  5. Verify that sufficient temporary (tmp) space is available (at least 1 GB).

Answer(s): D,E

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

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 /tmp. 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 installer. Other preparatory tasks include verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the file descriptor limit.


Reference:

Prepare Linux for the Controller, Install the Controller on Linux, and [Controller System Requirements] in the AppDynamics documentation.



The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent.
Which account and user name are used to connect to the Controller to view the information provided by the internal AppDynamics agent?

  1. The account is `root' and the user is `admin'.
  2. The account is `customer!' and the user is `root'.
  3. The account is 'system' and the user is "root.
  4. The account is internal' and the user is `admin'.

Answer(s): C

Explanation:

The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent that monitors the performance and health of the Controller itself. To access the information provided by the internal agent, you need to log in to the Controller UI with the following credentials:
Account = system
Username = root
Password = <root_user_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 it. The root user is the default administrator user for the system account and has the same password as the admin user for the customer1 account.


Reference:

Controller Self-Monitoring, Monitoring a Controller Using the Internal Monitoring Agent, Controller Accounts



What is the correct method to perform a NET Agent upgrade?

  1. Perform the agent upgrade on the application server host by running the MSI Installer Package.
  2. Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API.
  3. Perform the agent upgrade on the application server host by running the Agent Configuration Utility.
  4. Perform the agent upgrade via the AppDynamics Controller Ul.

Answer(s): A

Explanation:

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the correct method to perform a NET Agent upgrade is to perform the agent upgrade on the application server host by running the MSI Installer Package. This method will install updated agent files and maintain legacy configurations. You do not need to uninstall the old agent first when you upgrade from the NET Agent >= 3.9, except for patch releases. You need to stop IIS, instrumented Windows services, and instrumented standalone applications before running the MSI Installer Package. You also need to launch an elevated command prompt with full administrator privileges and specify your account access key for single-tenant Controller accounts. After the installation, you need to restart

Windows services and standalone applications.
The incorrect options are:
Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API. (B) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller REST API does not provide any endpoint for agent installation or upgrade. The REST API is mainly used for retrieving or updating configuration data, metrics, events, snapshots, and other information from the Controller.
Perform the agent upgrade on the application server host by running the Agent Configuration Utility. © This is not a valid method for upgrading the NET Agent, because the Agent Configuration Utility is a tool for modifying the agent configuration after installation, not for installing or upgrading the agent. The Agent Configuration Utility allows you to change the Controller connection settings, the agent logging level, the proxy settings, and other advanced options. Perform the agent upgrade via the AppDynamics Controller UI. (D) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller UI does not provide any feature for agent installation or upgrade. The Controller UI is mainly used for monitoring, analyzing, and troubleshooting the performance of the applications, business transactions, tiers, nodes, and other entities that are instrumented by the agents.


Reference:

1: Upgrade the .NET Agent for Windows - AppDynamics
2: Release Upgrade Checklist for .NET Agents - AppDynamics
3: REST API - AppDynamics
4: Configure the .NET Agent - AppDynamics
5: AppDynamics Application Performance Monitoring Platform - AppDynamics






Post your Comments and Discuss Cisco® 500-430 exam with other Community members:

500-430 Discussions & Posts