Cisco 500-430 Practice Test - Questions Answers, Page 3

As an AppDynamics Controller grows beyond supporting 500 agents, network throughput becomes more important. This is because the Controller needs to handle a large volume of data from the agents, as well as serve requests from the UI and API clients. Network throughput is the measure of how much data can be transferred over a network in a given time. A low network throughput can cause delays, errors, or timeouts in the communication between the Controller and the agents or clients.Therefore, it is recommended to monitor the network throughput of the Controller and ensure that it meets the minimum requirements for the expected load123.Reference:Controller System Requirements,Performance and Controller Sizing Guidelines,How to Run AppDynamics in Microsoft Azure

The AppDynamics Controller is a Java web application that runs on a GlassFish application server and uses a MySQL database. During the installation of the Controller, two user accounts are created by default:

The GlassFish asadmin user is the administrative user for the GlassFish server. This user has the authority to start, stop, and configure the GlassFish server and its domains. The default username for this user isadminand the default password isappdynamics.You can change the password for this user after the installation by using theasadmincommand-line tool1.

The customer-specified Controller administrator account is the user account that you provide during the installation wizard. This is the account that you use to access the AppDynamics User Interface (UI) for the first time and perform various tasks such as creating applications, configuring agents, managing users and groups, and so on. You can choose any username and password for this account, but AppDynamics recommends using only ASCII characters.You can also create additional user accounts in the Controller UI after the installation2.

The other options are not user accounts that are created by the Controller installation. The Elastic search root user, the REST API user, and the MySQL appd admin user are user accounts that are used internally by the Controller components and are not exposed to the end user.The OS user that will run the controller is a user account that you need to create on the host machine before the installation, and it is not created by the Controller installation3.Reference:Controller Installation,Manage Users and Groups, andUpdate the Root User and Glassfish Admin Passwordsin the AppDynamics documentation.

An Events Service cluster is a group of two or more Events Service nodes that work together to store and process unstructured data generated by AppDynamics components such as Application Analytics, Database Visibility, and End User Monitoring1.Using an Events Service cluster has two main advantages over a single-node instance12:

Clusters allow data replication across multiple nodes. This means that the data is duplicated and distributed among the nodes in the cluster, providing data redundancy and protection against data loss in case of a node failure. Data replication also improves data availability and query performance, as the cluster can handle concurrent requests from multiple clients.

Clusters are horizontally scalable by adding nodes. This means that the cluster can grow in size and capacity by adding more nodes to the cluster, without affecting the existing nodes or data. Horizontal scaling allows the cluster to handle increasing data volumes and performance demands, as well as balance the workload among the nodes.Reference:Events Service Deployment,What are the Benefits of Server Clustering?

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons that would require an administrator to install the Events Service cluster manually are:

Security concerns with passwordless SSH (B): This is a valid reason because the automated installation of the Events Service cluster requires passwordless SSH access to the target hosts. Passwordless SSH allows the Enterprise Console to execute commands on the remote hosts without prompting for a password. However, some organizations may have security policies that prohibit passwordless SSH access, as it may pose a risk of unauthorized access or malicious attacks.In such cases, the administrator can install the Events Service cluster manually, by following the steps described in the Manual Installation of the Events Service Cluster document1.

Security requirements to install using a non-root user account : This is a valid reason because the automated installation of the Events Service cluster requires root privileges on the target hosts. Root privileges allow the Enterprise Console to create directories, change permissions, and install packages on the remote hosts. However, some organizations may have security policies that restrict root access, as it may pose a risk of accidental or intentional damage to the system.In such cases, the administrator can install the Events Service cluster manually, by following the steps described in the Manual Installation of the Events Service Cluster document1. The administrator can use a non-root user account that has sudo privileges to perform the manual installation.

The incorrect options are:

