Cisco 500-430 Dumps Questions Answers

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. References: Sensitive Data Collection and Security, SQL Bind Variables, and Diagnostic Data Collectors in the AppDynamics documentation.

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.

References: .NET Agent Configuration Properties, Configure the .NET Agent for Windows Services and Standalone Applications, Instrument the DefaultDomain for Standalone Applications, Install the .NET Agent for Windows, Administer the .NET Agent

The AppDynamics Controller Admin Console lets you configure certain global settings for the Controller, such as metric retention periods, UI notification triggers, tenancy mode, and accounts in multi-tenancy mode1. Two of the settings that an administrator can configure from the AppDynamics Controller Admin Console are:

• License allocation: This setting allows you to view and manage the license usage and availability for your Controller. You can see the total number of licenses, the number of licenses in use, the number of licenses available, and the license expiration date for each agent type. You can also allocate licenses to specific applications or accounts, and set license limits and alerts2.
• Retention periods: This setting allows you to specify how long the Controller retains the metric data and the event data for your monitored applications. You can configure the retention periods for different types of data, such as minute-level metrics, hour-level metrics, day-level metrics, transaction snapshots, and events. You can also configure the data purge schedule and the data backup schedule3.

References: Access the Administration Console, License Rules, Data Retention