Practice Free 500-430 Exam Online Questions – Page 2

Question #11

Why would a load balancer be deployed in production for a single-node events cluster?

A . to use the embedded Events Service along with the single-node cluster
B . to hide the events server’s real name
C . to allow for deployment growth in the events cluster
D . to provide redundancy for the single-node

Correct Answer: C
C

Explanation:

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 by balancing 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.

Reference: Events Service Deployment in the AppDynamics documentation.

Question #12

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 . They are not supported on Windows.
D . They require an enterprise-grade database.
E . An alert is generated when disk space falls below 2 GB.

Reveal Solution Hide Solution

Correct Answer: DE
DE

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 is because 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.

Reference: Platform Requirements, Controller System Requirements, Controller Disk Space Requirements, Controller Disk Space Alert, [High Availability], [High Availability Toolkit]

Question #13

What is the most important factor in determining sizing for AppDynamics Controller?

A . Projected metric load per minute on the Controller
B . Number of administrators/end users logging on to the Controller to monitor application performance
C . Type of agents reporting to the Controller
D . Number of AppDynamics applications to be created on the Controller

Reveal Solution Hide Solution

Question #14

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?

A . The account is ‘root’ and the user is ‘admin’.
B . The account is ‘customer!’ and the user is ‘root’.
C . The account is ‘system’ and the user is "root.
D . The account is internal’ and the user is ‘admin’.

Reveal Solution Hide Solution

Question #15

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

A . Metrics baseline calculation
B . Controller log file rotation
C . Controller heap size
D . License allocation
E . Retention periods

Reveal Solution Hide Solution

1 2

Exams