Installation on SUSE Linux (A): This is not a valid reason for manual installation, because the automated installation of the Events Service cluster supports SUSE Linux as one of the compatible operating systems.The Enterprise Console can install the Events Service cluster on SUSE Linux hosts using the automated installation process, as long as the hosts meet the prerequisites described in the Events Service Requirements document2.

Installation on Windows (D): This is not a valid reason for manual installation, because the Events Service cluster does not support Windows as an operating system. The Events Service cluster can only run on Linux hosts, as it is based on Apache Cassandra, which is a Linux-based distributed database.The Events Service cluster cannot be installed on Windows hosts, either manually or automatically2.

1: Manual Installation of the Events Service Cluster - AppDynamics

2: Events Service Requirements - AppDynamics

The AppDynamics Rest API allows you to retrieve information and perform operations on the AppDynamics platform using HTTP requests. To retrieve all AppDynamics business applications from an AppDynamics Controller using the AppDynamics Rest API, you need to use the following URL format:

http(s)://<controller-host>:/controller/rest/applications

This URL returns the business application names and internal numeric identifiers for all the applications that are monitored by the Controller. You can use the application name or ID as a parameter for other API methods that require the application context. You can also specify the output format as XML (default) or JSON by adding the output query parameter. For example:

http(s)://<controller-host>:/controller/rest/applications?output=JSON

This URL returns the same information as the previous one, but in JSON format. You can also filter the applications by their status (alive or not) by adding the time-range-type query parameter. For example:

http(s)://<controller-host>:/controller/rest/applications?time-range-type=BEFORE_NOW&duration-in-mins=60

This URL returns only the applications that are alive in the last 60 minutes.An alive application is an application with at least one node that submits at least one metric to the Controller in the provided time range12.Reference:Application Model API,Metric and Snapshot API

AppDynamics can collect sensitive data such as credit card numbers from various sources, such as SQL queries, error messages, HTTP headers, cookies, and so on. To protect this data from unauthorized access or exposure, an administrator should configure the user permissions for the following features:

SQL Bind Variables: This feature enables the agents to capture the values of the parameters that are passed to SQL queries. These values can contain sensitive data such as credit card numbers, passwords, or personal information. To prevent this data from being stored or displayed in the Controller UI, the administrator should disable the Capture SQL Bind Values permission for the users who do not need to see this data. Alternatively, the administrator can enable the Mask SQL Bind Values permission, which replaces the values with asterisks (*) in the UI.The administrator can also configure the agent properties to exclude or mask certain bind variables based on patterns or keywords1.

Diagnostic Data Collectors: This feature enables the agents to collect additional data from the application code, such as method arguments, return values, HTTP headers, cookies, and so on. These data can also contain sensitive information that should not be exposed to unauthorized users. To control the access to this data, the administrator should disable the View Diagnostic Data Collectors permission for the users who do not need to see this data.The administrator can also configure the agent properties to exclude or mask certain data collectors based on patterns or keywords2.

Other features that can collect sensitive data and require user permissions are Error Detection, Memory Monitoring, and Policies. However, these features are less likely to capture credit card numbers than SQL Bind Variables and Diagnostic Data Collectors. Therefore, the best answer is option C and E.Reference:Sensitive Data Collection and Security,SQL Bind Variables, andDiagnostic Data Collectorsin the AppDynamics documentation.

The AppDynamics REST API to retrieve metrics allows you to get values generated for metrics by specifying the path of the metric and the time frame for the data1.Some of the valid reasons to use this API are12:

To archive 1-minute granularity data. The AppDynamics Controller stores metric data at different levels of granularity depending on the retention period. For example, it stores 1-minute granularity data for 8 days, 10-minute granularity data for 32 days, and 1-hour granularity data for 365 days. If you want to archive the 1-minute granularity data for longer than 8 days, you can use the API to retrieve and store the data in an external database or file system.

To calculate a new metric based on two existing metrics. The AppDynamics Controller provides some built-in metrics such as average response time, calls per minute, errors per minute, etc. However, you may want to calculate a new metric that is not available in the Controller, such as the ratio of errors to calls, or the percentage of slow transactions. You can use the API to retrieve the values of the existing metrics and perform the calculation using your own logic or formula.

