Cisco 500-430 Exam Dumps

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.

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

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons for the missing correlated server-side snapshots are:

Server has set the HttpOnly flag on all cookies. (A) This is a valid reason because the HttpOnly flag is a security feature that prevents client-side scripts from accessing the cookies. However, the AppDynamics JavaScript Agent relies on the cookies to correlate the browser snapshots with the server-side snapshots. The JavaScript Agent injects a cookie named _appdyn_browser into the browser requests, which contains the correlation information. If the server sets the HttpOnly flag on all cookies, including the _appdyn_browser cookie, the JavaScript Agent cannot read or modify the cookie, and the correlation fails.To enable the correlation, the server should not set the HttpOnly flag on the _appdyn_browser cookie12.

Server-side application is not instrumented with server agent. (E) This is a valid reason because the server-side snapshots are collected by the AppDynamics app agents that instrument the application servers. The app agents monitor the business transactions that are executed by the server-side application, and capture the execution context, call graphs, errors, and metrics. If the server-side application is not instrumented with the app agent, the server-side snapshots are not available, and the correlation fails.To enable the correlation, the server-side application should be instrumented with the app agent that is compatible with the application server and the Controller34.

The incorrect options are:

Correlated server-side snapshots work only for .NET Applications. (B) This is not a valid reason because the correlated server-side snapshots work for any application server that is instrumented with the AppDynamics app agent, not only for .NET applications. The AppDynamics platform supports various application servers, such as Java, .NET, PHP, Node.js, Python, and C/C++.The app agents collect the server-side snapshots for the business transactions that are executed by the application server, regardless of the programming language or framework34.

Correlated snapshots are visible only if the injection mechanism is Automatic. This is not a valid reason because the correlated snapshots are visible regardless of the injection mechanism. The injection mechanism refers to the way the AppDynamics JavaScript Agent is inserted into the web pages. There are two injection mechanisms: Automatic and Manual. The Automatic injection mechanism uses the app agent to inject the JavaScript Agent into the web pages that are served by the application server. The Manual injection mechanism requires the user to manually insert the JavaScript Agent into the web pages. Both injection mechanisms support the correlation of the browser snapshots and the server-side snapshots, as long as the JavaScript Agent and the app agent are configured correctly .

Correlated snapshots are visible only if browser is Chrome. (D) This is not a valid reason because the correlated snapshots are visible regardless of the browser. The AppDynamics JavaScript Agent supports various browsers, such as Chrome, Firefox, Safari, Edge, and Internet Explorer. The JavaScript Agent collects the browser snapshots for the web pages that are loaded by the browser, and correlates them with the server-side snapshots, regardless of the browser type or version .

Correlated server-side snapshots are visible only if Java version is 1.7+. (F) This is not a valid reason because the correlated server-side snapshots are visible regardless of the Java version. The AppDynamics Java Agent supports various Java versions, such as 1.5, 1.6, 1.7, 1.8, and 11. The Java Agent collects the server-side snapshots for the business transactions that are executed by the Java application server, and correlates them with the browser snapshots, regardless of the Java version or vendor .

1: Browser Snapshots - AppDynamics

2: Troubleshoot Browser RUM - AppDynamics

3: Transaction Snapshots - AppDynamics

4: Supported Environments and Versions - AppDynamics

[5]: Browser Real User Monitoring - AppDynamics

[6]: Set Up and Configure Web EUM - AppDynamics

[7]: Browser Support - AppDynamics

[8]: Java Agent - AppDynamics

[9]: Java Supported Environments - AppDynamics

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.

Custom correlation is needed when the default detection mechanisms of AppDynamics are not capable of auto-correlating transactions across tiers or across parent-child threads in complex multithreaded applications. Custom correlation enables the user to configure AppDynamics to propagate a unique correlation key by using the extension points of the distributed protocol or by decorating the payload. Among the four options, a custom TCP concurrent server is the most likely to require the implementation of custom correlation, as it is an unsupported framework and protocol that may not have easily-defined method calls or payload objects to configure as exit points or entry points. The other options, such as SOAP, JMS, and WCF, are supported by AppDynamics and can be automatically correlated by the agents without the need for custom configuration.Reference:Custom Correlation for Java ApplicationsandConfigure Custom Correlation for .NET Applicationsin the AppDynamics community.