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: 3)

Page 2 of 13
PDF with 50 Questions

What are two settings that an administrator can configure from the AppDynamics Controller Admin Console? (Choose two.)

  1. Metrics baseline calculation
  2. Controller log file rotation
  3. Controller heap size
  4. License allocation
  5. Retention periods

Answer(s): D,E

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 mode. 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 alerts. 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 schedule.


Reference:

Access the Administration Console, License Rules, Data Retention



If using SSL for agent communication with an AppDynamics Controller, it is recommended that agent SSL traffic

  1. is encrypted with a 64-bit encryption key
  2. is decrypted and then encrypted again at the firewall
  3. terminates at a reverse proxy or a load balancer in front of the Controller
  4. terminates at the Controller

Answer(s): C

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.


Reference:

Agent-to-Controller Connections and Enable SSL and SSH for Database Agent Communications in the AppDynamics documentation.



Which artifacts are needed, at minimum, to add a custom extension to a Machine Agent?

  1. Directory
    Jar or Script file

    Monitor.xml file
  2. Directory
    Manitor.xml file
    Custom-gxtension.xml file
  3. Directory
    Zip Extension
    Monitor.xml file
  4. Directory
    Script file
    Config.json file

Answer(s): A

Explanation:

To add a custom extension to a Machine Agent, you need at least three artifacts: a directory, a jar or script file, and a monitor.xml file. The directory is where you place your extension files under the <machine_agent_home>/monitors directory. The jar or script file is the executable file that collects and reports the custom metrics to the Machine Agent. The monitor.xml file is the configuration file that defines the name, frequency, and parameters of your extension. You can also optionally include other files such as libraries, configuration files, or templates for your extension.


Reference:

Build a Monitoring Extension Using Scripts, Extensions and Custom Metrics



An administrator is asked to improve the capacity of an Events Service cluster.
What is the recommended way to add capacity to the cluster?

  1. Add a new Events Service cluster to share the load.
  2. Add nodes running on machines with identical hardware matching the existing nodes.
  3. Add more storage to the master nodes of the cluster.
  4. Add more storage to as many of the existing nodes as possible.

Answer(s): B

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 nodes. 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 grow. The Events Service must run on dedicated machines with identical directory structures, user account profiles, and hardware profiles. 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 deployments.
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.


Reference:

1: Cisco AppDynamics Professional Implementer (500-430)
2: Events Service Requirements - AppDynamics
3: Events Service Deployment - AppDynamics
4: Events Service Deployment - AppDynamics






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

500-430 Discussions & Posts