To retrieve health rule violations. Health rules are the rules that define the performance and availability thresholds for your application components. When a health rule is violated, the AppDynamics Controller generates an event and optionally triggers a policy action. You can use the API to retrieve the list of health rule violations for a given application, time range, and severity level. This can help you monitor and troubleshoot the health of your application and take corrective actions if needed.Reference:Retrieve Metric Data,Health Rule API

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two recommendations for servers in an Events Service Cluster are:

Should be on the same local network : This is a valid recommendation because the Events Service Cluster is based on Apache Cassandra, which is a distributed database that relies on network communication between the nodes. Having the servers on the same local network reduces the network latency and improves the performance and reliability of the cluster.The network bandwidth should be at least 1 Gbps, and the network firewall should allow the required ports for the Events Service Cluster12.

Should have identical hardware specifications (D): This is a valid recommendation because the Events Service Cluster is horizontally scalable, which means that the nodes share the data storage and processing load equally. Having identical hardware specifications for the servers ensures that the cluster is balanced and efficient, and avoids performance bottlenecks or failures due to hardware differences.The hardware specifications should meet the minimum requirements for the Events Service Cluster, such as CPU cores, RAM, disk space, and disk type12.

The incorrect options are:

Should be installed using the same user account (A): This is not a valid recommendation because the Events Service Cluster does not require the same user account for installation. The user account that is used to install the Events Service Cluster should have sudo privileges on the target hosts, but it does not have to be the same for all the hosts.The user account that is used to run the Events Service Cluster should have read and write permissions on the installation directory, but it does not have to be the same for all the hosts either12.

Should have eight or more CPU cores (B): This is not a valid recommendation because the Events Service Cluster does not require eight or more CPU cores for the servers. The minimum requirement for the CPU cores is four, and the recommended requirement is six.Having more CPU cores may improve the performance of the cluster, but it is not a mandatory recommendation12.

Should be running the same operating system version (E): This is not a valid recommendation because the Events Service Cluster does not require the same operating system version for the servers. The Events Service Cluster supports various Linux operating systems, such as CentOS, Red Hat, Ubuntu, and SUSE.The operating system version should be compatible with the Events Service version, but it does not have to be the same for all the hosts12.

1: Events Service Requirements - AppDynamics

2: Events Service Deployment - AppDynamics

The AppDynamics .NET Agent can instrument both 32-bit and 64-bit processes, as long as they are running on a supported .NET Framework version and operating system. The agent automatically detects the process architecture and loads the appropriate profiler DLL.You can also specify the process architecture manually in the agent configuration file1. The AppDynamics .NET Agent also supports instrumentation of multiple instances of the same application, such as Windows services or standalone applications. You can configure the agent to assign different tier and node names for each instance, based on the process name, process ID, or command line arguments.This allows you to monitor the performance and health of each instance separately2.

The other statements are false because:

A) AppDynamics .NET Agent does support instrumenting processes running multiple App domains. The agent can monitor multiple App domains within a single process, as long as they are running the same .NET Framework version.The agent can also monitor multiple applications within a single App domain, by using the Standalone Applications element in the agent configuration file3.

B) AppDynamics .NET Agent does not automatically discover all the Windows services to be instrumented. The agent automatically instruments IIS applications only. For Windows services or standalone applications, you need to manually configure the agent by editing the agent configuration file and adding the Windows Services or Standalone Applications element.You also need to provide the executable name, tier name, and node name for each service or application4.

D) AppDynamics .NET Agent does not require that the Windows services are running under the ''App.pool identity user'' account. The agent can instrument Windows services running under any user account, as long as the account has sufficient permissions to load the agent profiler DLL and access the agent configuration and log files.The ''App.pool identity user'' account is only required for IIS applications that run in an application pool5.