Cisco Updated 500-425 Exam Questions and Answers by blossom

According to the Tiers and Nodes document1, establishing standards for naming applications, tiers, and nodes can help you identify and organize the components of your monitored environment, as well as troubleshoot performance issues and health rule violations. Some of the statements about establishing naming conventions are true:

• Application Tier and Node values can be configured in the application agent startup script: This is true for Java agents, as you can pass values to the agent that will be used as the application, tier, and node name for the system. For example, you can use the -Dappdynamics.agent.applicationName, -Dappdynamics.agent.tierName, and -Dappdynamics.agent.nodeName properties to specify the names in the JVM startup script2.
• Node names must be unique across the entire business application: This is true, as node names are used to identify the individual instances of the application components that are monitored by AppDynamics. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
• Application Tier and Node values can be configured in the controller-info.xml file: This is true for Java agents, as you can also configure the names in the controller-info.xml file, which is located in the /conf directory. The controller-info.xml file contains the properties that define the agent identity and connection to the Controller. You can use the , , and elements to specify the names in the file2.

Some of the statements about establishing naming conventions are false:

• Nodes that reside on different Tiers and different machines (hosts) can have duplicate Node names: This is false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
• Nodes that reside on the same Tier but on different machines (hosts) can have duplicate Node names: This is also false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.

References:

• Tiers and Nodes
• Name Business Applications, Tiers, and Nodes

Before creating a new database collector, you need to perform the following actions:

• Verify the database connection details. You need to provide the host, port, database name, and credentials for the database that you want to monitor. You also need to select the database type and the collector type1
• Create a database user and set user permissions. You need to create a database user with the minimum required permissions to access the database and run the queries that the Database Agent needs. You can use the scripts provided by AppDynamics to create the user and grant the permissions2

References: 1: Add Database Collectors 2: Database Permissions

The UniqueHostID agent property is recommended to be used when the machine agent is with multiple app agents on the same machine or when the machine agent is with an app agent on the same machine. This property allows you to specify a unique identifier for the host machine that overrides the default hostname resolution. This helps to avoid conflicts or confusion when multiple agents are running on the same host or when the hostname is not consistent across different agents1 References: 1: How are you able to associate the machine agent with application

The option that would solve this the fastest for the customer is to include baseline data within widgets on the dashboard. Baseline data is the data that represents the normal or expected behaviorof a metric, based on the historical data collected by the AppDynamics Cognition Engine. By including baseline data within widgets on the dashboard, the customer can easily compare the current value of the metric with the past average value for the same time. For example, if the customer wants to see the number of current database connections on their application in a Timeseries graph, and compare it to the past averages for the same time, they can create a Timeseries graph widget that shows the metric “Database Connections” and enable the option “Show Baseline Data” in the widget settings. This will display the current and the baseline values of the metric in the same graph, and allow the customer to see the trends and deviations over time1.