Cisco 500-430 Exam Dumps - Actual Questions Answers

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

A load balancer is a network device that distributes incoming traffic among a group of servers or nodes. A load balancer can improve the performance, availability, and scalability of a service bybalancing the load and providing failover mechanisms. In the context of AppDynamics, a load balancer can be used to route the traffic from the Controller and other Events Service clients to the Events Service nodes. The Events Service is the on-premises data storage facility for unstructured data generated by Application Analytics, Database Visibility, and End User Monitoring deployments.

One of the reasons why a load balancer would be deployed in production for a single-node Events Service cluster is to allow for deployment growth in the future. A single-node Events Service cluster is suitable for test environments or small-scale deployments, but it does not offer data replication or scalability. If the data volume or availability requirements increase, the Events Service cluster needs to be expanded to a multi-node cluster, which consists of three or more nodes. Deploying a load balancer in front of a single-node Events Service cluster makes it easier to add more nodes later, without having to modify the configuration of the Controller and other Events Service clients. The load balancer can also provide a single endpoint for the clients and enable load balancing and failover among the nodes1.

The other options are not valid reasons for deploying a load balancer for a single-node Events Service cluster. Option A is incorrect, because the embedded Events Service is not meant to be used along with the single-node cluster, as it runs on the same machine as the Controller and does not offer data replication or scalability. The embedded Events Service is only used by the Database Visibility product by default, and it is not recommended for production Application Analytics or EUM installations1. Option B is incorrect, because hiding the Events Service server’s real name is not a security or performance benefit, and it can be achieved by other means, such as DNS or firewall rules. Option D is incorrect, because a load balancer cannot provide redundancy for a single-node, as there is no other node to fail over to in case of a node failure. A load balancer can only provide redundancy for a multi-node cluster, which has data replication and fault tolerance1. References: Events Service Deployment in the AppDynamics documentation.

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